Plans & limits
Boardwalk is free to start on: author a workflow, validate it with boardwalk check, deploy it to your org on the Free plan, and run it hosted on a monthly allowance with no card. A subscription raises the allowances and adds self-hosted runners attached to the hosted control plane. This page is the reference for what each plan includes and how the limits behave; prices and per-unit rates live on the pricing page.
The plans
| Free | Solo | Pro | Team | Enterprise | |
|---|---|---|---|---|---|
| Price | $0 | $20/mo | $100/mo | $40/member/mo | Custom |
| Members | Up to 3 | 1 (just you) | 1 (just you) | Unlimited, every member billed | Volume-tiered |
| Hosted runs | Yes, on a monthly allowance | Yes | Yes | Yes | Yes |
| Compute-hours / month | 2 | 25 | 150 | 25 per member, pooled | Committed |
| Managed tokens / month | $2 at cost | $20 at cost | $100 at cost | $40 per member, pooled | Committed packs |
| Web searches / month | 50 | 500 | 2,000 | 1,000 per member, pooled | Metered |
| Concurrent hosted runs | 1 | 3 | 10 | 3 per member, pooled | Dedicated capacity |
| Storage | 5 GB (hard cap) | 20 GB | 100 GB | 100 GB + 25 GB per member | Custom |
| Self-hosted runners | None | 1 | 3 | 10 per org | Negotiated |
| Governance | Roles + audit log | Roles + audit log | Roles + audit log | + require-2FA, email domain policy | + SSO/SAML, SCIM, custom retention |
Solo and Pro are single-member plans. The moment an org adds anyone else it moves to Team, where every member is billed regardless of role and allowances pool org-wide. Enterprise adds committed usage packs, a self-managed deployment option, dedicated capacity, and named support with an SLA; talk to us.
Allowances & the monthly reset
Every paid plan includes monthly allowances: compute-hours, a managed-token pool, web searches, and storage. Two semantics to know:
- They reset monthly, on your billing anniversary. Each allowance refills in full at the start of each billing cycle and unused amounts never roll over. Prepaid credits are separate and never expire.
- You always see them in real units. The dashboard and
boardwalk usageshow gauges like "14.2 of 25 compute-hours" and "$3.10 of $20 managed tokens", plus the date the allowances reset. There are no rolling windows and no abstract percentages.
| Allowance | How it draws |
|---|---|
| Compute-hour | One hour of active run time on a standard 1-vCPU runner. Larger machines draw the allowance proportionally: an hour on a 4-vCPU machine uses 4 compute-hours, matching the per-vCPU compute meter. Suspended time (a long sleep, a human-input gate, waiting on a child run) releases the machine and draws nothing. |
| Managed-token pool | Draws at the model's at-cost rate. Bring-your-own inference keys bypass the pool entirely and cost $0 from Boardwalk on every plan. |
Concurrency & queueing
Each plan caps how many hosted runs execute at once: 3 on Solo, 10 on Pro, and 3 per member pooled org-wide on Team. The cap never fails a run:
- A run that starts while the org is at its cap queues and starts automatically when a slot frees, in FIFO order.
- A resumed run (waking from a sleep or an answered human-input gate) takes priority over queued new starts, so a workflow that suspended never gets stuck behind its own backlog.
- Queued runs are visible in the dashboard with their queue position; nothing errors and nothing is dropped.
Triggers on every plan
Cron schedules, webhooks, and workflow-to-workflow triggers deploy and fireon every plan, including Free. Nothing is held back behind a subscription: a Free org's cron runs on its schedule and its webhooks accept deliveries the moment they exist. What bounds a Free org is its monthly allowance, checked when a run starts, not a paused trigger.
- Downgrade or a lapsed subscriptiondoes not pause anything. Cron schedules keep their slots, webhooks keep accepting deliveries, and a webhook's signing secret is never invalidated. What changes is the allowance: the org falls back to the Free allowance, and runs are bounded by it the same way any Free org's are. Nothing is deleted, and run history stays.
- What a smaller allowance feels like is a run that does not start once the allowance is spent, reported against your balance rather than as a disabled trigger. Add credits or resubscribe and the next run starts; you never redeploy.
Spend caps
You can set an optional org spend cap: a ceiling on overage spend per billing cycle. A run that would start past the cap does not start until you raise the cap or the cycle resets, and the block links straight to the setting. It is the guarantee that a runaway loop can cost at most what you signed up for. An individual API key can carry its own monthly spend cap too, bounding one credential the same way; see machine access.
Overage, credits & the fee
When an allowance runs out, the same usage keeps working as overage, drawn from prepaid credits at the public rates, identical on every plan (full tables on the pricing page):
| Meter | Overage rate |
|---|---|
| Compute | $0.05 per vCPU-minute |
| Managed tokens | The model's source cost |
| Storage | $0.25 per GB-month |
| Web search | $0.008 per search |
- Usage carries no markup. The only fee is 10% on a prepaid credit top-up: a $50 top-up costs $55 and adds $50 of credit. It covers card processing and the upstream credit fee on routed tokens, which is what keeps per-model rates at cost.
- Purchased credits never expire, and when they run out, runs stop rather than producing a surprise bill.
- The Free plan runs hosted on a comped allowance and never bills on its own: its 5 GB storage is a hard cap, and when the monthly allowance is spent, runs stop. A Free org that wants to keep going can buy credits like any other, drawn at the same public rates.
Self-hosted runner limits
Paid plans include self-hosted runners: your machines attached to the hosted control plane.
| Plan | Included runners |
|---|---|
| Free | None |
| Solo | 1 |
| Pro | 3 |
| Team | 10 per org |
| Enterprise | Negotiated |
Registering a runner past the plan's cap is rejected at registration. Billing follows where the work happens: compute on your own runners is never billed and draws no compute-hours, while brokered usage the run makes through the control plane (managed tokens, artifact storage, web search) bills normally against allowances and credits. For running the whole platform on your own infrastructure with no account and no plan, see the open-source engine.