Runtime vs Superserve
Choose Runtime for cost-sensitive agent workloads with many short runs, where active-CPU billing and a free monthly allowance matter; choose Superserve for long-running coding and personal agents that need a persistent VM with pause, forks and brokered credentials. Runtime uses Firecracker microVM isolation; Superserve uses Firecracker microVM isolation.
Key differences between Runtime and Superserve
- Session length: No limit documented (Runtime) versus Unlimited (Superserve).
- SDKs and interfaces: Only Runtime lists Go, Ruby and Java.
What they have in common
- Both companies are based in the United States.
- Both are hosted platforms.
- Both use microVM isolation.
- Neither is open source.
- Both support snapshots.
- Both can pause and resume a sandbox.
- Both list TypeScript, Python, CLI, REST API and MCP server.
Runtime vs Superserve at a glance
| Attribute | Runtime | Superserve |
|---|---|---|
| What it is | Firecracker microVM sandboxes billed on active CPU at $0.025 per vCPU-hour, with pause that keeps memory, forks, SDKs in five languages and no plan fee. | Persistent Firecracker microVM sandboxes for long-running agents, with pause/resume, memory-and-disk snapshots, forks and a credentials broker that keeps secrets out of the sandbox. |
| Type | Hosted platform | Hosted platform |
| Isolation | Firecracker microVM with its own Linux kernel, disk and memory per sandbox, on dedicated servers Runtime operates | Firecracker microVM per sandbox |
| Open source | No | No |
| Self-host / BYOC | Not documented / Not documented | Not documented / Yes |
| SDKs | JavaScript/TypeScript, Python, Go, Ruby, Java, CLI, REST API, MCP server | Python, JavaScript/TypeScript, CLI, REST API, MCP server |
| Cold start (vendor claim) | Runtime measures create and exec from outside every one to five minutes and publishes p50/p95/p99 on its speed page; the September 2026 figures were taken down on 27 October 2026, so no current figure is published | Docs: sandboxes spin up "in seconds"; no figure published |
| Max session | No maximum documented; a sandbox pauses itself after 300 seconds of inactivity by default (idlePauseSeconds 60–86,400, or 0 for never) | Unlimited runtime on Developer and Pro plans; optional auto-pause cap on active time and an idle timeout of 60 s to 7 days |
| Persistence | Pause keeps memory and processes; paused sandboxes are kept while the account has credit or for 1–365 days as set (30 days after credit runs out with a card or prior top-up, 7 days otherwise); snapshots of running or paused sandboxes; forks of 1–10 running copies with memory and processes; volumes backed up daily; S3, R2 and GCS bucket mounts | Pause snapshots memory and disk and suspends the VM; paused sandboxes are kept indefinitely by default (optional auto-delete up to 30 days); snapshots of memory and disk can be forked into new sandboxes and persist until deleted |
| Snapshots / pause | Yes / Yes | Yes / Yes |
| GPU | Not documented | Not documented |
| Networking | Per-sandbox allow and deny lists, or internet off; sandboxes reach only the public internet, private addresses refused; HTTPS previews on runtimehost.com (private by default with rotatable tokens), custom domains, public TCP ports, WireGuard private networks and a dedicated outbound IPv4 ($5 per 30 days); secrets substituted by the host on outbound requests | Egress allow/deny rules by CIDR or domain; per-sandbox network log of HTTP/HTTPS connections; preview URLs with public or per-port authenticated access; secrets are bound to a sandbox and injected by a proxy on outbound calls so credentials never enter the VM |
| Pricing | $0.025 per active vCPU-hour and $0.0075 per reserved GiB-hour, billed per second; a waiting sandbox bills memory plus a 0.05 vCPU floor; paused sandboxes, snapshots and images $0.08 per GB per 30-day month; volumes about $0.11 per GiB per 30 days; outbound traffic free to 100 GiB a month then $0.02 per GB; no plan, seat or minimum fee | Usage on every plan: $0.0504 per vCPU-hour and $0.0162 per GiB-hour, billed per second while running; storage $0.000108 per GiB-hour for retained data including paused sandboxes. Developer $20/month (includes $20 usage, 100 concurrent, 4 vCPU/16 GiB max); Pro $250/month (includes $250 usage, 2,000 concurrent, 16 vCPU/64 GiB max); Enterprise custom |
| Free tier | 100 free hours of a 1 GB machine (100 GiB-hours of memory, 25 vCPU-hours of active CPU) in the first 30 days with no card, renewing monthly once the account has paid; without credit up to 4 sandboxes at once of 2 vCPU and 4 GiB | Limited free trial for a first sandbox, no card required (amount not stated) |
| Compliance | No certification of Runtime itself is named; the trust page lists subprocessor attestations (Virginia data centre SOC 1/2/3 Type 2 and ISO 27001; Neon and Vercel SOC 2 Type 2); DPA included in every account; SAML/OIDC SSO and SCIM free; 99% monthly API uptime promise on paid accounts | Trust centre hosted on Vanta; no certifications named |
| Regions | All processing in one region in Virginia, United States (trust page); limits are counted per region | Each team has a fixed home region; available regions are not listed |
| Company headquarters | Denver, Colorado, United States | San Francisco, California, United States |
| Good fit for | Cost-sensitive agent workloads with many short runs, where active-CPU billing and a free monthly allowance matter | Long-running coding and personal agents that need a persistent VM with pause, forks and brokered credentials |
Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Runtime
- You want the lowest published per-vCPU rate with billing only for active CPU.
- You need SDKs in Go, Ruby or Java as well as Python and TypeScript.
- You want SSO, SCIM, audit logging and a DPA without an enterprise contract.
- You run many short agent jobs and want a renewing free monthly allowance.
Reasons to choose Superserve
- You want sandboxes with no runtime limit that pause and resume with memory intact.
- You need API credentials kept outside the sandbox with an audit log of their use.
- You run coding-agent harnesses and want ready-made integration guides and a desktop template.
- You want per-second billing with no idle charge for paused sandboxes.
Trade-offs to check first
- Runtime: Single region: everything runs in one region in Virginia, United States.
- Runtime: No startup latency figures are currently published, and no certification of Runtime itself is named.
- Superserve: No cold-start figure, region list or compliance certification is published.
- Superserve: Only the client SDKs, CLI and console are published as open source; source for the sandbox runtime is not published.
Both are worth piloting with your own image and region. See the full Runtime profile and Superserve profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Runtime or Superserve better for AI agents?
What is the difference between Runtime and Superserve?
Which is open source, Runtime or Superserve?
How do Runtime and Superserve isolate code?
How does Runtime pricing compare with Superserve?
How long can sessions run on Runtime and Superserve?
idlePauseSeconds 60–86,400, or 0 for never). Superserve: Unlimited runtime on Developer and Pro plans; optional auto-pause cap on active time and an idle timeout of 60 s to 7 days.Do Runtime and Superserve support snapshots or pause and resume?
Sources
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
Agent Sandboxes. (2026). Runtime vs Superserve. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/withruntime-vs-superserve/