InstaVM vs Runtime
Choose InstaVM for agent builders who want fast-booting microVMs with desktop, SSH and snapshot-clone workflows under per-second billing; choose Runtime for cost-sensitive agent workloads with many short runs, where active-CPU billing and a free monthly allowance matter. InstaVM uses Firecracker microVM isolation; Runtime uses Firecracker microVM isolation.
Key differences between InstaVM and Runtime
- Session length: Configurable (InstaVM) versus No limit documented (Runtime).
- SDKs and interfaces: Only Runtime lists Go, Ruby, Java and 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 Runtime at a glance
| Attribute | InstaVM | Runtime |
|---|---|---|
| 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). | 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. |
| Type | Hosted platform | Hosted platform |
| Isolation | Firecracker microVM with its own kernel, filesystem and network stack per sandbox | Firecracker microVM with its own Linux kernel, disk and memory per sandbox, on dedicated servers Runtime operates |
| Open source | No | No |
| Self-host / BYOC | Not documented / Not documented | Not documented / Not documented |
| SDKs | Python, JavaScript/TypeScript, CLI, REST API | JavaScript/TypeScript, Python, Go, Ruby, Java, 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) | 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 |
| Max session | Session lifetime is configurable; no maximum documented; always-on VMs are offered | No maximum documented; a sandbox pauses itself after 300 seconds of inactivity by default (idlePauseSeconds 60–86,400, or 0 for never) |
| 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 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 |
| 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 | 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 |
| 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 | $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 |
| Free tier | $50 in starting credits with a card on file; 5 concurrent VMs and 100 browser sessions a month | 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 |
| Compliance | "SOC 2 Type II compliance" listed as an Enterprise plan feature; no report details published | 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 |
| Regions | Not documented | All processing in one region in Virginia, United States (trust page); limits are counted per region |
| Company headquarters | Not documented | Denver, Colorado, United States |
| Good fit for | Agent builders who want fast-booting microVMs with desktop, SSH and snapshot-clone workflows under per-second billing | Cost-sensitive agent workloads with many short runs, where active-CPU billing and a free monthly allowance matter |
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 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.
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.
- 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.
Both are worth piloting with your own image and region. See the full InstaVM profile and Runtime profile, or the complete comparison.
More comparisons
Frequently asked questions
Is InstaVM or Runtime better for AI agents?
What is the difference between InstaVM and Runtime?
Which is open source, InstaVM or Runtime?
How do InstaVM and Runtime isolate code?
How does InstaVM pricing compare with Runtime?
How long can sessions run on InstaVM and Runtime?
idlePauseSeconds 60–86,400, or 0 for never).Do InstaVM and Runtime 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 Runtime. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/instavm-vs-withruntime/