01
What counts as compute time?
Compute is the sandbox memory limit multiplied by running time. It is not based on observed memory use or host oversubscription. Paused sandboxes stop accruing compute charges.
00Sandbox0 Cloud pricing
Pay for compute. Keep persistent state.
Two usage rates in USD. Running sandbox memory is compute; retained rootfs data uses the storage rate.
Paused sandboxes stop compute charges. Retained state continues to accrue storage by byte-time.
Live pricebook
USDCompute
only while running
$0.02
/ 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.02
per GiB-hour
STORAGE
$0.02
per GiB-month
NETWORK + REQUESTS
$0.00
current rates
01Price ledger
Every meter, in one place.
Compute follows the configured memory limit, not observed usage. Persistent rootfs data is measured as byte-time.
| Resource | Rate | How it is measured | |
|---|---|---|---|
| Compute | $0.02per GiB-hour | Running sandbox memory limit × runtime | |
| 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
02Default 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 | 100running 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. Approved team-specific overrides can raise a default limit.
View your effective quotas03Worked 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.02
$0.80
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.20
04Billing 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. The published quotas are standard PAYG operational guardrails, not included usage. Approved team-specific overrides may differ, and the Dashboard shows the effective limits for your team and region.
05Core platform upgrade
Build the sandbox. Keep the state.
Cloud sign-in and new account creation are temporarily paused during an upgrade to the platform’s underlying infrastructure and core capabilities. Pricing remains available for planning.