CubeSandbox
v0.7.2 open-sourceThe section your link pointed to isn't on CubeSandbox's page any more, so we've brought you to the top.
CubeSandbox is a secure sandbox service built on RustVMM and KVMKVMA Linux kernel module that turns the kernel into a hypervisor, letting a process run fully isolated virtual machines using hardware virtualisation extensions. Cyber tools use it to sandbox execution environments at near-native speed. that creates hardware-isolated MicroVM sandboxes in under 60ms with less than 5MB memory overhead.
host:
quota:
paused_resource_release_ratio: 1
sandbox = Sandbox.create(network={"allow_public_traffic": False}, lifecycle={"timeout": 300})
bash create.sh --mode upgrade
cubeNode:
network:
mtu: 1450
sandbox.connect(timeout=10)
[cow.s3]
enable = true
redis:
db: 2
sandbox = Sandbox.create(distribution_scope='zone-us-east-1')
await sandbox.setTimeout(Sandbox.NEVER_TIMEOUT);
cubemastercli node isolate <node-id>
cubemastercli node unisolate <node-id>
# Python SDK
sandbox = await client.create(options=CreateOptions(timeout=NEVER_TIMEOUT))
# Adjust an already-running sandbox
await sandbox.set_timeout(NEVER_TIMEOUT)
# cubemaster config (yaml)
host_mount:
allowed_prefixes:
- /data/shared/
- /data/project-a/
# '/' is explicitly forbidden and will be rejected at admission
# terraform.tfvars
TENcentCLOUD_CUBE_PROXY_REPLICAS = 3
cube_lifecycle_manager_replicas = 1
cube_lifecycle_manager_discovery_refresh_interval = 30
curl -X POST https://<cube-api>/cube/sandbox \
-H 'Content-Type: application/json' \
-d '{"network": {"allow_public_traffic": false}}'
# Response includes traffic_access_token; pass it on subsequent dataplane calls:
curl https://<cube-proxy>/<sandbox-id>/... \
-H 'cube-traffic-access-token: <token>'
bash install.sh --mode=upgrade
cubecli cubebox logs --tail 100 --stderr <id>
CUBEMASTER_DISK_SPACE_SAFETY_MARGIN=2.0 cubemaster serve
CUBE_SANDBOX_NETWORK_CIDR=10.200.0.0/16 bash one-click-install.sh
CUBE_SANDBOX_NETWORK_CIDR=192.168.100.0/24 CUBE_SANDBOX_NETWORK_CIDR_SKIP_CONFLICT_CHECK=1 bash one-click-install.sh
ONE_CLICK_SKIP_PVM_CHECK=1 bash one-click-install.sh
# In your .env file, set the desired ports before running install.sh:
CUBE_SANDBOX_MYSQL_PORT=3307
CUBE_SANDBOX_REDIS_PORT=6380
bash install.sh
Summary
CubeSandbox is an open-source, Apache 2.0-licensed sandbox service that gives AI agents isolated, hardware-level execution environments to run code in, self-hosted as a cluster of components (CubeMaster, Cubelet, CubeProxy) with a systemd-based installer, a Web UI, and Go/Python SDKs for programmatic control. It targets teams building or operating AI agent infrastructure who need to run untrusted, agent-generated code without it touching the host, rather than security teams doing manual analysis. Its README describes it as E2B-compatible and positions it within CNCF's AI-native infra landscape, with features like copy-on-write snapshots, an OpenResty-based egress proxy for credential injection and domain filtering, and Prometheus metrics for cluster monitoring. First committed in 2026, it already has 68 contributors and 16 releases in the past year, the latest 28 days ago, suggesting active development.
CubeSandbox is a secure sandbox service built on RustVMM and KVM that creates hardware-isolated MicroVM sandboxes in under 60ms with less than 5MB memory overhead.
How CubeSandbox helps
Which of my agent's outbound connections are actually leaving the sandbox, and to where?
the egress proxy logs every L7 request as structured JSON with domain, route, and body detail, giving a per-sandbox audit trail of what left the box and through which allow/deny rule it passed
Can an agent I'm running get to a credential without ever seeing it in its own code or environment?
credentials are injected at the proxy layer per egress rule rather than into the sandbox, so anything captured in logs or by the agent itself shows only a redacted placeholder
Did an agent's runaway or misbehaving process actually stay contained, or did it touch the host?
each sandbox runs its own dedicated kernel inside a MicroVM boundary, so a compromise or crash inside one sandbox has no path to the host or to other sandboxes
What was running in a sandbox right before something went wrong, and can I get back to that exact state?
copy-on-write and incremental memory snapshots let a sandbox be checkpointed and rolled back to a prior point-in-time state, or forked to explore what would have happened differently
Are all my cluster nodes running compatible versions of the sandbox components?
the version matrix reports guest-image, agent, kernel and control-plane versions per node and surfaces skew, and template compatibility checks flag replicas whose node doesn't match what the template expects
How many concurrent agent sandboxes can this cluster actually hold before I run out of resources?
Cubelet reports live CPU, memory and disk usage per node to CubeMaster, and the low per-sandbox memory overhead from page sharing determines how many resident instances a given node can carry
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for CubeSandbox, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail CubeSandbox puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
cubesandbox.com, every changeTencent Cloud's 2 pages as they looked each month from October 2026 to October 2026: 2 renders, 0 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
17 entries
No entries match these filters.
- October 20263
- September 20262
- August 20261
- July 20263
- June 20263
- May 20263
- April 20262
Project health
Issue, contributor and maintainer activity in TencentCloud/CubeSandbox, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 120 +120 vs prior 12 months
- Maintainers 16 +18 joined · −2 left, last 12 months
- Bus factor 4 committers behind half the commits
- Community-filed 78% of issues opened, last 12 months
- Median time to close 12 days first maintainer reply 23 hours
- Open backlog 65 of 419 issues ever filed
- Issues opened / month 22 · 14 communitymaintainers
- Open backlog 65
- Contributors / month 40
- Commits / month 136
- Stars 12,590
- bugs 57%
- features 20%
- questions 7%
- docs 1%
- other 15%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.