All 224 Dependencies
Every package CubeSandbox depends on, ranked by repo health score.
CubeSandbox is an open-source sandbox service purpose-built to give AI agents secure, disposable compute at scale. Each sandbox boots as a dedicated MicroVM with its own Linux kernel on top of KVM, isolating agent-executed code at the hardware level rather than sharing a host kernel the way container-based sandboxes do. Cold starts average under 60ms and steady-state overhead per sandbox is under 5MB, so a single node can host thousands of concurrent, hardware-isolated environments — a density and speed profile aimed squarely at agent workloads that spin up and tear down sandboxes constantly.
Under the hood, CubeSandbox splits into a stateless control plane and a node-local data plane. CubeAPI (Rust/Axum) and CubeMaster (Go) handle scheduling and API traffic with all coordination state held in Redis, so either service scales out horizontally with no local state to reconcile. On each compute node, Cubelet drives the sandbox lifecycle through CubeShim, a containerd Shim v2 implementation that hands off to CubeHypervisor — a lightweight VMM built on RustVMM. Snapshotting and cloning go through CubeCoW, a Rust storage engine that uses the kernel's FICLONE ioctl for O(1), zero-copy snapshots, enabling hundred-millisecond-granularity checkpoint/rollback/fork of running sandboxes.
The project ships an E2B-compatible REST API, so existing E2B SDK code (Python, JS) can point at a self-hosted CubeSandbox cluster by changing only the API URL and key — no client-side rewrite. Security is handled at the network layer: all sandbox egress routes through CubeEgress, an OpenResty-based L7 proxy enforcing per-domain/path/method allowlists with automatic credential injection, so secrets used to call external APIs never enter the sandbox itself. CubeVS adds eBPF-based inter-sandbox isolation and SNAT egress at the kernel level.
Beyond the core runtime, CubeSandbox includes auto-pause/auto-resume for idle sandboxes, a pluggable Volume framework for custom storage backends, a WebUI/CLI for operators, and deployment tooling for single-node, Terraform-based Tencent Cloud clusters, and Kubernetes. Client SDKs are published for Python (PyPI), Go, and Node, and the project is maintained by Tencent Cloud with an active, CNCF-landscape-listed open-source community.