Pikbase

Product / Coordinate work

Workflows

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

Custom functions, shared libraries, and workflows execute in the Pikbase tenant runtime rather than requiring a separately deployed application server.Verified 2026-08-20 · owner GSB Core · evidence ↗

Durable by design

A workflow waits on people, timers, functions, or external events without a caller holding the process open.

Attached to the model

Entity definitions can carry triggers that run before or after an operation, ordered or in parallel, for single or bulk requests.

Readable afterwards

Steps and execution logs stay visible in the console, so an operator can reconstruct what happened.

Explicit side effects

Operations that reach outside the database are disabled by default and require explicit approval before they run.

Operations

Each entry links to its reference page, generated from the same documentation the CLI and the MCP server return.

startWorkflow

Creates a workflow instance and returns immediately, without waiting for completion.

runWorkflow

Executes a workflow and waits for the backend to finish before returning.

iterateTask

Advances or provides input to tasks within running workflows.

Keep reading

The guide covers the working shape of this capability, including request payloads, limits, and failure handling.

Workflows

Rest of the platform

Database ↗

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

Auth ↗

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

Functions ↗

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

Documents ↗

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

Assistant ↗

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