01
What counts as compute time?
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.
00Sandbox0 Cloud pricing
Pay for compute. Keep persistent state.
Compute is billed by the second. The hourly price is an equivalent rate for easy comparison. Retained rootfs data uses the storage rate.
No one-hour compute minimum. Paused sandboxes stop compute charges. Retained state continues to accrue storage by byte-time.
Live pricebook
USDCompute
Billed by the second · ≈$0.000004167/GiB-second
$0.015
/ GiB-hour
Storage
prorated hourly
$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
NETWORK + REQUESTS
$0.00
current rates
01Price ledger
Every meter, in one place.
Compute is billed by the second using the configured memory limit. The GiB-hour rate is an equivalent price. Persistent rootfs data is measured as byte-time.
| 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. | |
| Persistent rootfs | $0.02per GiB-month | Retained rootfs and rootfs snapshot byte-time | |
| 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 |
compute meterstorage metercurrent free meter
02Compare compute prices
Compare compute per GiB-month.
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. Persistent rootfs is billed separately at the rate above.
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
Room to run. Clear guardrails.
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. | |
| Sandbox claims | 5per second | Per team | Burst up to 5 claims. | |
| API requests | 100per second | Per team | Burst up to 200 requests. |
Persistent rootfs has no separate Team Quota. You can request a quota increase for free. Increases are subject to approval; standard usage charges still apply.
View your effective quotas04Worked example
Four GiB. Ten hours. One clear total.
Add 20 GiB of persistent storage retained for a full billing month. Network traffic and object-store requests add no charge 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-month × $0.02
$0.40
Network + requests
Current free rates
$0.00
Example total
No plan fee added to this calculation.
$1.00
05Billing boundaries
The details that affect the total.
02
How is a storage month calculated?
Storage is prorated by the hour using a 730-hour billing month. One GiB retained for a full billing month costs $0.02.
03
Are network traffic and storage operations charged?
No. Ingress is free, egress is temporarily free, and object-store GET and PUT requests have no per-request charge.
04
Can the default quotas be increased?
Yes. You can request a quota increase for free by emailing [email protected]. Increases are subject to approval, and usage is billed at the standard rates. The Dashboard shows the effective limits for your team and region.
06Start with the real rates
Build the sandbox. Keep the state.
Create an account, claim a sandbox, and pay for the memory-time and durable storage you use.