Documentation
Sandbox limits and billing
Sizes, lifetime, running and session limits, and how sandbox compute is billed.
Sizes and lifetime
- Sizes are 2vcpu-8gb and 4vcpu-16gb. The list response names the sizes your environment offers.
- The workspace disk is 5 to 64 GiB, 20 GiB by default.
- Each sandbox lasts eight hours from its first start and cannot be extended.
- A workspace can run 2 sandboxes at once by default. The list response shows your limit as max_running.
Commands and terminals
- Up to 4 commands and 2 terminals run in one sandbox at a time.
- A command times out after 300 seconds by default, and at most 3600. A command still running 30 seconds past its timeout is cancelled with exit code 124.
- Command output is capped at 8 MiB. Past that the command ends with exit code 137 and is marked truncated.
- A terminal closes after 30 minutes with no input or output.
Billing
A running sandbox uses unit-minutes from your workspace allowance or prepaid credit, at the runner rate of its size: 2 vCPU counts 1x and 4 vCPU counts 2x. A stopped sandbox is not billed, and a start that never reaches running charges nothing.
Each start reserves 15 minutes ahead and adds more while the sandbox runs. When a run ends, only the seconds it ran are charged. credits_used shows the charge so far, including the current run.
Without credit, create and start are refused with credit_exhausted. If credit runs out while a sandbox runs, the sandbox fails with credit_exhausted and stops. Its files stay, and you can start it again after adding credit.