Deploy Now

SaaS Alternative

E2B Modal Fly Machines

Categories

Self-Hosted DevOps AI Security Infrastructure Cloud Native Sandbox Virtualization

Stars

12,155

Forks

1,104

Watchers

68

Developer links

Last Updated: 09-11-2026
Share on X

CubeSandbox

CubeSandbox gives every AI agent its own hardware-isolated MicroVM with a dedicated Linux kernel — not a shared-kernel container but a true KVM virtual machine — booting in under 60ms with less than 5MB of memory overhead per instance, enabling thousands of concurrent sandboxes on a single server via kernel sharing and Copy-on-Write memory. The Rust-built CubeProxy exposes an E2B SDK-compatible REST API on Axum, so existing E2B Cloud applications switch by changing one environment variable with zero client code changes. CubeMaster orchestrates cluster-level scheduling in Go while Cubelet manages node-local sandbox lifecycles including create, run, pause, resume, snapshot, and destroy operations. CubeVS, the eBPF-powered network layer, enforces per-sandbox isolation with LPM trie-based egress policies entirely in kernel space — no userspace context switches — while CubeEgress provides an L7 security proxy with per-domain, per-path, and per-method allowlists plus automatic credential injection that keeps secrets invisible to sandbox code. Hundred-millisecond-granularity snapshots enable checkpoint, rollback, and parallel fork from any saved state. The volume framework supports E2B-compatible pluggable storage with independent lifecycle and cross-sandbox sharing. Production deployment uses Terraform on Tencent Cloud or Helm charts on Kubernetes, K3s, or TKE, with full ARM64 support alongside x86_64 and AutoPause/AutoResume for cost optimization. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

CubeSandbox
CubeSandbox
CubeSandbox
CubeSandbox
CubeSandbox

Benefits

  • Sub-60ms Hardware-Isolated MicroVMs
  • Each sandbox boots a dedicated Linux kernel inside a KVM MicroVM in under 60 milliseconds with less than 5MB memory overhead — true hardware isolation, not container sharing.
  • E2B SDK Drop-In Replacement
  • Natively compatible with the E2B SDK interface, allowing existing E2B Cloud applications to migrate by changing one environment variable with zero client code modifications.
  • eBPF Network Security at Kernel Level
  • CubeVS enforces per-sandbox network isolation and egress filtering entirely in kernel space using eBPF LPM tries, with an L7 proxy for domain-level credential injection.
  • Thousands of Sandboxes Per Server
  • Kernel sharing and Copy-on-Write memory keep per-instance overhead under 5MB, while AutoPause/AutoResume further optimizes density by suspending idle sandboxes automatically.

Features

  • Snapshot and Rollback
  • Hundred-millisecond-granularity checkpoints on running sandboxes with rollback to any saved state and parallel fork for exploring multiple execution paths simultaneously.
  • Cluster Orchestration
  • CubeMaster schedules sandbox creation across nodes while Cubelet manages local lifecycles, with Redis-backed state coordination and cube-lifecycle-manager for auto-pause and resume.
  • CubeVS Network Layer
  • Three-layer eBPF architecture provides per-sandbox TAP devices, stateful connection tracking with O(1) lookups, and protocol-aware NAT timeouts entirely in kernel space.
  • Volume Framework
  • E2B-compatible pluggable storage volumes with independent lifecycle management, cross-sandbox sharing, and support for custom backend storage solutions.
  • Production Deployment
  • Deploy via Terraform on Tencent Cloud, Helm charts on Kubernetes or K3s, or single-node quickstart scripts with ARM64 and x86_64 architecture support.
  • L7 Security Proxy
  • CubeEgress provides per-domain, per-path, and per-method allowlist policies with automatic credential injection — secrets never visible to sandbox code.