Pikbase

Product / Coordinate work

Workflows

Describe durable, inspectable processes instead of hiding state in glue code.

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 ↗

Query and transactionally save related data through one permission-aware entity contract.

Auth ↗

Enforce identity, tenancy, and record-level authorization at the data layer instead of in the interface.

Functions ↗

Add tenant-resident logic and shared libraries where data operations are not enough.

Documents ↗

Turn governed multilingual content into stored files, PDFs, and email sent under your own identity.

Assistant ↗

Give a coding agent the same contract as your team, bounded by the same permissions.