Home / Compute
Sandbox as a Service
sandbox-as-a-service.com/pricingContainer and VM sandboxcompute/sandbox-as-a-serviceJSONcomparereport an errorprovider JSON
- Free allowance
- $5 of signup credit, which the page estimates at about 56 hours of a small sandbox; small is 2 vCPU, 4 GB and 40 GB at $0.09 an hour
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- request-rate$0.09 an hour for small, $0.28 for medium and $0.55 for large; 20 concurrent sandboxes per account; going over returns 429 until one is destroyed
- Evidence
- documented5 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
| Free tier | $5 of signup credit, which the page estimates at about 56 hours of a small sandbox; small is 2 vCPU, 4 GB and 40 GB at $0.09 an hour unit mixed; metered on wall-clock |
|---|
| Price | none stated |
|---|
| Limits | - request-rate (binding) $0.09 an hour for small, $0.28 for medium and $0.55 for large source
- request-rate (binding) 20 concurrent sandboxes per account; going over returns 429 until one is destroyed source
- retention-clamped a sandbox has a 1,440-minute maximum lifetime source
not stated |
|---|
| Identity | email No card is required to sign up; the quickstart signs in with Google and creates an API key. The kind email is inferred from the Google sign-in. |
|---|
| Egress | not stated |
|---|
| Per-object cap | not stated |
|---|
| Retention | not stated |
|---|
| Interface | rest REST API at sandbox-as-a-service.com/v1 with bearer API keys, plus an MCP server; no SDK, CLI or SSH documented |
|---|
| Reliability | no reliability event recorded |
|---|
| Evidence note | documented the pricing page was read on 2026-10-22 and states the credit, the ladder, the concurrency cap and the 1,440-minute lifetime. That lifetime is the wall-clock axis, stated by the vendor in the units it is enforced in |
|---|
| Parsed numbers | |
|---|
Evidence 5
| date | source | what it proved |
|---|
| 2026-10-02 | sandbox-as-a-service.com/pricing | not published |
| 2026-10-22 | sandbox-as-a-service.com/pricing | 'Prepaid credit, charged for exactly as long as a sandbox runs - no minimum, no rounding up, and provisioning time is not billed. No subscription, no seats, no minimum spend. An account with no running sandboxes costs nothing.' with the ladder 'small 2 vCPU 4 GB 40 GB $0.09/hour', 'A 10-minute small sandbox: about $0.015. The $5 of credit you get on signup covers roughly 56 hours', '20 concurrent sandboxes' and '1440 minutes maximum lifetime', quoted |
| 2026-11-03 | sandbox-as-a-service.com/ | the service is reached by REST and an MCP server |
| 2026-11-03 | sandbox-as-a-service.com/pricing | signup needs no card |
| 2026-11-03 | sandbox-as-a-service.com/pricing | the pricing page lists hourly sandbox prices only; no egress allowance or egress price |
More fields 8
| keep rate | 1.0 |
|---|
| billing model | unclassified |
|---|
| shape | {"vcpu": 2,"ram": 4,"disk": 40,"gpu_class": null,"gpu_count": null,"note": "small; medium is 4 vCPU, 8 GB and 80 GB, large is 8 vCPU, 16 GB and 160 GB"} |
|---|
| session cap | {"wall_clock_min": 1440,"idle_reap_s": null,"restart_required": false,"note": "1,440 minutes maximum lifetime per sandbox, and an account with no running sandboxes costs nothing"} |
|---|
| free tier kind | one-time-credit |
|---|
| granularity | {"min_billed_s": 0,"rounding_s": null} |
|---|
| burst x | 1.0 |
|---|
| ps | {"gib": 40,"price": "included in the sandbox size","durability": "sandbox disk","on_stop": true,"on_destroy": false,"retention": "the 1,440-minute lifetime"} |
|---|
Unknown values 9
- chaining: a source was read and is silent on this field
- egress metered: egress metering was not published
- egress terms: a source was read and is silent on this field
- limits note: a source was read and is silent on this field
- per object cap stated: a source was read and is silent on this field
- reliability note: nothing of this kind was observed
- retention notes: the field may be stated in a source that was not read
- retention stated: a source was read and is silent on this field
- tooling: a source was read and is silent on this field