How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.
AgentENV is a distributed sandbox platform that launches isolated Firecracker microVMs across many machines, so AI agents can run their workloads in parallel and at scale. Each environment gets its own dedicated Linux kernel, and a gateway and scheduler control plane places and manages environments across a multi-node cluster. It also serves an E2B-compatible HTTP API, so existing E2B Python and TypeScript SDK code works unchanged against your own infrastructure.
The main features of kvcache-ai/agentenv are: MicroVM Agent Sandboxes, Distributed Workload Orchestration, E2B-Compatible APIs, Sandbox Cluster Schedulers, Sandbox Forking, Snapshot Fork Restores, MicroVM Sandboxes, MicroVM Runtime Isolations.
Projects with overlapping indexed features include: deeplethe/sandstorm — Sandstorm is a self-hosted platform for running large numbers of isolated sandboxes for AI agents across a cluster of… superradcompany/microsandbox — Microsandbox is a runtime for creating and managing lightweight, hardware-isolated virtual machines — called sandboxes… zerocore-ai/microsandbox — microsandbox is a platform that runs untrusted code inside hardware-isolated microVMs, each with its own kernel,… agent-substrate/substrate — Substrate is a Kubernetes-based platform for running AI agents as persistent actors. Each actor keeps its memory and… e2b-dev/code-interpreter — This project is an infrastructure platform designed to provide secure, isolated, and ephemeral cloud-based Linux… mesosphere/marathon — Marathon is an Apache Mesos container orchestrator and distributed workload manager. It serves as a framework for…
Sandstorm is a self-hosted platform for running large numbers of isolated sandboxes for AI agents across a cluster of machines. A central master places sandboxes onto worker nodes, which join by pairing code or dial out from behind a NAT. Each node isolates workloads with either Firecracker microVMs or gVisor, a user-space kernel for hosts without KVM. Master, node, and web console roles ship in a single executable. What sets it apart is density and start speed. Children are forked from a warmed parent snapshot using shared copy-on-write memory, so many sandboxes start in milliseconds without
Microsandbox is a runtime for creating and managing lightweight, hardware-isolated virtual machines — called sandboxes — that boot directly from standard OCI container images. Each sandbox runs as its own host process with a separate kernel, filesystem, and network stack, providing process-per-sandbox isolation. The project includes a command-line tool and multi-language SDKs (Rust, TypeScript, Python, Go) for programmatic lifecycle control, and it communicates with sandbox agents over Unix sockets using a CBOR-encoded protocol. What distinguishes Microsandbox is its combination of host-manag
microsandbox is a platform that runs untrusted code inside hardware-isolated microVMs, each with its own kernel, filesystem, and network stack. It boots directly from standard OCI container images, supports copy-on-write filesystem layers, and integrates with AI agents to execute tool calls and generated code in isolated environments with secret protection. What sets microsandbox apart is its host-side network proxy that enforces firewall rules, intercepts DNS, inspects TLS traffic, and injects secrets at the network boundary without exposing them inside the VM. It provides SSH access to micr
Substrate is a Kubernetes-based platform for running AI agents as persistent actors. Each actor keeps its memory and filesystem state across idle periods: when it goes quiet, it is snapshotted to durable object storage and its worker is freed, and it is later restored onto any available worker when a request arrives. Agents built on any framework can run from standard container images without code changes, and each untrusted agent runs in its own gVisor or microVM sandbox with separate compute, network, and storage. What sets it apart is the combination of density and containment. Because mos