Skip to main content

Pricing and credits

Processita bills usage in credits, tracked separately for each tenant. This page explains what costs credits, what doesn't, and where to free credits come from.

What's free​

  • Every read-only request (listing or viewing models, process instances, tasks, logs, the dashboard) costs nothing, no matter how often you call it.
  • Claiming a service task job (POST /service-task-jobs/claim) costs nothing unless it actually claims a job — a poll that finds nothing pending is free, since this endpoint is designed to be called repeatedly while waiting for work to appear.

API request volume itself is never billed — if you're worried about calling the API too often, that's governed by a separate rate limit, not your credit balance.

What costs credits​

Every other action that changes something — starting a process instance (manually, via a call activity, or from a timer start event firing on its own schedule), completing a task, sending a message, broadcasting a signal (charged once per broadcast, regardless of how many instances it notifies or starts), completing/failing a service task job, extending a job's lock, moving or retrying a token, updating an instance's variables, cancelling an instance, or saving a model — costs 1 credit, charged the moment that action happens.

On top of that one credit, if the action causes the process engine to automatically advance through further steps on its own (for example, a gateway deciding a branch, or a chain of automatic tasks running back-to-back before the next thing that needs to wait), each of those automatically-advanced steps costs 1 additional credit. A short process that only has a couple of steps barely costs anything beyond its starting action; a long straight-line process that walks through many steps in one go costs proportionally more — you're billed for how much work the engine actually did, not just for the one action you took.

A timer start event firing a new instance on its own schedule is billed exactly the same way as starting that instance yourself — there's no separate "free" tier for automatic triggers.

Where your credits come from​

On the first day of each calendar month, every tenant's balance is automatically topped up to 1000 free credits — no action needed. If a tenant's balance is already at or above 1000 (for example, an idle tenant that never spent last month's top-up), nothing is added; credits don't stack or accumulate past that ceiling.

If a tenant needs more than its monthly allowance, a superadmin can add credits manually at any time.

Running out​

If a tenant's balance reaches zero, what happens next depends on how the next step would be triggered:

  • Anything you do directly — starting an instance, completing a task, completing/failing a service task job, updating variables, and so on — is rejected immediately with a clear error. Nothing is attempted.
  • A process the engine is already running on its own — a gateway deciding a branch, a chain of automatic tasks, a timer start event firing on schedule — doesn't error out. It simply stops making progress and stays exactly where it is, with no error anywhere, until the balance is topped up.

Either way, reads keep working as normal, and nothing already running is interrupted mid-step. The balance resumes as soon as credits are added, whether that's the next monthly grant or a manual top-up — a process that was stuck on auto-advancement for lack of credits picks back up on its own, no restart needed.

A tenant's balance never goes below zero. If a cascade of auto-advanced steps is already in progress when the balance reaches zero (it's only re-checked periodically, not after every single step), the steps that would have pushed the balance negative are simply free rather than putting the tenant in debt — the credit ledger still records the full cost of the work that was actually done, it just shows the running balance floored at 0 for that entry.

Seeing where your credits went​

Every credit-consuming (and -granting) event is recorded in your tenant's credit ledger — a plain, readable list ("Task 'Approve invoice' completed on 'Invoice approval' — 4 credits", and so on) showing exactly what each charge was for, when it happened, and your running balance afterward. It's reachable from the sidebar's Credits item, and from the Dashboard's "Credits consumption per day" chart.