InstaVM vs Superserve
Choose InstaVM for agent builders who want fast-booting microVMs with desktop, SSH and snapshot-clone workflows under per-second billing; choose Superserve for long-running coding and personal agents that need a persistent VM with pause, forks and brokered credentials. InstaVM uses Firecracker microVM isolation; Superserve uses Firecracker microVM isolation.
Key differences between InstaVM and Superserve
- Session length: Configurable (InstaVM) versus Unlimited (Superserve).
- SDKs and interfaces: Only Superserve lists MCP server.
What they have in common
- Both are hosted platforms.
- Both use microVM isolation.
- Neither is open source.
- Both support snapshots.
- Both can pause and resume a sandbox.
- Both list Python, TypeScript, CLI and REST API.
InstaVM vs Superserve at a glance
| Attribute | InstaVM | Superserve |
|---|---|---|
| What it is | Firecracker-based Linux microVMs for agents with sub-200 ms claimed boots, snapshots, clones, persistent volumes, a desktop runtime and SSH access, with a local Apple-container companion (CodeRunner). | 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 kernel, filesystem and network stack per sandbox | Firecracker microVM per sandbox |
| Open source | No | No |
| Self-host / BYOC | Not documented / Not documented | Not documented / Yes |
| SDKs | Python, JavaScript/TypeScript, CLI, REST API | Python, JavaScript/TypeScript, CLI, REST API, MCP server |
| Cold start (vendor claim) | Website: "185ms" P95 cold start, "Provision a fresh VM in ~147ms" over SSH, snapshot restore "typically under 500ms" (vendor claims) | Docs: sandboxes spin up "in seconds"; no figure published |
| Max session | Session lifetime is configurable; no maximum documented; always-on VMs are offered | 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 | State persists across execute() calls within a session and is destroyed when it ends; named volumes persist across VM lifecycles with mid-task checkpoints; VMs can be paused, snapshotted, resumed or cloned; snapshots built from OCI images | 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 | Default-deny outbound with domain/CIDR allowlists and package-manager controls (Free plan egress limited to known package managers and AI APIs; Pro unrestricted or allowlists); proxy-based secret injection; shares expose any port publicly or privately with custom domains | 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 | Per second: $0.000014 per vCPU (about $0.05/hour) and $0.0000045 per GB of RAM (about $0.02/hour); 10 GB volume storage included, then $0.0002 per GB-hour. Free plan $0 base plus usage (5 concurrent VMs); Pro $100/month plus usage (100 concurrent VMs, 99.9% SLA); Enterprise custom | 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 | $50 in starting credits with a card on file; 5 concurrent VMs and 100 browser sessions a month | Limited free trial for a first sandbox, no card required (amount not stated) |
| Compliance | "SOC 2 Type II compliance" listed as an Enterprise plan feature; no report details published | Trust centre hosted on Vanta; no certifications named |
| Regions | Not documented | Each team has a fixed home region; available regions are not listed |
| Company headquarters | Not documented | San Francisco, California, United States |
| Good fit for | Agent builders who want fast-booting microVMs with desktop, SSH and snapshot-clone workflows under per-second billing | 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 InstaVM
- You want fast microVM boots with per-second billing and a $50 trial.
- You need desktop and browser automation with live noVNC takeover.
- You want to clone a running VM or checkpoint a volume mid-task.
- You prefer SSH-first access without installing an SDK.
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
- InstaVM: Free plan lists egress to known package managers and AI APIs; unrestricted egress is listed under Pro.
- InstaVM: Regions, GPU support and maximum session length are not documented.
- 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 InstaVM profile and Superserve profile, or the complete comparison.
More comparisons
Frequently asked questions
Is InstaVM or Superserve better for AI agents?
What is the difference between InstaVM and Superserve?
Which is open source, InstaVM or Superserve?
How do InstaVM and Superserve isolate code?
How does InstaVM pricing compare with Superserve?
How long can sessions run on InstaVM and Superserve?
Do InstaVM 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). InstaVM vs Superserve. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/instavm-vs-superserve/