E2B Sandbox

license

Apache-2.0(OSI

source

public(SDKs+infra, Terraform self-host)

managed-tier

e2b.dev hosted sandbox cloud (proprietary)

core features withheld

no — 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

E2B's SDKs are published under MIT and the runtime behind its hosted cloud under Apache-2.0, and the runtime repository says the same code serves the public cloud, dedicated enterprise deployments and the single-machine Embed package. The paid tiers add capacity and deployment choices -- custom CPU and RAM, longer sessions, more concurrent sandboxes, bring-your-own-cloud deployment -- rather than any capability withheld from the source.

• 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.

• 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-09-29

  The pricing page tiers differ in capacity: Hobby lists "Default sandbox CPU and RAM" and "Sessions up to 1 hour", Pro lists "Custom sandbox CPU and RAM", "Sessions up to 24 hours" and "100 concurrent sandboxes, expandable to 1,100", and Enterprise lists "Custom sizes, plus BYOC deployment".

• 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://raw.githubusercontent.com/e2b-dev/E2B/main/LICENSE recorded 2026-09-29

  The root LICENSE of the e2b-dev/E2B SDK repository is the Apache License, "Version 2.0, January 2004", with the standard "TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION".

• https://raw.githubusercontent.com/e2b-dev/E2B/main/packages/js-sdk/LICENSE recorded 2026-09-29

  The LICENSE in the JavaScript SDK package directory of e2b-dev/E2B is the "MIT License", opening "Permission is hereby granted, free of charge, to any person obtaining a copy of this software".

• https://raw.githubusercontent.com/e2b-dev/E2B/main/packages/python-sdk/LICENSE recorded 2026-09-29

  The LICENSE shipped in the Python SDK package directory of e2b-dev/E2B is the "MIT License" with "Copyright (c) 2025 FOUNDRYLABS, INC.", not the Apache-2.0 text at the repository root.

• https://raw.githubusercontent.com/e2b-dev/E2B/main/README.md recorded 2026-09-29

  The SDK repository README points self-hosters at the infra repository and states "The infrastructure is deployed using Terraform."

• https://raw.githubusercontent.com/e2b-dev/infra/main/LICENSE recorded 2026-09-29

  The LICENSE of the e2b-dev/infra repository (now served as e2b-dev/runtime) is the Apache License, "Version 2.0, January 2004", byte-identical to the SDK repository root LICENSE.

• https://raw.githubusercontent.com/e2b-dev/infra/main/README.md recorded 2026-09-29

  The infra README calls it "The open-source runtime behind" E2B, describes it as "the complete backend that powers" E2B Cloud including "the control-plane API, the per-node orchestrator that drives Firecracker", says "It is written in Go, licensed under Apache-2.0" and "The same code serves the public cloud, dedicated enterprise deployments, and the single-machine".

• https://raw.githubusercontent.com/e2b-dev/runtime/main/embed/README.md recorded 2026-09-29

  The E2B Embed README in the runtime repository offers "A complete E2B, sandboxes included, on one machine you own." via Docker Compose, Terraform on GCP or AWS and Kubernetes, while calling all four "single-machine evaluation packages, not deployment patterns". Searched the body for license key, paid, pricing, commercial and subscription: none.

Adoption is measured as PyPI downloads of the e2b package, corroborated by E2B's own reporting of sandboxes started, its adoption among Fortune 100 companies, and named production users such as Perplexity, Hugging Face, Manus and Groq. The vendor's figures are not independently verified.

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

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

• 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.

• 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 downloads in the trailing 30 days.

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

  ~4,583,328 downloads last month

E2B runs each sandbox as its own Firecracker microVM, with sessions of up to 24 hours on the Pro plan, pause and resume that keeps memory as well as the filesystem, and configurable CPU and RAM. Its isolation comes from Firecracker, the runtime that sets the frontier of the category, and as a managed layer built on that runtime E2B sits a step below it.

• https://e2b.dev/ recorded 2026-09-29

  Homepage says the microVM runtime is "built on Firecracker with dedicated kernels and a custom memory and snapshot layer" and is "Battle-tested across 1B+ sandboxes".

• https://e2b.dev/docs/sandbox recorded 2026-09-29

  Sandbox docs state "Sandboxes can run continuously for up to 24 hours (Pro) or 1 hour (Base)."

• https://e2b.dev/docs/sandbox/persistence recorded 2026-09-29

  Persistence docs say a sandbox can be paused and resumed "from the exact state it was in, including the filesystem and the memory, so running processes and loaded variables survive."

• https://e2b.dev/enterprise recorded 2026-09-29

  Enterprise page says "Every agent session runs in its own Firecracker microVM." with egress control per sandbox.

• https://e2b.dev/pricing recorded 2026-09-29

  Pricing page lists "Sessions up to 24 hours", "100 concurrent" sandboxes and "Custom sandbox CPU and RAM" for Pro versus "Default sandbox CPU and RAM" on Hobby.

• 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://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.