00Sandbox0 Cloud pricing
Compute is billed by the second. The hourly price is an equivalent rate for easy comparison. Retain incremental storage for $0.02/GiB-month, with shared base images excluded.
$5 free credit for eligible new users after adding a credit card.
No one-hour compute minimum. Paused sandboxes incur storage charges only. Keep up to 2,000 paused sandboxes per team by default; request a higher quota for free.
Live pricebook
USDCompute
Billed by the second · ≈$0.000004167/GiB-second
$0.015
/ GiB-hour
Storage
Incremental RootFS · retained memory · shared data counted once
$0.02
/ GiB-month
$0.00 network + request meters
Ingress, egress for now, object-store GET, and object-store PUT.
COMPUTE
$0.015
per GiB-hour
≈$0.000004167/GiB-second · billed by the second
STORAGE
$0.02
per GiB-month
Incremental data · shared base images excluded
NETWORK + REQUESTS
$0.00
current rates
01Price ledger
Compute is billed by the second using the configured memory limit. Retained storage is billed by time and effective incremental data, with shared base images and platform recovery retention excluded.
| Resource | Rate | How it is measured | |
|---|---|---|---|
| Compute | $0.015per GiB-hour | Billed by the second at ≈$0.000004167/GiB-second. Rate follows the running memory limit. | |
| Retained storage | $0.02per GiB-month | Changed RootFS blocks and retained memory checkpoint data, prorated by time over 730 hours. Shared base images, duplicate references, and platform recovery retention are excluded. | |
| Network ingress | Free | Data transferred into a sandbox | |
| Network egress | Freefor now | Data transferred out of a sandbox | |
| Object-store GET requests | Free | No per-request charge | |
| Object-store PUT requests | Free | No per-request charge |
Storage billing
The shared template image is on us. With 100 sandboxes that each keep 100 MiB of independent changes, you retain about 9.77 GiB: about $0.20 for a full 730-hour storage month. There is no full-month minimum.
Shared once. Snapshots and forks share unchanged data within your team. Only additional retained data adds storage.
Platform recovery is on us. Internal recovery checkpoints, maintenance copies, object-store version history and cleanup delays are covered by Sandbox0.
You control retention. Pause to stop compute charges. Delete unneeded sandboxes and snapshots to release their data and stop its storage charges.
Your retained filesystem changes and any saved memory checkpoints are billable. A memory checkpoint is stored process state; your configured running RAM limit is a separate compute measure. Snapshots and forks share unchanged data within your team, and new writes add storage as copies diverge.
Pausing stops compute charges while retained storage continues to accrue. Resuming does not create another billable copy of the same filesystem. Billing stops when the last sandbox, snapshot or fork releases the data, without waiting for physical cleanup. Delete or expire snapshots you no longer need, too.
Storage is prorated by retention time over a 730-hour month. Usage measures persisted changed filesystem blocks before compression, excluding shared base images, encryption and internal indexing overhead. Provisioned disk capacity does not determine your storage bill. Usage may take time to appear; processing delays do not extend the time you pay for.
02Compare compute prices
Every price includes CPU and memory, normalized to 1 GiB of memory running for 730 hours. We divide each allocation’s hourly compute cost by its memory in GiB, then multiply by 730, using public USD list rates.
| Provider / source | Compute / GiB-month | Allocation used for calculation | Plan fee (excluded) |
|---|---|---|---|
| Sandbox0 | $10.95 | 2 vCPU / 4 GiB | No monthly plan fee |
| E2B | $30.22 | 2 vCPU / 4 GiB | Hobby $0; Pro $150/month |
| Daytona | $30.22 | 2 vCPU / 4 GiB | Pay as you go |
| Modal Sandbox | $43.43 | 2 vCPU / 4 GiB | Starter $0; Team $250/month |
| Vercel Sandbox | $15.48 – $62.200–100% active CPU | 2 vCPU / 4 GiB (see note) | Pro from $20/month |
| Cloudflare Sandbox | $6.57 – $24.090–100% active CPU | 2 vCPU / 6 GiB | Workers Paid $5/month |
Checked . Ranges show 0–100% active CPU while memory stays allocated. Other rows use the full requested CPU allocation. Cloudflare uses 2 vCPUs / 6 GiB because of its minimum memory requirement; its total is divided by 6. The other allocations are divided by 4. CPU-to-memory ratios therefore differ. Prices exclude plan fees, credits, discounts, taxes, storage, and network charges, and are rounded to the nearest cent. 730 hours means aggregate runtime across sessions, not a promise of one uninterrupted session. The 1 GiB figure is a comparison unit, not a purchasable instance size or a performance benchmark.
Sandbox0: Compute is billed by the second using configured memory × runtime; hourly rates are equivalents for comparison. No separate CPU charge; CPU limits still apply. Retained incremental storage costs $0.02/GiB-month; shared base images and platform recovery retention are excluded. Pausing stops compute charges.
E2B: Hobby sessions last up to 1 hour; Pro up to 24 hours. Pro's plan fee is additional to usage. Includes 10 GiB storage on Hobby or 20 GiB on Pro.
Daytona: Linux rates. Storage adds $0.000108/GiB-hour after the first 5 GiB free. Enterprise and volume discounts are excluded.
Modal Sandbox: Sandbox-specific rates, with 1 physical core = 2 vCPUs. Billing uses the higher of requested or actual resources. Bursting, region selection, storage, and network can add cost. Plan credits are excluded. Resource billing details.
Vercel Sandbox: iad1 rates. Vercel labels memory in GB; its SDK specifies 2048 MB per vCPU. This comparison treats its advertised 4 GB allocation as 4 GiB, assuming those MB use binary units. CPU charges exclude I/O wait; memory has a 1-minute minimum. Creation, transfer, and storage charges are additional; plan credits are excluded. SDK memory allocation.
Cloudflare Sandbox: Containers rates apply to Sandbox. The example uses a custom 2 vCPU / 6 GiB instance: Cloudflare requires at least 3 GiB per vCPU. CPU is billed only while active. Provisioned disk, Workers, Durable Objects, logs, and egress can add charges; included usage is excluded. Instance constraints.
03Default PAYG quotas
These per-team operational limits are separate from usage billing. They control capacity and admission; they do not add included usage or change the rates above.
| Resource | Default quota | Scope | Notes | |
|---|---|---|---|---|
| Active sandboxes | 20running at once | Per team | Paused sandboxes do not consume active capacity. | |
| Paused sandboxes | 2,000retained | Per team | No paused compute charge; retained storage is billed. At the limit, new sandboxes and forks are blocked; existing compute can still pause. | |
| Sandbox claims | 5per second | Per team | Burst up to 5 claims. | |
| API requests | 100per second | Per team | Burst up to 200 requests. |
Paused sandbox retention has a default quota of 2,000 per team. Existing sandboxes can still pause at the limit. Resume or delete paused sandboxes to free capacity, or request a quota increase for free. Increases are subject to approval.
View your effective quotas04Worked example
Run for ten hours and pause when the work is done. Retain 20 GiB of billable incremental data for one 730-hour storage month. Paused time adds no compute charge. Network traffic and object-store requests are free at the current rates.
4 GiB memory × 10 running hours
Usage receipt
USD
Compute
4 GiB × 10 h × $0.015
$0.60
Storage
20 GiB × 730 h × $0.02/GiB-month
$0.40
Network + requests
Current free rates
$0.00
Example total
No plan fee added to this calculation.
$1.00
05Billing boundaries
Yes. Eligible new users receive a one-time $5 usage credit after Stripe confirms a saved credit card. Each user and team can receive the welcome credit once. Adding a card makes no charge and does not enable automatic recharge. After the credit is used, add prepaid funds to continue.
Compute is billed by the second using the sandbox memory limit and running time. The GiB-hour price is an equivalent rate for comparison, not a one-hour minimum. Paused sandboxes stop accruing compute charges.
Pausing stops compute charges. Retained incremental RootFS data and memory checkpoints cost $0.02/GiB-month, prorated over 730 hours. Snapshot and fork references to the same data are counted once within a team. Shared base images and platform recovery retention are excluded. Each team can retain 2,000 paused sandboxes by default and request a higher quota for free. At the limit, new sandboxes and forks are blocked. Existing sandboxes can still pause, resume, or be deleted, so pausing can temporarily exceed the limit. Resuming is subject to active capacity and available compute credit.
No. Ingress is free, egress is temporarily free, and object-store GET and PUT requests have no per-request charge.
Yes. You can request a quota increase for free by emailing [email protected]. Increases are subject to approval. Running compute and retained incremental storage are billed; pausing stops compute charges. The Dashboard shows the effective limits for your team and region.
06Start with the real rates
Create an account, claim a sandbox, and pay for running compute and the incremental data you keep.
