Zeroboot launches sub-millisecond VM sandboxes

This is the right kind of infrastructure bet for agentic workloads: the latency target is ambitious, but the value prop only matters if isolation stays real under load. Zeroboot’s prototype numbers are eye-catching, yet the current limitations make it clear this is still early-stage plumbing, not a drop-in production platform.

• –The published benchmarks are the headline feature: roughly 0.79ms p50 spawn latency, 1.74ms p99, and about 265KB of memory per sandbox.
• –The architecture is clever because it keeps the hypervisor boundary intact while using copy-on-write snapshot memory to avoid a full boot for every task.
• –The tradeoffs are non-trivial: no networking inside forks, single-vCPU sandboxes, shared PRNG state, and full re-snapshot time for template updates.
• –The repo’s managed API plus Python and TypeScript SDKs suggest a real platform play, while self-hosted KVM on Linux keeps it attractive for infra-savvy teams.
• –Compared with container-first sandboxes, Zeroboot is pitching the hardest thing to get right in agent infra: near-instant startup without giving up VM isolation.