zeroboot-vm-sandbox

Skill by ara.so — Daily 2026 Skills collection. Zeroboot provides sub-millisecond KVM virtual machine sandboxes for AI agents using copy-on-write forking. Each sandbox is a real hardware-isolated VM (via Firecracker + KVM), not a container. A template VM is snapshotted once, then forked in ~0.8ms per execution using mmap(MAP_PRIVATE) CoW semantics. Set your API key as an environment variable: Never hardcode keys in source files. Execute code in a fresh sandbox fork. Request: Headers: Response: See docs/DEPLOYMENT.md in the repo. Requirements: /dev/kvm not found (self-hosted) API returns 401 Unauthorized Timeout on execution High memory usage (self-hosted) - Template : Firecracker boots once, pre-loads your runtime, snapshots memory + CPU state - Fork (~0.8ms) : New KVM VM maps snapshot memory as CoW, restores CPU state - Isolation : Each fork is a separate KVM VM with hardware-enforced memory isolation - Each sandbox is a real KVM VM — not a container or process jail - Memory isolation is hardware-enforced (not software) - CoW means only pages written by your code consume extra RAM - Linux host with KVM support ( /dev/kvm accessible) - Firecracker binary - Rust 2021 edition toolchain - Snapshot layer : Firecracker VM boots once per runtime template, memory + vCPU state saved to disk - Fork layer (Rust): mmap(MAP_PRIVATE) on snapshot file → kernel handles CoW page faults per VM...