RadarTopicsBuildersWeeklyReads
Open Source Radar
zerobootdev/

zeroboot

GitHubWebsite

Zeroboot provides sub-millisecond VM sandboxes for AI agents using copy-on-write forking on Firecracker/KVM, with Python/TypeScript SDKs and a managed API option.

2.4kstars
107forks
12issues
Apache-2.0license
2026since
Star historydaily snapshots by VibeCrowd

Collecting history — the radar snapshots this repo daily. The trend line appears after 3 days of data (1 so far).

Alternatives & relatedmatched by topic overlap
Reviewgenerated from repository data · Aug 5, 2026

What it is

Zeroboot is a Rust-based project that enables sub-millisecond VM sandboxes for AI agents by using a copy-on-write forking model on top of Firecracker/KVM. It shares a real VM as a template and forks new VMs quickly by mapping snapshot memory as CoW and restoring CPU state.

How it works

  • Template: Firecracker boots a VM, pre-loads the runtime, and snapshots memory + CPU state.
  • Fork: (~0.8ms) Creates a new KVM VM, maps snapshot memory as CoW, restores all CPU state.
  • Isolation: Each fork is a separate KVM VM with hardware-enforced memory isolation.

Getting started

The README shows how to call the managed API for execution:

curl -X POST https://api.zeroboot.dev/v1/exec \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer zb_demo_hn2026' \
  -d '{"code":"import numpy as np; print(np.random.rand(3))"}'

SDK examples are provided:

  • Python:
from zeroboot import Sandbox
sb = Sandbox("zb_live_your_key")
result = sb.run("print(1 + 1)")
  • TypeScript:
import { Sandbox } from "@zeroboot/sdk";
const result = await new Sandbox("zb_live_your_key").run("console.log(1+1)");

Recent releases

There are no releases listed.

Traction

Stars: 2417 Forks: 107 Open issues: 12

Behind the repo

Not provided in the facts.

Caveats

  • Status: Working prototype. The fork primitive, benchmarks, and API are real, but not production-hardened yet.
  • License: Apache-2.0
  • Requires Linux box with KVM for self-hosting.
  • Known limitations include single vCPU per fork, no networking inside forks, and template update via full re-snapshot (~15s).
SharePost on XLinkedIn
All trending reposRevenue-verified startups →