Pikbase

The managed backend for business applications

Build your business app. Not another backend.

Define your data and business rules. Build your frontend. Pikbase brings APIs, permissions, functions, workflows, and documents together in one managed backend.

Discuss your project See how it works

For operational systems, business portals, and ERP-style applications—with or without AI.

Your application

Your frontend
HTMLCSSJSReact
Any framework · Any static host
PikbaseManaged backend
Data Auth & permissions Functions Workflows Documents & storage Transactions & audit

Just your app. Pikbase behind it.No separate API server or ORM process to deploy.

Overview · under two minutes

See how Pikbase fits behind your app.

The usual path

Every business app needs a backend. So every team builds one. Again.

Each piece is one more thing to deploy, secure, and keep running before the first real feature ships.

Assembled for every project
  • API server
  • ORM layer
  • Auth service
  • Permission checks
  • Job queue
  • Workflow engine
  • PDF renderer
  • Email service
  • File storage
  • Audit log
With Pikbase
PikbaseManaged backend
Data Auth & permissions Functions Workflows Documents & storage Transactions & audit

No separate API backend, ORM process, workflow server, or document service to deploy.

One connected business process

From order to invoice. Without assembling another stack.

Configure the rules once. Pikbase coordinates the data, calculations, approval, document, and delivery steps behind your application.

01 · CalculateApply your rules

Calculate line totals, discounts, and taxes with server-side logic you define.

Functions guide ↗
02 · CreatePrepare the invoice

Create the invoice and line items together in one database transaction.

Transactions guide ↗
03 · ApproveRoute the decision

Assign approval tasks and retain the workflow execution history.

Workflow guide ↗
04 · DeliverGenerate and send

Render and store a localized PDF, then email it through your configured provider.

Documents guide ↗

You provide the business rules, approval policy, templates, and sender configuration. This is an example of capabilities you can configure, not a preinstalled invoicing application. Email uses your SMTP or SES provider, and a database rollback cannot recall an email already sent.

One managed backend

The backend pieces you need. Already connected.

No separate API backend, ORM process, workflow server, or document service to deploy. Open any capability for its documented contract.

01

Model once

Database

Give AI-assisted teams a governed data model, query layer, and transactional save path instead of a hand-built backend.

02

Control access

Auth

Keep identity, tenancy, and deep permission policies enforced in the backend, not the interface.

03

Run logic

Functions

Run business logic inside the tenant runtime without deploying an application server or server farm.

04

Coordinate work

Workflows

Compose durable, inspectable business processes instead of asking generated glue code to hold state.

05

Deliver content

Documents

Manage documents, PDFs, messages, files, and multilingual content as governed backend capabilities.

06

Work with agents

Assistant

Let coding agents work through CLI and MCP against the same governed backend contract your team controls.

One contract for every caller

Your app. Your team. Your agents. One permission model.

The frontend, CLI, and supported MCP tools call the same backend. Entity, record, and property permissions are enforced for each caller.

  • Application
  • Console / CLI
  • Supported MCP tools
Backend checks entity, record, and property permissions
  • Scoped by permission

    Every caller — a member, a CLI session, or an agent — acts inside the workspace permissions granted to it.

  • Inspectable operations

    Definitions, functions, and workflows stay readable in the console instead of disappearing into generated glue code.

  • Destructive actions require confirmation

    Destructive agent-initiated operations require explicit confirmation before they run.

Explore agent access Read the docs 
const orders = new QueryParams<Order>("Order")
  .filter("status", "open", QueryFunction.Equals)
  .include(new IncludeQuery<Customer>("customer").select(["id", "name"]))
  .self.sortBy("createDate", QuerySortType.Descending)
  .take(25)
  .returnCount();

const page = await entityService.query(orders, token, tenantCode);
gsb call query --raw --input '{
  "queryParams": {
    "entDefName": "Order",
    "filters": [{ "col": { "name": "status" },
                  "val": { "value": "open" },
                  "function": 0 }],
    "count": 25
  }
}'

Change with control

Review what ships. Recover what changed.

Keep backend resources in source, deploy reviewed changes, and choose a recovery path that matches the scope of the problem.

git · main7f34c2a

schema/Invoicemodified

workflows/Approvalmodified

functions/validateInvoicemodified

docTemplates/Invoicemodified

reviewdeploy
PIKBASE WORKSPACEacme-production

Definitions, logic, and policy remain visible to your team and permission-scoped agents.

01 · Whole workspace

Workspace backups

Workspace backups distinguish automatic and manual restore points; authorized operators can create on-demand backups and restore completed snapshots.

02 · Single record

Entity snapshots

Version-enabled entities support explicit restorable snapshots, while tracked entities retain automatic field-change history.

Revert and redeploy source for a definition or logic error, restore a workspace backup for an environment-wide problem, or use an entity snapshot for one versioned record. Backup availability and retention depend on your plan.

For application teams and implementation partners

What does your business need to build?

Bring your process, approval rules, integrations, and deployment requirements. We’ll evaluate how they fit in Pikbase.

Discuss your project See pricingSecurity and trust