Cloud runs
Sandbox time and plans
Local runs with the CLI are free and unlimited: they are never metered and never count against a plan. On workbenches.dev only cloud sandbox time is metered. Model tokens are your own, on your OpenRouter key, and never appear on the workbenches.dev bill. Runs on your own workers record no sandbox time.
Plans#
| Plan | Price | Members | Sandbox-hours a month | Private Workbenches | Past the included hours |
|---|---|---|---|---|---|
| Free | $0 | 1 | 5 | 3 | Cloud runs stop until you upgrade. |
| Pro | $29.99 a month | 5 | 50 | Unlimited | $1.50 per sandbox-hour, up to your spend limit. |
| Enterprise | Contact us | Custom | Custom | Custom | Custom limits and terms. |
Organizations already on an earlier plan version keep it: Pro at $49 with 75 hours, and Team at $299 with 25 members and 400 hours. A shipped plan version never changes; a new price ships as a new version.
See the pricing page for the current offer.
What a sandbox-hour is#
A sandbox-hour is one hour of the standard cloud sandbox, 2 vCPU and 4 GiB, metered per second. Larger sandboxes use hours faster in proportion to their cost:
weight = (vCPU x $0.0504 + GiB x $0.0162) / (2 x $0.0504 + 4 x $0.0162)4 vCPU and 8 GiB counts 2 hours per hour. 1 vCPU and 2 GiB counts half an hour. A size the sandbox did not report counts as standard. A sandbox's size comes from the Workbench's requirements (cpu, memory_gb, disk_gb); without them it is 2 vCPU and 4 GiB.
The time is the sandbox's measured lifetime. A lingering preview window is billed for the time it stays open. Runs still in progress are not counted until they end.
The period#
The allowance resets with your subscription period. Free and complimentary organizations use UTC calendar months.
Starting a run#
When a run is created:
- A payment method must be on file, even within the free hours.
- Within the included hours, the run starts.
- Past them, Free refuses. A paid plan with an active subscription keeps running until overage reaches the spend limit.
- The run's time limit, the default 60 minutes included, must fit in the sandbox time still available: the included hours not yet used, plus the hours the spend limit still pays for when overage is sold and the subscription is active.
A refusal is status 402 with code plan_limit and a message that names the limit and how to raise it. The message reaches the CLI and the MCP tools unchanged. For a time limit that does not fit, the message names the minutes requested and available.
The check counts only time already used, so concurrent runs may overshoot by up to their limits. A run is billed for the sandbox time it uses, not the limit it asked for. Every run, on every plan, is capped at 1440 minutes.
The spend limit#
Overage is capped by a monthly spend limit, $50 by default. Owners and admins can change it on the billing page. When it is reached, cloud runs pause until next month or until the limit is raised.
Other limits#
- Members. The member cap counts members and live pending invitations. Accepting an invitation is refused when the organization is at the cap.
- Private Workbenches. Pushing a Workbench that does not exist yet is refused at the cap. New versions of existing Workbenches are not.
- Nothing is deleted. State already over a cap, such as after a downgrade, is never removed. A cap only blocks new additions.
Billing page#
Owners and admins manage billing on the billing page in the dashboard: upgrade, add a card, switch plans, set the spend limit, and open the Stripe customer portal for cards, invoices, and cancellation at the period end. Every member sees the plan, hours used and remaining this period, overage, spend limit, and member and private Workbench counts.
A switch to a more expensive plan applies at once and invoices the prorated difference; the amount is shown for confirmation first. A switch to a cheaper plan takes effect at the end of the period. A cancelled subscription returns the organization to Free.
The same actions are available in the API: see Billing.