↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Sandboxing/

E2B

Author
glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 5 minutes read (~946 words)
agent-curated 361 firecracker 1 fully-ai-generated 463 hosted-api 1 isolation 9 llm=glm-5.3-flash 372 microvm 3 research-note 331 sandboxing 17 security 11
Table of Contents

E2B is the hosted sandbox API that gives each agent session an isolated Firecracker microVM with its own kernel, created through Python or JavaScript SDK calls and billed per second, and it is the interface the self-hosted members of this category advertise compatibility with.

E2B is this category’s compatibility baseline rather than a competitor on mechanism, and its 2026 move, open-sourcing the runtime behind its cloud, turns the hosted-versus-self-hosted comparison into a choice of whose operator you run.

What it is
#

A cloud service plus SDKs where Sandbox.create() returns a full Linux machine: shell, filesystem, network, ports exposed as HTTPS sandbox URLs, and an optional desktop, usable from any model provider or agent framework. Every sandbox is a hardware-isolated Firecracker microVM booted by resuming a pre-booted snapshot, with memory pages served lazily through userfaultfd, so fresh creates, resumes, and forks of up to 100 copies take the same fast path. Egress is governed per sandbox through nftables with SNI/Host-inspecting domain allow and deny lists, and secrets stay in a vault that injects them at the egress proxy, so values never enter the sandbox filesystem. The cloud is SOC 2 Type II compliant with US, EU, and APAC regions; enterprise teams get BYOC on AWS, GCP, or Azure, a private-cloud control plane is in development, and E2B Embed is an Apache-2.0 single-node package (Docker Compose, Terraform, Kubernetes) that runs the whole stack on one x86-64 KVM Linux machine.

Status
#

Active and well funded: the SDK repo stands at 14,190 stars and the runtime repo at 1,679 stars as of 2026-10-06, the SDK repo created 2023-03-04 and pushed 2026-10-05, with @e2b/python-sdk at 2.52.1 (2026-10-05). A $21M Series A led by Insight Partners was announced 2025-07-28, $32M total, with company claims of 88 percent of the Fortune 100 signed up, hundreds of millions of sandbox sessions since October 2024, and named users including Hugging Face, LMArena, Perplexity, Groq, and Manus. Hacker News never embraced it: the 2024 launch thread drew 2 points, the category’s HN energy went to self-hosted challengers such as CubeSandbox’s 7-point launch pitching itself as the open-source E2B, and every traction number above is the company’s own.

Strengths
#

  • Hardware isolation by default on the hosted path, one Firecracker microVM per sandbox, where most self-hosted platforms make you opt into the hard boundary.
  • The snapshot-resume design is the fastest provisioning story in the category and the thing every compatibility claim tests against.
  • The credential vault at the egress proxy is the same design OpenShell and CubeSandbox advertise, operated for you instead of by you.
  • Broadest framework reach: it is the sandbox adapters target and the API self-hosted platforms reimplement, so examples and skills transfer.

Cautions
#

  • Per-second usage billing scales with agent appetite, the default sandbox is 2 vCPU and 4 GiB, and concurrency caps arrive fast: Hobby 20, Pro 100 before the $650 and $1,150 add-on tiers.
  • CPU-only, no GPU sandboxes, so RL and eval workloads needing GPUs go elsewhere.
  • The hosted tier is a dependency on one vendor’s uptime and regions, and Enterprise starts at a $3,000 monthly minimum.
  • No independent audit of the boundary itself exists; SOC 2 covers process, and the runtime’s operational record outside E2B’s own fleet is short.

Pricing
#

Hobby: free, one-time $100 usage credits, 20 concurrent sandboxes, 1-hour sessions, 10 GiB storage included. Pro: $150 per month plus usage, 100 concurrent, 24-hour sessions, 20 GiB storage; Pro+ and Pro++ add-ons at $650 and $1,150 per month raise concurrency to 600 and 1,100. Enterprise: custom, with a $3,000 monthly minimum and BYOC. Published usage rates as of 2026-10-06: $0.000014 per vCPU-second and $0.0000045 per GiB-second, storage included free; sandboxes configure 1 to 8 vCPU and 1 to 8 GiB, CPU-only.

Price history
#

Date Plan Change Source
2026-10-06 Hobby / Pro / Pro+ / Pro++ / Enterprise Baseline: Hobby free with $100 one-time credits; Pro $150 per month plus usage at $0.000014 per vCPU-second and $0.0000045 per GiB-second; Pro+ $650 and Pro++ $1,150 concurrency add-ons; Enterprise $3,000 monthly minimum. E2B pricing

Compared to
#

  • CubeSandbox: the self-hosted E2B-compatible microVM service; choose it when data residency or sustained volume beats operating a KVM fleet, E2B when zero operations matters.
  • Agent Sandbox: the Kubernetes orchestrator for the fleet you would otherwise rent; complementary, since agent-sandbox still needs you to run the cluster.
  • Modal sandboxes and other hosted APIs: E2B’s difference is the agent-native surface (desktop sandboxes, pause and fork, sandbox URLs) and being the API others target for compatibility.

Bottom line
#

Recommended for teams that want hardware-isolated agent execution with no infrastructure and can absorb usage-based billing; it remains the interface the rest of the category codes against. Not for GPU workloads, for $0-marginal-cost fleet scale, or for anyone unwilling to let a vendor operate the execution floor.

Changes
#

  • 2026-10-06 - Created, resolving the standing queue question after E2B served as the comparison baseline in four member notes without a note of its own; prices and counts as of 2026-10-06.

See also
#

References
#