Zeroboot
Apache-2.0 Rust exec server that forks a pre-warmed Firecracker snapshot into a new copy-on-write KVM VM for every code run, with Python and TypeScript SDKs. A prototype snapshot-forking exec server for stateless, sub-millisecond-spawn code runs, self-hosted on Linux with KVM.
Overview
Zeroboot is an Apache-2.0 server written in Rust that runs untrusted code snippets for AI agents in VMs created by copy-on-write forking. A template is made once by booting a Firecracker VM, pre-loading a runtime and snapshotting its memory and CPU state; each request then creates a new KVM VM, maps the snapshot memory with MAP_PRIVATE and restores the CPU state, which the README benchmarks at a 0.79 ms p50 spawn (vendor benchmark). The HTTP API offers /v1/exec and /v1/exec/batch for Python (the default) and Node.js/JavaScript, plus health and Prometheus metrics endpoints, with optional API-key auth rate-limited at 100 requests per second per key. Python and TypeScript SDKs wrap the API, and it self-hosts on any Linux machine with KVM.
The README calls the project a "Working prototype" whose fork primitive, benchmarks and API are real but "not production-hardened yet". Documented limitations: one vCPU per fork, no networking inside forks, userspace random-number generators that need explicit reseeding per fork because forks share the snapshot's CSPRNG state, and a full re-snapshot for template changes. Each exec has a 30-second default timeout and no state carries between runs. A managed API is in early access with no pricing published; zeroboot.dev redirects to the GitHub repository.
Notable
- Created in March 2026 by Adam Miribyan; no tagged release (the changelog lists 0.1.0 as untagged); 2,483 GitHub stars at verification.
- README benchmark table: 0.79 ms p50 and 1.74 ms p99 spawn, ~265 KB per sandbox (vendor benchmark).
- Status in the README: "Working prototype", "not production-hardened yet".
Zeroboot specifications
| Attribute | Details |
|---|---|
| Isolation | Each execution runs in its own KVM virtual machine forked from a Firecracker template snapshot: snapshot memory is mapped copy-on-write with mmap(MAP_PRIVATE) and CPU state is restored, so forks cannot see each other's writes (hardware-enforced via Intel VT-x/AMD-V) |
| Deployment | Open-source project · Self-hostable |
| Open source | Yes (Apache-2.0) |
| SDKs and interfaces | Python, JavaScript/TypeScript, REST API |
| Cold start (vendor claim) | README (vendor benchmark): spawn latency p50 0.79 ms and p99 1.74 ms; fork plus Python exec ~8 ms; 1,000 concurrent forks in 815 ms; ~265 KB of memory per sandbox |
| Max session length | Each exec has a timeout_seconds parameter that defaults to 30 seconds; a maximum and long-lived sandboxes are not documented |
| Persistence | None between runs: every exec forks fresh from the template snapshot. Templates (for example Python with numpy and pandas pre-loaded, or Node.js) are built once by booting Firecracker and snapshotting memory and CPU state (~15 s); template updates require a full re-snapshot |
| GPU | Not documented |
| Networking | No networking inside forks; sandboxes communicate with the host over serial I/O only (README known limitations) |
| Pricing | Free to self-host under Apache-2.0. A managed API at api.zeroboot.dev is offered as early access through a sign-up form; no pricing published |
| Free tier | Free to self-host; the README includes a demo key for the managed endpoint |
| Compliance | Not documented |
| Regions | Not documented |
| Company headquarters | Not documented |
Facts from Zeroboot’s public documentation, verified November 18, 2026. Performance numbers are vendor claims.
Strengths and trade-offs
Strengths
- You run large numbers of short, independent Python or Node.js snippets and want a separate VM for each one.
- You want a small, self-hostable exec server with a two-endpoint HTTP API and batch execution.
- You want each run isolated by KVM rather than by a container or namespace.
Trade-offs
- Labelled a working prototype that is not production-hardened.
- No networking inside forks and a single vCPU per fork.
- No state carries between runs; long-lived sandboxes are not documented.
- Userspace PRNGs must be reseeded per fork, and the managed API has no published pricing.
Good fit for: Very high-rate, short Python or Node.js snippet execution where each call gets its own VM.
How Zeroboot compares
| Sandbox | Company HQ | Isolation | Open source | Self-host / BYOC | Cold start (vendor) | Max session | Snapshots / pause | GPU | SDKs |
|---|---|---|---|---|---|---|---|---|---|
| Zeroboot | Not documented | CoW KVM fork of Firecracker snapshot | Yes | Yes / Not documented | 0.79 ms p50 (claim) | 30 s default timeout | Not documented / Not documented | Not documented | Python, JavaScript/TypeScript, REST API |
| smol machines (smolvm) | Not documented | libkrun microVM | Yes | Yes / Not documented | <200 ms (claim) | Not documented | Yes / Yes | Yes | JavaScript/TypeScript, Python, Rust, Go, CLI, REST API |
| Firecracker | United States | KVM microVM | Yes | Yes / No | <125 ms (spec) | Not documented | Yes / Yes | Not documented | REST API, CLI |
| E2B | United States | Firecracker microVM | Yes | Yes / Yes | Not documented | 1 h / 24 h (Pro) | Yes / Yes | No | Python, JavaScript/TypeScript |
| Microsandbox | Not documented | MicroVM (libkrun) | Yes | Yes / Yes | <100 ms | Not documented | Yes / Not documented | Not documented | TypeScript, Python, Rust, Go, Ruby, CLI, MCP server |
| Daytona | United States | Containers or VMs | No | Not documented / Yes | <90 ms | Unlimited | Yes / Yes | Yes | Python, TypeScript, Ruby, Go, Java |
Head-to-head: smol machines (smolvm) vs Zeroboot
Frequently asked questions
What is Zeroboot?
How does Zeroboot isolate code?
Is Zeroboot open source?
How much does Zeroboot cost?
How long can Zeroboot sessions run?
What are the alternatives to Zeroboot?
Sources
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 18, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
Agent Sandboxes. (2026). Zeroboot. agentsandboxes.org. Last reviewed November 18, 2026. https://agentsandboxes.org/sandboxes/zeroboot/