Home / Compute
Superserve
superserve.ai/pricingContainer and VM sandboxcompute/superserveJSONcomparereport an errorprovider JSON
- Free allowance
- Free with $100 of credit, pay-as-you-go after it, up to 20 concurrent sandboxes and no time limit on a sandbox
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- request-rateup to 20 concurrent sandboxes on Free, 1,000 on the paid tier
- 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 | Free with $100 of credit, pay-as-you-go after it, up to 20 concurrent sandboxes and no time limit on a sandbox unit mixed; metered on wall-clock |
|---|
| Price | none stated |
|---|
| Limits | - request-rate (binding) up to 20 concurrent sandboxes on Free, 1,000 on the paid tier source
not stated |
|---|
| Identity | email (placeholder) not published |
|---|
| Egress | not published: the pricing page lists compute, memory and retained-storage rates only and says estimates exclude network charges; no transfer allowance or per-GB price is stated |
|---|
| Per-object cap | not stated |
|---|
| Retention | not stated |
|---|
| Interface | rest, cli REST API, the @superserve/cli CLI and a TypeScript SDK; no SSH found in the docs read |
|---|
| Reliability | no reliability event recorded |
|---|
| Evidence note | documented the pricing page was read on 2026-10-22. The page states 'No time limit on sandboxes', which is the wall-clock axis, and 20 concurrent sandboxes is the bound |
|---|
| Parsed numbers | |
|---|
Evidence 5
More fields 5
| keep rate | 1.0 |
|---|
| billing model | unclassified |
|---|
| session cap | {"wall_clock_min": null,"idle_reap_s": null,"restart_required": false,"note": "'No time limit on sandboxes', quoted; the page states no reap"} |
|---|
| free tier kind | one-time-credit |
|---|
| burst x | 1.0 |
|---|
Unknown values 8
- chaining: a source was read and is silent on this field
- egress metered: egress metering was not published
- 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