In v0.6.0, we brought CubeSandbox into Kubernetes and delivered the E2B-compatible Volume framework. v0.7.0 addresses the two things production users care about most: letting sandboxes flow across machines, and letting upgrades no longer break existing assets.
Read moreAgent RL rollout places different demands on sandboxes than ordinary Agent services: every trajectory needs a clean, isolated execution environment; lifecycles are minute-scale; volume is massively parallel; and the sandbox may run arbitrary model-generated code. Based on a 128-core 251 GiB machine and 1-core 4096 MiB sandbox specs, the Unisound team derived three sets of numbers: a scheduling ceiling of 117, a no-oversell safety boundary of 58, and a measured steady state of 80-100. This article records the full process from spec configuration and scheduling parameter derivation to measured bottlenecks.
Read moreCreating a sandbox takes a single API call. Deleting one requires answering a string of questions: does it still have an active session? Is this cleanup request a latecomer? Who collects sandboxes left behind by crashed replicas? The Guangdong Rising team consolidated the sandbox capabilities of two product lines into a standalone service — the sandbox execution layer of the SIN PaaS (AI platform) — and answered these questions with leases, fencing tokens, tri-color mark-and-sweep collection, and admission control.
Read moreA single financial research Agent run can last tens of seconds to several minutes, reading research methodologies and data definitions, calling data APIs, running scripts, generating intermediate files, and having the model synthesize results. The sandbox carrying it can't just 'run a snippet of code' — it must contain the complete Agent loop in an isolated environment. This article introduces three core use cases of CubeSandbox in Hongze's 4as Agent.
Read moreA resident Agent application needs the sandbox to remember not just task artifacts, but also the Agent's own configuration, conversation history, and a set of frequently invoked Skills. But sandboxes are inherently ephemeral — restarts, pauses, and migrations can zero out all of this state. This article shares the pitfalls and solutions from the Shanghai Yangpu New Energy AI team's migration of Hermes Studio onto CubeSandbox.
Read moreReplacing a cloud Agent product's sandbox from Daytona to Cube looks like just swapping to a faster tool. But in practice, the migration changes three things: the sandbox deployment model (SaaS to self-hosted), the sandbox startup model (per-session rebuild to snapshot restore), and more fundamentally — the sandbox's role in the product architecture (from 'tool execution container' to 'independent runtime environment').
Read moreIn early 2026, OpenClaw single-handedly sparked a local terminal Agent craze, and people began handing over file systems, browsers, email, terminals, and various account permissions to Agents. But behind the hype lies a risk more immediate than model hallucination. This article is InfoQ's exclusive interview with Jin Feng, head of Tencent Cloud's IaaS Frontier Technology Team, exploring Cube's evolution from Serverless infrastructure to Agent sandbox and the path from 'can run' to 'production-ready.'
Read moreAgent browser runtime is a 'composite workload.' It imposes four core hard requirements on AI Agent sandboxes: can outbound network reach the real internet, is the startup sequencing stable under batch creation, can per-sandbox runtime state be dynamically injected, and can real capacity be accurately perceived. The Lexmount team hit and resolved all four of these problems when integrating their browser runtime with CubeSandbox.
Read moreToday (July 24), Cube Sandbox v0.6.0 is officially released. This version merges 92 commits from 31 contributors, bringing six core features. Among them, K8s and Volume support are the two most requested by the community and the biggest highlights of this release.
Read moreOn July 3, Tencent Cloud open-sourced the AI Agent secure sandbox Cube Sandbox v0.5.0. Native Arm support — one of the headline features — has been merged upstream with substantial investment from the Arm engineering team. Developers can now build, deploy, launch, and run typical sandbox workloads end-to-end on AArch64 servers.
Read moreIf v0.3.0 solved 'fast' (millisecond snapshot / clone / rollback), and v0.4.0 solved 'governance' (L7 egress control + observability + cluster consistency), then v0.5.0 aims to solve 'stable, efficient, broad'. With 116 commits from 26 contributors, v0.5.0 brings four core features: AutoPause/AutoResume sandbox lifecycle automation, ARM64 full-stack native support, Tencent Cloud Terraform one-click cluster deployment, and network security enhancements.
Read moreHow does Cube Sandbox achieve sub-second snapshots of tens-of-GiB filesystems, memory checkpoints that write only a fraction of total guest RAM, and cloning that creates N independent copies with near-zero disk growth? This article dissects the three interlocking kernel mechanisms — XFS reflink, /proc/pagemap anonymous page detection, and soft-dirty bit — that power Cube v0.3.0's snapshot, clone, and rollback capabilities.
Read moreAI Agents give machines autonomous execution power — and open a Pandora's box of data exfiltration and credential abuse. CubeSandbox builds an end-to-end network security system — from virtual switching to application-layer auditing — on a foundation of KVM MicroVM isolation, an eBPF in-kernel network datapath, and L7 proxy deep inspection. This article dissects the design and implementation of core components like CubeVS, CubeProxy, and CubeEgress, and shows how Cube balances open execution with security and control.
Read moreWhen software consumers shift from humans to Agents, the requirements change fundamentally — creating a service is no longer an ops task, but part of the inference-and-action loop. Neon's $1B acquisition by Databricks validates this thesis. Cube Sandbox turns "fast spawn, clone, and rollback" into a general-purpose runtime capability, letting any traditional software service become Agent-friendly with near-zero code changes.
Read moreFollowing v0.3.0's snapshot/clone/rollback trio, v0.4.0 ships 58 commits from 15 contributors centered on three questions: egress governance (CubeEgress L7 proxy + credential injection + domain filtering + access audit), observability (container log forwarding via vsock), and consistency (node component version matrix + template compatibility checks). Also delivers a 41% reduction in network P99 latency and cuts template build peak disk from 4.2x to 1.2x image size.
Read morePerformance benchmark data for CubeSandbox on a Tencent Cloud SA9.4XLARGE32 standard CVM (PVM kernel), covering sandbox creation from template (cold-start latency, concurrency scaling, single-host density) and Snapshot operations (Snapshot creation, create-from-snapshot, Rollback, Clone, Pause/Resume). Each section includes the exact commands needed to reproduce the results.
Read moreIn modern AI Agent stacks, the sandbox plays the role of a "secure runtime" — executing model-generated code and tool calls. Cube Sandbox v0.3.0, with 82 commits from 22 contributors, is a foundational architecture upgrade aimed at high-concurrency, long-horizon, and reinforcement-learning workloads. Around three new SDK primitives — snapshot / clone / rollback — it brings "environment replication" and "error recovery" down from minutes to milliseconds.
Read morePerformance benchmark data for CubeSandbox on a real bare-metal node, covering sandbox creation from template (cold-start latency, concurrency scaling, single-host density) and Snapshot operations (Snapshot creation, create-from-snapshot, Rollback, Clone). Each section includes the exact commands needed to reproduce the results.
Read moreA community walkthrough on preparing the prerequisite environment — OS choice, kernel version, dependencies — for deploying Cube Sandbox in PVM mode on a standard cloud VM running OpenCloudOS 9. (Article in Simplified Chinese.)
Read moreHow a system originally forged in years of Serverless workloads — high density, high elasticity, high concurrency, strong isolation — extends naturally into the Agent era. This post walks through Cube's core designs (distributed scheduling + node-local bin-packing, resource pooling, frontend/backend decoupling, snapshot restore + lazy load, resource sharing, full-stack lock optimization, native security, and reusing VM resources) and the new capabilities for Agent workloads (low-latency code execution, Agentic RL, image acceleration, snapshot-based branch cloning, event-level snapshot & rollback).
Read moreFollowing v0.2.0, Cube Sandbox shipped v0.2.2 on May 18. This release extends E2B compatibility from the SDK layer down to the wire-protocol layer, fixes seven recurring stability issues from the v0.1.x era, and lands the first round of CVE remediations for the 0.2 series.
Read moreA community walkthrough covering the full deployment of Cube Sandbox on an AWS EC2 nested-virtualization instance (c8i.2xlarge) — environment setup, three required patches (Cubelet, CubeShim, and Guest image), service bring-up, template creation, and sandbox creation via the E2B-compatible SDK. Note: original article is in Simplified Chinese.
Read moreWe are launching a blog to share release notes, technical deep-dives, and community stories around Cube Sandbox.
Read more