> ## Documentation Index
> Fetch the complete documentation index at: https://vms.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Plans reference

> The price, the limits, and the trial of each plan, and the price of each sandbox size.

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.

Ask how many sandboxes I run at a time, how many I start each minute and each day, and which sizes I use.
Tell me the smallest plan in this reference that is sufficient.

## 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.

| Plan | Price each month | Sandboxes at a time | Starts each minute | Starts each day | Saved snapshots | Templates |
| - | - | - | - | - | - | - |
| \$20 plan | \$20 | 150 | 40 | 1,500 | 20 | 20 |
| \$100 plan | \$100 | 400 | 100 | 6,000 | 100 | 100 |
| \$500 plan | \$500 | 1,250 | 200 | 12,000 | 500 | 500 |
| \$2,000 plan | \$2,000 | 2,500 | 300 | 18,000 | 2,000 | 2,000 |

A start costs nothing. Each stopped sandbox above the saved snapshots of the plan costs $0.04 each day. Each [template](https://vms.dev/docs/sandboxes/templates.md) 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.

| Limit | What counts |
| - | - |
| Sandboxes at a time | Sandboxes that are `creating`, `starting`, `running`, or `stopping` |
| Starts each minute | Creates and resumes in the last 60 seconds |
| Starts each day | Creates and resumes in the last 24 hours |

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](#plans) says. A template counts when it is `saving` or `ready`.

A create that answers `503 no_capacity` is not a start.

| Error | Status | When |
| - | - | - |
| `billing_required` | 402 | The workspace has no plan and no trial, a payment review is open, the trial time is used, the credit and the balance are empty after the grace, or the spending limit of the month is reached |
| `size_not_allowed` | 403 | The plan does not include the size. Only the trial has this limit. |
| `start_limit` | 429 | The workspace is at the limit of sandboxes at a time, starts each minute, or starts each day |

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`](https://vms.dev/docs/api-reference/limits/get-the-limits). A key with `sandboxes:read` is enough.

```json theme={null}
{
  "plan": "trial",
  "billingReview": false,
  "sizes": ["small", "medium", "large"],
  "concurrentSandboxes": { "limit": 3, "used": 1 },
  "startsPerMinute": { "limit": 40, "used": 2 },
  "startsPerDay": { "limit": 1500, "used": 5 },
  "savedSnapshots": { "limit": 2, "used": 1 },
  "templates": { "limit": 2, "used": 0 },
  "autoStopSeconds": 14400,
  "trialUnitHours": 60
}
```

`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

| Term | Value |
| - | - |
| Length | 14 days |
| Card | Needed |
| Usage | 60 unit-hours, which is 30 hours of a `medium` sandbox |
| Sandboxes at a time | 3 |
| Sizes | `small`, `medium`, and `large` |
| Automatic stop | Within 4 hours of each start. The default is 1 hour. See [Limits of the trial](https://vms.dev/docs/sandboxes/auto-stop.md#limits-of-the-trial). |
| Saved snapshots | 2 |
| Templates | 2 |
| After the trial | The \$20 plan starts, and Stripe charges the card |
| Number of trials | One for each workspace, and one for each owner |

## 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.

| Size | Units | Price each hour |
| - | - | - |
| `small` | 1 | \$0.017 |
| `medium` | 2 | \$0.034 |
| `large` | 4 | \$0.068 |
| `xlarge` | 8 | \$0.136 |

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](https://vms.dev/docs/reference/health-and-recovery.md#health).

## Credit and balance

| Money | Comes from | Expires |
| - | - | - |
| Credit | The fee of each paid month, and \$1.02 (60 unit-hours) in the trial | One month after the end of the paid month. Trial credit expires when the trial ends. |
| Balance | Top-ups and their bonuses | Never |

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.

| Top-up | Bonus |
| - | - |
| Less than \$100 | 0% |
| \$100 | 2.0% |
| \$200 | 5.8% |
| \$500 | 10.7% |
| \$1,000 | 14.5% |
| \$2,000 | 18.3% |
| \$5,000 | 23.2% |
| \$10,000 and more | 27.0% |

Automatic top-up starts at \$5. After 3 declined top-ups in a row, it turns off.

## Grace and debt

| Plan | When the credit and the balance are empty |
| - | - |
| Paid plan | The workspace keeps running for 48 hours. The balance can go below zero to the debt allowance: 50% of the plan price or \$100, whichever is larger. Then the sandboxes stop with their data kept. |
| Trial or no plan | The sandboxes stop with their data kept. |

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](https://vms.dev/docs/workspace/usage-and-balance.md#cap-the-use-of-each-member).

## Roles

| Action | Owner | Admin | Member |
| - | - | - | - |
| See the plan, the billing info, the cards, the invoices, and the charges | Yes | Yes | Yes |
| Choose a plan, change the plan, or start the trial | Yes | Yes | No |
| Open the billing portal | Yes | Yes | No |
| See the balance and the usage | Yes | Yes | Yes |
| Top up, change automatic top-up, or change the spending limit | Yes | Yes | No |
| Change the member caps | Yes | Yes | No |

See [how billing works](https://vms.dev/docs/explanation/billing.md) for the comparison with boat.dev.

Read the [changelog.](https://vms.dev/docs/changelog.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.