CubeSandbox: A secure, lightweight sandbox service for AI agents with E2B SDK compatibility.
What problem it solves
AI agents need isolated environments that can execute code and workloads while supporting fast creation, secure network access, and manageable state. They also need an interface that can integrate with existing agent tooling and deployment workflows.
Key features
Hardware-level isolation — Each sandbox runs in its own MicroVM with a dedicated operating system kernel. Kernel-level network controls add isolation between sandboxes.
Source: README, hypervisor
E2B SDK compatibility — The service exposes an E2B-compatible interface, allowing existing E2B SDK clients to change their environment configuration without modifying client code.
Source: README, sdk
Network security and credential protection — Network policies can filter sandbox egress and control access by domain, path, and method. The security proxy injects credentials so secrets remain outside sandbox code.
Source: README, CubeEgress
Snapshot, clone, and rollback — The Copy-on-Write state engine supports checkpoints, parallel forks, rollback, and filesystem-only snapshots. Storage backends can be extended for cross-node templates and paused sandboxes.
Source: README, cubecow
Cluster deployment and operations — The project supports single-node and multi-node deployment, Kubernetes deployment, Terraform-based cluster provisioning, scheduling plugins, and sandbox observability.
Source: README, CubeObservability
Who it may suit
This project may suit teams building AI-agent execution environments, sandboxed code execution systems, or agent workflows that require isolation and network controls. It may also suit operators seeking E2B-compatible sandbox infrastructure with snapshot, scheduling, and multi-node capabilities.
Topics to discuss
Which deployment path best fits different agent workloads and operational requirements?
How should scheduler plugins be designed for resource-aware placement and workload isolation?
What storage backend and snapshot policy should teams use for cross-node sandbox workflows?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/TencentCloud/CubeSandbox#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…