Superserve
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. A well-documented persistent-VM sandbox whose credentials broker suits agents that must call third-party APIs safely.
Overview
Superserve is a hosted sandbox service in which every sandbox is a Firecracker microVM that can stay alive indefinitely, pause with its memory and disk intact and be snapshotted or forked. You drive it from Python or TypeScript SDKs, a CLI, a REST API or a hosted MCP server, and the docs carry integration guides for Claude Code, Codex, OpenAI Agents SDK, LangChain, CrewAI and others, plus a superserve/desktop template that ships an XFCE desktop and Chrome for computer-use agents. Templates are built from a BuildSpec, and Docker can run inside a sandbox.
The distinctive piece is the secrets layer: credentials are bound to a sandbox and injected by a proxy on outbound requests, with an audit trail of which credential was used where. Pricing is per-second vCPU and memory plus retained storage, with Developer ($20/month) and Pro ($250/month) plans and an Enterprise tier that can deploy into your own AWS, GCP or Azure VPC for early partners. The SDKs, CLI and console are Apache-2.0 on GitHub, but the sandbox service itself is closed. No maturity label, compliance certification or region list is published.
Notable
- Snapshots: 100 per team, 20 per sandbox; a running sandbox pauses "usually for under a second" while one is taken.
- Paused sandboxes are kept forever by default; idle timeout is configurable from 60 seconds to 7 days.
- Client repository (SDKs, CLI, MCP server, console) is Apache-2.0 with 505 GitHub stars at verification.
Superserve specifications
| Attribute | Details |
|---|---|
| Isolation | Firecracker microVM per sandbox |
| Deployment | Hosted platform · BYOC available |
| Open source | No |
| SDKs and interfaces | Python, JavaScript/TypeScript, CLI, REST API, MCP server |
| Cold start (vendor claim) | Docs: sandboxes spin up "in seconds"; no figure published |
| Max session length | 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 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 |
| GPU | Not documented |
| Networking | 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 | 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 | Limited free trial for a first sandbox, no card required (amount not stated) |
| Compliance | Trust centre hosted on Vanta; no certifications named |
| Regions | Each team has a fixed home region; available regions are not listed |
Facts from Superserve’s public documentation, verified November 9, 2026. Performance numbers are vendor claims.
Strengths and trade-offs
Strengths
- 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
- No cold-start figure, region list or compliance certification is published.
- The sandbox runtime is closed; only the clients are open source.
- BYOC deployment is limited to Enterprise "early partners".
Good fit for: Long-running coding and personal agents that need a persistent VM with pause, forks and brokered credentials.
Use cases Superserve fits
- Coding agents: Persistent Firecracker VMs with pause, forks and a credentials broker, built for long-running coding and personal agents.
How Superserve compares
| Sandbox | Isolation | Open source | Self-host / BYOC | Cold start (vendor) | Max session | Snapshots / pause | GPU | SDKs |
|---|---|---|---|---|---|---|---|---|
| Superserve | Firecracker microVM | No | No / Yes | Not documented | Unlimited | Yes / Yes | Not documented | Python, JavaScript/TypeScript, CLI, REST API, MCP server |
| E2B | Firecracker microVM | Yes | Yes / Yes | Not documented | 1 h / 24 h (Pro) | Yes / Yes | No | Python, JavaScript/TypeScript |
| Daytona | Containers or VMs | No | Not documented / Yes | <90 ms | Unlimited | Yes / Yes | Yes | Python, TypeScript, Ruby, Go, Java |
| Morph Cloud | VM | No | No / Not documented | <250 ms (restore) | Configurable | Yes / Yes | Not documented | Python, TypeScript |
| Runtime | Firecracker microVM | No | No / No | Not documented | No limit documented | Yes / Yes | Not documented | JavaScript/TypeScript, Python, Go, Ruby, Java, CLI, REST API, MCP server |
| Leap0 | Firecracker microVM | No | No / Yes | ~100 ms (claim) | 8 h max | Yes / Yes | Not documented | Python, JavaScript/TypeScript, Go, MCP server |
| InstaVM | Firecracker microVM | No | No / No | <200 ms (claim) | Configurable | Yes / Yes | Not documented | Python, JavaScript/TypeScript, CLI, REST API |
Frequently asked questions
What is Superserve?
How does Superserve isolate code?
Is Superserve open source?
How much does Superserve cost?
What are the alternatives to Superserve?
Sources
Cite this page
Agent Sandboxes. (2026). Superserve. agentsandboxes.org. Last reviewed November 9, 2026. https://agentsandboxes.org/sandboxes/superserve/
Found an error or a missing sandbox? Submit a correction — every entry links to the sources it relies on.