CreateOS Sandbox vs Tencent Cloud Agent Runtime
Pick Tencent Cloud Agent Runtime if you already run on Tencent Cloud, serve users in mainland China, or need very dense sandbox bursts for RL training and evaluation. Pick CreateOS Sandbox if sessions must outlast 24 hours, you want published per-plan limits and USD pricing, or you need an outbound allowlist by host, IP or CIDR.
Pricing at a Glance
CreateOS rates verified 17 October 2026. Tencent Cloud Agent Runtime pricing as published on 17 October 2026. Rates billed per GB rather than per GiB, or as bundled sizes, are quoted as published rather than converted.
CreateOS Sandbox
- Compute
- $0.0362 /vCPU-hr
- Memory
- $0.0116 /GiB-hr
Tencent Cloud Agent Runtime
Tencent bills per second at CNY 0.000081 per core-second and CNY 0.000025 per GiB-second, plus CNY 0.0021 per GiB-hour for disk beyond 15 GiB free per running instance, as of 17 October 2026.
Where CreateOS Sandbox Fits Better
What CreateOS Sandbox brings to this matchup, with a plain note on where Tencent Cloud Agent Runtime has the edge.
No lifetime cap, where a Tencent sandbox tool tops out at 24 hours.
Per-plan size and concurrency limits are published in English: up to 8 vCPU / 16 GB and 30 concurrent sandboxes on Enterprise.
Outbound rules by host, IP, CIDR or wildcard, enforced outside the VM; Tencent's pages describe a PUBLIC or VPC network mode without allowlist semantics.
Where Tencent Cloud Agent Runtime is strong
Tencent built Agent Runtime for very dense, bursty agent workloads such as RL rollouts, with E2B protocol compatibility, many prebuilt environments (code, browser, OSWorld desktop, Android, SWE-bench) and an Apache-2.0 engine, CubeSandbox, that you can run yourself.
Which to Pick
Pick CreateOS Sandbox if
- Agent sessions need to run longer than 24 hours.
- You want English docs with published per-plan limits and prices in USD.
- You need an egress allowlist for untrusted code.
Pick Tencent Cloud Agent Runtime if
- Your workloads already run on Tencent Cloud or serve mainland China.
- You need prebuilt OSWorld, Android or SWE-bench environments for training and evaluation.
- You want an open-source engine (CubeSandbox, Apache 2.0) you can self-host.
Head-to-Head Comparison
Every dimension side by side, checked on 17 October 2026 against each vendor's own docs and pricing pages. "Not published" means we could not find it on the vendor's pages, not that the feature is missing.
| Dimension | CreateOS Sandbox | Tencent Cloud Agent Runtime |
|---|---|---|
| Isolation | Firecracker micro-VM with its own guest kernel, root filesystem and network identity | VM-level isolation (vendor-stated); the open-source CubeSandbox engine uses RustVMM and KVM with a dedicated guest kernel |
| Pause and resume | Saves disk, memory and CPU state; vCPU stops billing while paused, memory and storage still bill | Pause with or without memory; compute stops billing and the paused state bills as storage |
| Fork | Fork a paused sandbox into many independent copies, each with its own id and IP | Not published for the managed service (CubeSandbox v0.7 adds create-from-snapshot as a preview) |
| Outbound network default | Open with no rules; deny-by-default once any host, IP, CIDR or wildcard rule exists, enforced on the host outside the VM | Set per sandbox tool: PUBLIC (internet) or VPC mode; no default or allowlist semantics found |
| Inbound access | Closed by default; opt-in public HTTPS URL, plus API-authenticated shell and port tunnels | Not published |
| Largest size | 8 vCPU / 16 GB on Enterprise (Pro 8 vCPU / 8 GB, Beginner 4 / 4, Free 1 / 1) | Not published (billing examples use 1 core / 2 GiB and 2 cores / 4 GiB) |
| Concurrency | Free 1, Beginner 5, Pro 20, Enterprise 30; paused sandboxes count toward the cap | Quota exists, value not published; 'hundreds of thousands of instances per minute' (vendor-stated) |
| Session length | No lifetime cap; optional idle auto-pause from 60 s to 24 h, off by default | Default timeout 5 minutes, maximum 24 hours |
| Billing | Per second: $0.03616363/vCPU-hr, $0.01159025/GiB-hr, storage $0.0001584/GB-hr; no egress fees, 50 GiB bandwidth budget per sandbox | Per second for CPU and memory in CNY, hourly settlement; 15 GiB system disk free per running instance |
| SDKs and interfaces | TypeScript, Go, Python, Rust, C#, Java (all but TypeScript pre-1.0), CLI, MCP, REST | SDK, API, CLI and MCP server; compatible with the E2B SDK by swapping domain and key |
Common Questions
How long can a Tencent Cloud Agent Runtime sandbox run?
Up to 24 hours. The CreateSandboxTool API defaults to a 5-minute timeout with a 24-hour maximum, and the product page states a 24-hour instance lifetime. CreateOS Sandbox has no lifetime cap and offers an optional idle auto-pause from 60 seconds to 24 hours.
Does Tencent Cloud Agent Runtime work with the E2B SDK?
Yes, Tencent's FAQ says you can use the E2B SDK by swapping the domain and key. CreateOS Sandbox does not claim E2B compatibility; it ships its own TypeScript, Go, Python, Rust, C# and Java SDKs, with every language except TypeScript still pre-1.0.
Are Tencent Agent Runtime prices quoted in US dollars?
No. Tencent quotes CNY 0.000081 per core-second and CNY 0.000025 per GiB-second on its China site, billed per second with hourly settlement. CreateOS Sandbox quotes $0.03616363 per vCPU-hour and $0.01159025 per GiB-hour, billed per second, the same on every plan.
Sources
Checked 17 October 2026.
See CreateOS Sandbox for yourself
Book a demo, or explore the Sandbox and its pricing.