E2B Sandbox

license

Apache-2.0(OSI)

source

public(SDKs+infra, Terraform self-host)

managed-tier

e2b.dev hosted sandbox cloud (proprietary)

core-gated

ungated(the infrastructure powering E2B Cloud is itself published Apache-2.0 as e2b-dev/infra with no carve-out, and the paid tiers are capacity and session-length limits on the hosted service rather than features held back from the source)

Apache-2.0 SDKs and infrastructure with a managed cloud sold beside them. Nothing in the core is held back, and that reading rests on both repos and the pricing page. e2b-dev/E2B carries four Apache-2.0 LICENSE files, all copies of the root, and no carve-out - but the decisive fact is the second repo: e2b-dev/infra, described by the org as "Infrastructure that is powering E2B Cloud", is public, Apache-2.0 and equally free of an enterprise directory. The managed product runs the published code. The pricing tiers sell capacity and session length - CPU/RAM customization, 24-hour sessions, 100 concurrent sandboxes rising to 1,100 - and name no capability the source withholds.

• https://github.com/e2b-dev/E2B recorded 2026-06-04

  Apache-2.0 license; open source sandbox infra + Terraform self-host; managed cloud at e2b.dev

• https://api.github.com/repos/e2b-dev/E2B/git/trees/main?recursive=1 recorded 2026-08-12

  Full untruncated recursive tree, 993 entries. Four license paths, all Apache-2.0 copies of the root: LICENSE, packages/cli/LICENSE, packages/js-sdk/LICENSE, packages/python-sdk/LICENSE. No ee/, enterprise/, commercial/ or proprietary/ path.

• https://api.github.com/repos/e2b-dev/infra/git/trees/main?recursive=1 recorded 2026-08-12

  The repo the org describes as "Infrastructure that’s powering E2B Cloud" is public and Apache-2.0: 2,809-entry untruncated tree, one LICENSE, no enterprise/, ee/, commercial/ or proprietary/ path. The control plane behind the managed product is therefore the same published code, not a closed package beside it.

• https://e2b.dev/pricing recorded 2026-08-12

  Three tiers - Hobby (free + usage), Pro ($150/mo + usage), Ultimate (custom). What Pro adds is capacity, not capability: "Customize your Sandbox CPU & RAM", "Up to 24-hour sandbox session length", "Up to 100 concurrently running sandboxes", "Ability to purchase extra concurrency up to 1,100". The page names no feature absent from the open source and mentions no enterprise edition.

• https://api.github.com/repos/e2b-dev/E2B recorded 2026-08-12

  Repo metadata: language Python, license spdx_id Apache-2.0, 13,357 stars, default branch main.

PyPI reports 5,845,335 downloads in the trailing 30 days for the e2b package, solidly inside the 1M-10M band and nowhere near the 10M floor for level 5. Vendor figures corroborate: 1B+ sandboxes started, 94% of Fortune 100 as customers, "7M+ monthly downloads" across the Python and npm SDKs, and named production users including Perplexity, Hugging Face, Manus, Groq, Rogo, Lindy and Gumloop. That puts it at level 4, with reach in the 1M-10M band.

• https://pypistats.org/packages/e2b recorded 2026-06-04

  ~4,583,328 downloads last month

• https://e2b.dev/ recorded 2026-06-04

  1B+ sandboxes started; named production customers (Perplexity, Hugging Face, Manus, Groq)

• https://pypistats.org/api/packages/e2b/recent recorded 2026-08-13

  {"last_day":253438,"last_month":5845335,"last_week":1377059} for the e2b package. 5.85M in the trailing 30 days bands at 1M-10M, level 4 on the software adoption scale.

• https://e2b.dev/ recorded 2026-08-13

  The stat band still reads "94% of Fortune 100 companies", "1b+ started sandboxes", and adds "7M+ monthly downloads". Named case studies include Perplexity, Hugging Face, Manus, Groq, Rogo, Lindy and Gumloop.

VM-grade isolation (Firecracker) is the strongest tier in the feature matrix, with broad SDK and runtime support and proven scale: e2b.dev states "Each sandbox is powered by Firecracker, a microVM made to run untrusted workflows", offers sessions up to 24 hours with configurable CPU and RAM, and reports 1b+ started sandboxes. It sits one rung below Firecracker itself, the frontier-definer it builds on, so 4 rather than 5. Independent ComputeSDK TTI benchmarks put E2B at a 0.66s median time-to-interactive, 12th by median of 24 providers, where an earlier run had it at ~370ms and 7th of 19: still sub-second, so the fast cold-start holds, but the corroboration is weaker than it was and the band now rests on isolation strength and scale rather than on speed.

• https://e2b.dev/ recorded 2026-06-04

  each sandbox powered by Firecracker microVM; 1B+ sandboxes started

• https://www.computesdk.com/benchmarks/sandboxes/ recorded 2026-07-09

  ComputeSDK TTI leaderboard (independent, 100 iters/day, 2026-07-09 run): median time-to-interactive ~370ms sequential / ~470ms burst @100 concurrent; 7th-fastest of 19 providers

• https://e2b.dev/ recorded 2026-08-13

  "Each sandbox is powered by Firecracker, a microVM made to run untrusted workflows." Sessions run up to 24 hours, sandboxes expose configurable CPU and RAM, and the stat band reports 1b+ started sandboxes.

• https://www.computesdk.com/benchmarks/sandboxes/ recorded 2026-08-13

  ComputeSDK TTI leaderboard, run of 2026-08-07, 24 providers. E2B posts a 0.66s median, 0.96s P95, 1.02s P99 and 100% success for a composite of 92.1 - 12th by median.