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

# How billing works

> How the plan, the trial, and the usage credit of a workspace work, and how the terms compare with boat.dev.

A workspace pays for one plan each month. The plan sets the limits of the workspace, and its fee comes back as credit for sandbox time.

Explain the billing of my workspace.

Explain how the plan, the trial, and the usage credit work.
Use the plans reference for the exact values.

## The workspace pays, not each person

The workspace is the Stripe customer. One invoice each month pays for the plan. Members are free, and the price does not change when the team grows.

Owners and admins choose the plan and open the Stripe billing portal. Each member can see the plan, the invoices, and the charges.

## The fee comes back as credit

Each month, the plan fee comes back as usage credit. Sandbox time uses the credit by the second, at the price of the size. Unused credit carries over for one month.

The plan also sets the limits: how many sandboxes run at a time, and how many start each minute and each day. A start costs nothing. Each plan allows each size, `xlarge` included.

## Usage takes the credit, then the balance

Each running second of a sandbox costs the price of its size. A sandbox that starts, stops, or fails costs nothing, and so does a sandbox that is unreachable because of a problem on our side. The usage of each minute comes out of the credit first, then out of the prepaid balance.

Top-ups add to the balance, and from \$100 they get a bonus of up to 27%. Automatic top-up adds money when the funds go below a limit, so that the sandboxes do not stop. A monthly spending limit stops the running sandboxes and new starts, so that a runaway agent cannot spend more than you planned.

When the credit and the balance are empty, a workspace with a paid plan keeps running for 48 hours, with a small debt allowance. A card problem does not stop your work at once. See [grace and debt](https://vms.dev/docs/reference/plans.md#grace-and-debt).

## The trial needs a card

The trial lasts 14 days. It gives 60 unit-hours, 3 sandboxes at a time, and sizes up to `large`. The card stops one person from starting many trials. Each workspace and each owner gets one trial.

At the end of the trial, the \$20 plan starts. To stop before that, cancel in the billing portal.

## Comparison with boat.dev

These terms come from boat.dev in November 2026.

| Term | VMS | boat.dev |
| - | - | - |
| `small` each hour | \$0.017 | \$0.018 |
| `xlarge` each hour | \$0.136 | \$0.200 |
| Billing starts | When the sandbox is `running` | When a machine is assigned |
| Plan fee | Comes back as credit, carries over one month | Comes back as time, does not carry over |
| Sandboxes at a time on the \$20 plan | 150 | 100 |
| Starts each minute on the \$20 plan | 40, at no cost | 12, extra starts cost money |
| `xlarge` | On each plan | Needs the \$100 plan |
| Team members | Free | Each seat pays the plan price |
| Trial | 14 days, 60 unit-hours, 3 sandboxes | 7 days, 25 hours, 2 sandboxes |
| Top-ups | From $5, bonus from $100, up to 27% | From $15, bonus from $200, up to 25% |
| Automatic top-up | From \$5, also in the trial | From \$15, not in the trial |
| Empty balance | 48 hours of grace, debt to 50% of the plan or \$100 | 24 hours of grace, debt to 25% of the plan or \$50 |
| Saved snapshots on the \$20 plan | 20 | 10 |
| Templates on the \$20 plan | 20, with no expiry date | Counted as saved snapshots |
| Each extra snapshot or template each day | \$0.04 | \$0.056 |
| Stopped data | 30 days | 14 days |

See the [plans reference](https://vms.dev/docs/reference/plans.md) for each value.

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


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