Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
zeroboot — Sub-millisecond VM sandboxes for AI agents via copy-on-write forking | Kitploit
Tools/GitHubGitHub/zerobootdev/zeroboot
Container SecurityDynamic Analysis (Sandboxing)Security VirtualizationCloud SecurityDevSecOpsAI Security
GitHubzerobootdev/zeroboot

zeroboot

Sub-millisecond VM sandboxes for AI agents via copy-on-write forking

View Repository
2.4k107105 months agoReviewed by Kitploit

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share
Website

Zeroboot

Sub-millisecond VM sandboxes for AI agents via copy-on-write forking

License Rust API Status


demo

Try it

root@kitploit:~
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))"}'

Benchmarks

Each sandbox is a real KVM virtual machine with hardware-enforced memory isolation.

How it works

root@kitploit:~
  Firecracker snapshot ──► mmap(MAP_PRIVATE) ──► KVM VM + restored CPU state
                              (copy-on-write)         (~0.8ms)
  1. Template (one-time): Firecracker boots a VM, pre-loads your runtime, and snapshots memory + CPU state
  2. Fork (~0.8ms): Creates a new KVM VM, maps snapshot memory as CoW, restores all CPU state
  3. Isolation: Each fork is a separate KVM VM with hardware-enforced memory isolation

SDKs

Python — sdk/python

root@kitploit:~
from zeroboot import Sandbox
sb = Sandbox("zb_live_your_key")
result = sb.run("print(1 + 1)")

TypeScript — sdk/node

root@kitploit:~
import { Sandbox } from "@zeroboot/sdk";
const result = await new Sandbox("zb_live_your_key").run("console.log(1+1)");

Docs

  • API Reference
  • Deployment Guide
  • Architecture

Status

Working prototype. The fork primitive, benchmarks, and API are real, but not production-hardened yet. Open an issue if you're interested.

Self-host or managed

Zeroboot is open source. Self-host it on any Linux box with KVM, or use the managed API:

root@kitploit:~
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))"}'

Building the managed service for teams that don't want to run their own infra. Sign up for early access: https://tally.so/r/aQGkpb

Known limitations

  • Forks share CSPRNG state from the snapshot. Kernel entropy is reseeded via RNDADDENTROPY but userspace PRNGs (numpy, OpenSSL) need explicit reseeding per fork. See Firecracker's guidance.
  • Single vCPU per fork. Multi-vCPU is architecturally possible but not implemented.
  • No networking inside forks. Sandboxes communicate via serial I/O only.
  • Template updates require a full re-snapshot (~15s). No incremental patching.

License

Apache-2.0

Download Tool
MetricZerobootE2BmicrosandboxDaytona
Spawn latency p500.79ms~150ms~200ms~27ms
Spawn latency p991.74ms~300ms~400ms~90ms
Memory per sandbox~265KB~128MB~50MB~50MB
Fork + exec (Python)~8ms---
1000 concurrent forks815ms---