Sandbox pricing and plans

Sizes and prices

Size	vCPU	Memory	Disk	Per hour
small (default)	1	2 GiB	10 GiB	$0.05
standard	2	4 GiB	20 GiB	$0.10
large	4	8 GiB	40 GiB	$0.20
xl	8	16 GiB	80 GiB	$0.40

• A sandbox costs $0.05 per vCPU an hour, with 2 GiB of memory per vCPU.
• A running sandbox is billed by the minute, with a one-minute minimum.
• A sandbox keeps the price it started at until it stops. It pays the current price from its next start.
• A stopped sandbox is billed 6¢ per GiB a month for the data it changed, after the stopped storage the plan includes. The operating system it started from is not counted.
• Usage from all sandboxes in an org is added up before it is charged, so ten 5-minute sandboxes cost the same as one 50-minute sandbox.
• Sandboxes use the same credit as runs and models. The Billing page shows sandbox spend separately.
• The price per hour is the same on every plan.

Plans

	Pay as you go	Personal	Team	Platform
Per month	$0	$20	$150	$500
Sandbox usage included each month	none	$20	$100	$300
vCPUs across running sandboxes	2	64	512	4,096
Sandboxes, running or stopped	25	100	1,000	20,000
Stopped storage included each month	25 GiB	25 GiB	250 GiB	1 TiB
Seats	2	2	unlimited	unlimited

• Every plan has no limit on how long a sandbox runs.
• Included usage is spent on sandboxes before paid credit. It is not spent on runs or models, and it does not carry over to the next month.
• Included stopped storage is counted in GiB-months per calendar month (UTC). 25 GiB stopped for a whole month costs nothing. 50 GiB stopped for half a month also costs nothing.
• On pay as you go, add credit on the Billing page. The first top-up is at least $10. Pay as you go runs 2 vCPUs at once, so a large or xl sandbox needs a plan.
• Change the plan on the Plan page in the dashboard, at app.divergentlabs.xyz/plan, or with plan <name> at the ssh div.io prompt. A change between paid plans is prorated.
• For more than Platform allows, contact us.

Limits

Limit	What counts	When reached
vCPUs	vCPUs of running sandboxes. A stopped sandbox uses none.	New and resumed sandboxes are rejected with sandbox_quota_exceeded.
Sandboxes	Running and stopped sandboxes.	New sandboxes and forks are rejected with sandbox_limit.
Seats	Members and open invitations.	New invitations are rejected with seat_limit.

• These limits are separate from the GPU and container limits for runs.
• Moving to a smaller plan does not stop anything already running. What does not fit is rejected after that.
• When the org reaches its usage limit, or runs out of credit with no card on file, its running sandboxes are stopped. They are never deleted. Resume them when you are ready.
• Run div limits to see what the org uses against its plan.