Pricing detail
Included capacity.
Three measurements determine what a plan includes: API and execution capacity, database storage, and file storage. API and execution capacity is derived from your plan’s power users; database storage, file storage, and retained backups are quantities the plan buys. End-user activity consumes the same allowance but does not add an identity charge.
Back to pricingMeasurement status. These are the allowances your plan includes. Usage measurement is being rolled out and appears in Pikbase Account as it becomes available for your workspace. Until enforcement begins we contact you rather than restricting a workspace or charging for consumption above an allowance, and the date enforcement starts will be published on this page and sent by email at least 30 days beforehand.
Per included power user, each month
Each included power user adds the same allowance to the workspace, on every plan. What counts as a power user?
| API calls | 500,000 |
|---|---|
| Or function and workflow execution | 1 h 23 min |
API requests and function or workflow execution draw on one shared allowance. For capacity accounting each API call is normalized to 10 ms of execution capacity, so an application that leans on workflows and one that leans on queries are treated the same and neither has to be estimated separately. The two rows above show the same allowance spent entirely one way or entirely the other, not two separate budgets.
What each plan includes
API and execution totals are the per-power-user allowance multiplied by the plan’s power users. Database storage, file storage, and retained backups are the quantities each plan buys, the same in the Core, Corporate, and SaaS editions; file transfer out each month is up to twice the file storage. Additional power users, storage, and backups raise these totals at their Marketplace prices.
| Plan | Included power users | API calls / month | Or execution capacity | Database | Files | Retained backups |
|---|---|---|---|---|---|---|
| Starter | 3 | 1.5 million | 4 h 10 min | 4 GB | 20 GB | 1 |
| Team | 10 | 5 million | 13 h 53 min | 12 GB | 100 GB | 1 |
| Business | 25 | 12.5 million | 34 h 43 min | 32 GB | 200 GB | 1 |
| Enterprise | Agreed with your deployment | Agreed | Agreed | Agreed | Agreed | Agreed |
Marketplace units
When a workspace needs more than its plan carries, add capacity to that workspace from the Marketplace in Pikbase Account instead of moving the whole organization to a larger plan. Unit prices are shown in the Marketplace before you confirm, and additions are billed on your existing cycle.
| Add-on | Unit | Price | Notes |
|---|---|---|---|
| Power users | 1 user | $12 per month | Another person who operates functions, workflows, or the organization structure. |
| Database storage (GB) | 1 GB, from 4 | $0.25 per month | Workspace database size, including indexes and change tracking, bought per GB. |
| File storage (GB) | 1 GB, from 20 | $0.05 per month | Files, attachments, and generated documents, bought per GB. |
| Retained backups | 1 backup | $3 per month | Keeps one more automatic workspace backup available for restore. |
What is not measured
There is no separate developer fee, per-application fee, or limit on how many entity definitions, properties, permissions, functions, workflows, or document templates a workspace holds. Usage remains subject to the published plan limits and Terms of Service.