Free
Trying it on a real workflow before deciding anything.
$0
No card. One seat.
One workspace, enough to run something real and see the traces.
Start freeRestoring durable state…
Every limit below is the value the platform actually enforces — the same rows the API reads when it decides whether to accept a run. Free is a working workspace, not a time-limited trial.
Trying it on a real workflow before deciding anything.
$0
No card. One seat.
One workspace, enough to run something real and see the traces.
Start freeOne engineer running agent workflows in production.
$49/mo
Per month. Single seat — buy Team for more people.
A working individual: delegation, replay, MCP tools, the API.
Start free, upgrade laterA team sharing workspaces, and the only plan with agent teams.
$99/mo
Per seat, per month.
Teams of agents and teams of people, with priority scheduling.
Start free, upgrade laterLonger retention, higher ceilings, and a signed agreement.
Custom
Custom.
Custom limits, dedicated support, and a contract.
Book a demo“Unlimited” means the plan record carries no ceiling. A dash means zero, and zero is a real zero — a plan showing a dash for agent teams cannot save a team, and the API says so with that number in the refusal.
| Free | Pro | Team | Enterprise | |
|---|---|---|---|---|
| Runs per monthAcross the whole account. | 500 | 10,000 | 50,000 | Unlimited |
| Runs per month, per workspaceSo one workspace cannot drain the account's month. | 500 | 5,000 | 20,000 | Unlimited |
| Tokens per monthCounted, not estimated. | 1M | 50M | 250M | Unlimited |
| Agent minutes per monthTime an agent spends working. Waiting on an approval is not charged. | 60 min | 1,500 min | 10,000 min | Unlimited |
| Workspaces | 1 | 3 | 10 | Unlimited |
| Members per workspace | 3 | 5 | 25 | Unlimited |
| Concurrent runsPer workspace. | 2 | 5 | 15 | 50 |
| AgentsRegistered agents per workspace. | 3 | 25 | 100 | Unlimited |
| Agent teamsA roster on the canvas, with per-member delegation grants enforced in the runtime.Built, but off by default in this deployment. Behind a runtime switch (AGENT_TEAMS_ENABLED) that is off by default. The canvas shows the node and says so; ask us before you buy Team for this. | — | — | Included | Included |
| Delegation between agentsAn agent may hand work to another on its roster, within a depth limit.Built, but off by default in this deployment. Behind a runtime switch (AGENT_ACTIVATIONS_ENABLED) that is off by default. | — | Included | Included | Included |
| Agents in a teamChecked at save, not at run. | — | 3 | 8 | 25 |
| Levels of delegationA transfer is a tail call and does not count. | — | 1 | 3 | 5 |
| Replay a runRe-executes from the recording. No provider calls, no cost, no side effects. | — | Included | Included | Included |
| MCP toolsTools discovered from an MCP server. | — | Included | Included | Included |
| API accessAPI keys, scoped to a workspace. | — | Included | Included | Included |
| API keysLive keys per workspace. | — | 5 | 25 | Unlimited |
| OpenTelemetry exportSpans pushed to your own collector.Built, but off by default in this deployment. Behind a runtime switch (OTEL_TRACE_EXPORT_ENABLED) that is off by default. Traces are recorded and visible in the product either way — this row is only about the export. | — | — | Included | Included |
| Run historyAfter this, the rows are DELETED, not hidden. | 7 days | 30 days | 90 days | 365 days |
| Event historyThe timeline a run is debugged from. | 7 days | 30 days | 90 days | 365 days |
| Trace historySpans, which are larger and kept for less time. | 3 days | 14 days | 45 days | 180 days |
| Payload historyRequest and response bodies. The most expensive to keep. | 7 days | 14 days | 30 days | 90 days |
| Support | Community | Priority | Dedicated |
We publish no uptime figure and offer no SLA, because we have neither. We hold no SOC 2 or ISO 27001 certification and no audit has been performed. We publish no latency or throughput benchmark, because none has been measured under conditions worth quoting. If any of those decides your purchase, the answer today is no — say so and we will tell you when it changes.
Data past its window is DELETED from the database, not hidden behind a filter. There is no flag to flip that brings it back. A downgrade is honoured at the old window for a grace period before the shorter one starts deleting, so a plan change does not remove history before you have seen a warning.
Entitlements resolve from your billing account's plan code, which billing only ever writes. No quota check calls a payment provider, so a provider outage cannot stop a run. A past-due account is restricted; its plan code — and therefore its retention — does not change, because a late card must never delete a customer's data.
Limits resolve from the workspace's billing account, never from the person acting. A Pro member working inside a Free workspace gets Free's limits, at every enforcement point. Guests are held to their own per-member cap, and an API key inherits that cap rather than escaping it.