Pikbase

Product / Run logic

Functions

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

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 ↗

Runs in the tenant

Functions and shared code libraries execute in the tenant runtime, so adding backend behavior does not require provisioning a separate application server.

Keeps secrets server-side

Privileged operations, integration credentials, and domain rules stay out of the browser bundle.

Inside the transaction

Entity writes made during a run join that run's transaction and roll back together, with explicit commit checkpoints when a long operation needs one.

Callable by name

One function is reachable from workflows, entity triggers, the CLI, and authorized agent tools through the same contract.

Operations

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

runWfFunction

Executes a specific workflow function directly by name or ID.

testWfFunction

Tests a workflow function without saving it to the GSB backend.

Keep reading

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

Serverless functions

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.

Workflows ↗

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

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.