OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Agent Infrastructure

Zeroboot

Zeroboot is open-source infrastructure for running code in isolated KVM virtual-machine sandboxes. It forks preinitialized Firecracker snapshots using copy-on-write memory mappings and provides an execution API plus Python and TypeScript SDKs for submitting code.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Zeroboot — OpenViST project profile in Agent Infrastructure.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Zeroboot when an agent or service needs to run code in isolated VM sandboxes and can work within the project's current prototype status and runtime constraints.

Who it is for

  • AI-agent developers who need isolated environments for generated code.
  • Teams building code-execution services that can use the API or Python and TypeScript SDKs.
  • Operators self-hosting sandbox infrastructure on Linux servers with KVM support.

Documented uses

  • Submit code for execution through the API or an SDK.
  • Create separate execution sandboxes from a preinitialized VM snapshot.
  • Self-host agent-oriented sandbox infrastructure on Linux with KVM.
Before you choose

Requirements & limits

The repository is public and identifies the project as open source under the Apache-2.0 license.

  • Self-hosting requires Linux with KVM support.
  • Each fork is a separate KVM VM with hardware-enforced memory isolation, according to the project documentation.
  • Forks have one vCPU and no networking; sandbox communication is through serial I/O.
  • Userspace PRNGs inherit state from the snapshot and need explicit reseeding per fork where relevant.
  • Template changes require a full new snapshot, stated to take about 15 seconds.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Submit code through the Zeroboot execution API

Send a code payload to the documented execution endpoint using the repository's demo request.

Before you start

  • An HTTP client such as curl.
  • The documented execution endpoint and demo bearer token.

Steps

  1. Send a POST request to https://api.zeroboot.dev/v1/exec.

  2. Set Content-Type to application/json and Authorization to Bearer zb_demo_hn2026.

  3. Include a JSON body with a code field containing the code to execute. The README example uses Python code.

Expected outcome

The request submits code to Zeroboot's execution API for sandbox execution.

Guide limitations

  • The README presents this as a demo request and does not document response interpretation here.
  • Forks have no networking, use one vCPU, and communicate through serial I/O only.
  • The project describes itself as a working prototype that is not production-hardened.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
10 October 2026
Original website title
zerobootdev/zeroboot · Official homepage title · retained in its source language
How we review sourcesSuggest a correction