Agent Sandboxesagentsandboxes.org
Head-to-head

CubeSandbox vs SPACE

Answer in brief

Choose CubeSandbox for self-hosted, E2B-compatible microVM sandboxes at high density on your own Linux hosts; choose SPACE for operators who want a Firecracker sandbox control plane with asynchronous lifecycle operations and E2B SDK compatibility. CubeSandbox uses RustVMM/KVM microVM isolation and is open source; SPACE uses Firecracker microVM isolation and is open source.

By the Agent Sandboxes editors · Updated

Key differences between CubeSandbox and SPACE

  • Isolation: CubeSandbox uses RustVMM/KVM microVM; SPACE uses Firecracker microVM.
  • Company headquarters: Tencent is based in Shenzhen, China; Perplexity is based in San Francisco, United States.
  • SDKs and interfaces: Only CubeSandbox lists JavaScript/TypeScript and Go.

What they have in common

  • Both are open-source projects you run yourself.
  • Both use microVM isolation.
  • Both are open source.
  • Both can be self-hosted.
  • Both support snapshots.
  • Both can pause and resume a sandbox.
  • Both list Python, REST API and CLI.

CubeSandbox vs SPACE at a glance

AttributeCubeSandboxSPACE
What it isTencent Cloud's open-source, E2B-compatible sandbox platform that runs each sandbox in a RustVMM/KVM microVM with copy-on-write snapshots.Perplexity's open-source sandbox platform that runs code in Firecracker microVMs with pause, suspend-to-snapshot and an E2B compatibility layer.
TypeOpen-source projectOpen-source project
IsolationDedicated microVM per sandbox with its own guest kernel, built on RustVMM and KVM (CubeHypervisor), with eBPF-based network isolation and egress filteringFirecracker microVM per sandbox with its own writable filesystem ("Firecracker isolates guest execution")
Open sourceYes (Apache-2.0)Yes (Apache-2.0)
Self-host / BYOCYes / NoYes / No
SDKsPython, JavaScript/TypeScript, Go, REST API, CLIPython, REST API, CLI
Cold start (vendor claim)README: sandboxes created in under 60 ms at single concurrency, average 67 ms / P95 90 ms / P99 137 ms at 50 concurrent creations, measured on bare metal; memory overhead claimed under 5 MB per sandboxNo boot time figure published; warm pools keep booted sandboxes ready and the native create readiness budget is 5 seconds
Max sessionNot documentedDefault idle suspend after 6 hours without access or command activity; lifecycle operations have a 30-minute deadline
PersistenceCubeCoW copy-on-write snapshot engine with cloning, rollback and forking from saved state; AutoPause/AutoResume for idle sandboxes; cross-node pause/resume with an S3 backend (v0.7.0); creating sandboxes from snapshots is a preview; pluggable volumes (S3, host mounts, shared block)Paused keeps VM memory resident on the worker (not durable); suspended writes a snapshot of memory, runtime state and root filesystem and releases VM resources; wake restores either; snapshots, checkpoint and rollback are incubating and hidden unless enabled per organisation
Snapshots / pauseYes / YesYes / Yes
GPUNo — GPU sandboxes are on the roadmap, not availableNot documented
NetworkingeBPF virtual switch (CubeVS) for inter-sandbox isolation and policy; CubeEgress gateway for L7 domain filtering, credential injection and auditing; per-sandbox traffic tokensEgress governed by NetworkPolicyV1 destination rules with optional per-policy TLS interception; operator egress profiles; in the Kind install sandbox pods are restricted to public IPv4 and cluster DNS
PricingFree to self-host (Apache-2.0); no hosted offering is describedFree to self-host (Apache-2.0); no hosted offering described
Free tierFree to self-hostFree to self-host
ComplianceNot documentedNot documented
RegionsSelf-hosted; Terraform one-click deployment on Tencent CloudSelf-hosted; local Kind cluster install documented, with an AWS EKS reference deployment in the repository
Company headquartersShenzhen, Guangdong, ChinaSan Francisco, California, United States
Good fit forSelf-hosted, E2B-compatible microVM sandboxes at high density on your own Linux hostsOperators who want a Firecracker sandbox control plane with asynchronous lifecycle operations and E2B SDK compatibility

Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.

Which should you choose?

Reasons to choose CubeSandbox

  • You want E2B-compatible SDKs against infrastructure you run yourself
  • You need microVM isolation with snapshot forking and rollback for agent branching or evaluation
  • You run on Tencent Cloud or want a Terraform path onto it
  • You need credential injection at the egress gateway so keys never reach the sandbox

Reasons to choose SPACE

  • You want Firecracker isolation with pause, suspend and wake semantics spelled out
  • You need egress policy with TLS interception and per-organisation feature gating
  • You have existing E2B Python SDK code and want to point it at your own cluster
  • You run on Kubernetes (an EKS reference exists) or can run the direct adapter without it

Trade-offs to check first

  • CubeSandbox: Self-hosted; no managed service is documented, so you operate the hypervisor fleet
  • CubeSandbox: Linux hosts only, with x86_64 PVM for the easy path and OpenCloudOS or TencentOS recommended
  • SPACE: Linux x86_64 hosts with KVM only; the install does not run on macOS
  • SPACE: Boot time figures are not published and no hosted version is documented

Both are worth piloting with your own image and region. See the full CubeSandbox profile and SPACE profile, or the complete comparison.

More comparisons

Frequently asked questions

Is CubeSandbox or SPACE better for AI agents?
Neither is better for every workload. CubeSandbox suits self-hosted, E2B-compatible microVM sandboxes at high density on your own Linux hosts. SPACE suits operators who want a Firecracker sandbox control plane with asynchronous lifecycle operations and E2B SDK compatibility.
What is the difference between CubeSandbox and SPACE?
CubeSandbox uses RustVMM/KVM microVM; SPACE uses Firecracker microVM. Tencent is based in Shenzhen, China; Perplexity is based in San Francisco, United States. Only CubeSandbox lists JavaScript/TypeScript and Go.
Which is open source, CubeSandbox or SPACE?
Both are open source (CubeSandbox: Apache-2.0; SPACE: Apache-2.0).
How do CubeSandbox and SPACE isolate code?
CubeSandbox: Dedicated microVM per sandbox with its own guest kernel, built on RustVMM and KVM (CubeHypervisor), with eBPF-based network isolation and egress filtering. SPACE: Firecracker microVM per sandbox with its own writable filesystem ("Firecracker isolates guest execution").
How does CubeSandbox pricing compare with SPACE?
CubeSandbox: Free to self-host (Apache-2.0); no hosted offering is described. SPACE: Free to self-host (Apache-2.0); no hosted offering described. Rates change, so check the CubeSandbox and SPACE pricing pages before deciding.
Do CubeSandbox and SPACE support GPUs?
CubeSandbox: No — GPU sandboxes are on the roadmap, not available. SPACE: Not documented.
Can you self-host CubeSandbox or SPACE?
Yes, both can be self-hosted.
How long can sessions run on CubeSandbox and SPACE?
CubeSandbox: Not documented. SPACE: Default idle suspend after 6 hours without access or command activity; lifecycle operations have a 30-minute deadline.
Do CubeSandbox and SPACE support snapshots or pause and resume?
CubeSandbox: snapshots yes, pause and resume yes. SPACE: snapshots yes, pause and resume yes.

Sources

  1. github.com/TencentCloud/CubeSandbox
  2. cubesandbox.com
  3. cubesandbox.com/guide/quickstart
  4. github.com/TencentCloud/CubeSandbox/releases
  5. github.com/perplexityai/SPACE
  6. space.docs.perplexity.ai/
  7. github.com/perplexityai/SPACE/blob/main/docs/installation.md
  8. github.com/perplexityai/SPACE/blob/main/docs/architecture.md

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

Agent Sandboxes. (2026). CubeSandbox vs SPACE. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/cube-sandbox-vs-perplexity-space/