Skip to main content
This reference gives the price and the limits of each plan, the trial, and the price of each sandbox size.

Find the plan that fits my workload.

Plans

Each plan costs a fixed price each month. The fee comes back as usage credit. Unused credit carries over for one month. Members are free, and each plan allows each size. A start costs nothing. Each stopped sandbox above the saved snapshots of the plan costs $0.04 each day. Each [template](/sandboxes/templates) above the templates of the plan also costs $0.04 each day. Each charge comes out of the credit or the balance one time each day (UTC), and counts toward the spending limit. Data of a stopped sandbox stays 30 days. A template has no expiry date.

Limits

Each create checks the limits of the plan. A create above a limit makes no sandbox and costs nothing. The saved snapshots and the templates of the plan are not limits. A stopped sandbox or a template above them is not refused. It costs $0.04 each day, as Plans says. A template counts when it is saving or ready. A create that answers 503 no_capacity is not a start. For too many starts, the start_limit error has retryAfterSeconds and a Retry-After header: the time until the oldest start leaves the minute or the day. At the limit of sandboxes at a time, the error has no retryAfterSeconds. Stop or delete a sandbox, then try again. Read the limits and the current use with GET /v1/limits. A key with sandboxes:read is enough.
plan is trial, plan-20, plan-100, plan-500, plan-2000, or null. With no plan, sizes is empty and each limit is 0.

Trial

Sandbox sizes

One capacity unit is 2 vCPU, 4 GiB of RAM, and 40 GiB of disk. Usage costs $0.017 for each unit-hour, by the second. Billing starts when the sandbox is running. These states cost nothing: creating, starting, stopping, stopped, error, failed, a sandbox with health: unreachable, and a stop that fails with snapshot_failed and tries again. A sandbox with health: degraded is billed, and so is a stop that fails with agent_unreachable. See Health and recovery.

Credit and balance

Usage takes the credit first, then the balance. The usage of each minute comes out of the credit or the balance in the next minute. When a plan ends and the balance has money, running sandboxes keep running on the balance.

Top-ups

A top-up is $5 to $100,000. From $100, a top-up gets a bonus: 2% + 12.5% × log10(top-up ÷ $100), at most 27%. Automatic top-up also gets the bonus. Tax is on top of the amount when it applies. Automatic top-up starts at $5. After 3 declined top-ups in a row, it turns off.

Grace and debt

After the stop, a create or a resume answers 402 billing_required until a top-up.

Spending limit

The spending limit is the most that a workspace can spend on usage in one month (UTC). The owners and admins get an email at 50%, 80%, and 100%. At 100%, the running sandboxes stop with their data kept, and a create or a resume answers 402 billing_required.

Member caps

An owner or an admin can cap each member: the sandboxes at the same time, and the unit-hours each month. A start above a cap answers 429 start_limit. A sandbox counts for the person who created it. For a sandbox that an API key created, that is the person who created the key. See Cap the use of each member.

Roles

See how billing works for the comparison with boat.dev.