Back to vendors
Entry priceHobby is free with a one time $100 credit, and Pro is $150 a month plus per second usage.Full pricing detail

E2B is an open source sandbox platform that gives AI agents isolated Firecracker microVMs to run code, use tools and operate desktops, in E2B's cloud, the customer's own cloud account, or self hosted.

E2B is an open source sandbox platform that gives AI agents isolated Linux machines to work in. An agent can execute generated code, run shell commands, work with files, install packages, reach the internet or operate a desktop without touching the customer's own infrastructure. E2B provides the compute, and the customer brings its own model and orchestration framework. E2B says more than 100,000 teams use it and more than 2 billion sandboxes have started on it. Customers include Hugging Face, Manus, Groq, ClickUp, Genspark, Lindy and Rogo, which runs 10,000 to 15,000 sandboxes at once, and Arena runs up to 600,000 sandboxes a day.

Every sandbox is its own Firecracker microVM with its own kernel. A sandbox can be paused and resumed later exactly as it was, filesystem and memory included, or snapshotted and forked, and volumes, in private beta, keep files across sandboxes. Auto resume restarts a paused sandbox when a request arrives, and lifecycle events go to the customer's webhook. Egress can be allowed or denied per sandbox, E2B Secrets injects credentials at the egress proxy so they never sit in the sandbox, and an MCP gateway gives the agent more than 200 tools from the Docker MCP Catalog. E2B Desktop sandboxes add a graphical Linux desktop with screen, mouse and keyboard for agents that use a computer.

E2B runs as a managed cloud on Google Cloud and AWS, with US regions by default and EU and Asia Pacific regions on request. Enterprise customers can run it inside their own AWS, Google Cloud or Azure account, and E2B Embed packages the Apache-2.0 runtime for a self hosted install. E2B holds SOC 2 Type II, with the report in its trust center, and signs HIPAA BAAs on Enterprise. Single sign on, SCIM and role based access are planned.

Pricing combines a plan with per second usage. Hobby is free with a one time $100 credit, Pro is $150 a month for longer sessions and higher concurrency, and Enterprise starts at a $2,000 monthly commitment. The default sandbox of 2 vCPUs and 4 GiB runs about $0.17 an hour.

Vendor details

Canonical URL

https://e2b.dev

Category

Agent infrastructure

Funding status

E2B is independent. Its contracting entity is FoundryLabs, Inc., a Delaware corporation, per E2B's security page.

Company status

independent

Use cases & customers

Target customers

AI developersinfrastructure teams

Deployment options

SaaSAPI

Integrations

E2B offers Python and JavaScript/TypeScript SDKs, a CLI, a REST API with an OpenAPI 3.1 specification, custom templates, and an MCP gateway inside sandboxes exposing 200+ tools from the Docker MCP Catalog. Setup guides cover Claude Code, Codex, Cursor, Devin, the OpenAI Agents SDK, the Vercel AI SDK, LangChain, CrewAI, Mastra, Google ADK, Letta and NVIDIA NeMo Gym.

In practice

Your agent writes Python and you can't safely run it on your own servers. E2B runs the model-generated code in an isolated Firecracker microVM and returns the results without touching your infrastructure.

Your coding agent's tasks run for hours across several sessions. You pause the E2B sandbox between steps and resume it later with its files, processes and variables exactly as they were.

Your agent needs to click through a real desktop app, not just call APIs. E2B Desktop gives it a graphical Linux desktop to see and control, with a live stream so your team can watch.

Agentic Index coverage score

8.0 / 14 capabilities · 57%

Integrations & Tool Calling Full

An agent in a sandbox reaches other systems through a built in MCP gateway that runs inside the sandbox and exposes more than 200 tools from the Docker MCP Catalog (Airtable, GitHub, Browserbase, Exa and others) or custom MCP servers through one interface. Credentials are passed as secrets that resolve at egress instead of living in the sandbox.

Sourcedocs.e2b.dev/mcp-gatewayread 2026-11-03

Workflow Orchestration Not documented

There is no workflow logic in E2B itself. The customer brings its own orchestration framework, and E2B provides the machine an agent's steps run on (commands, background processes, code contexts), not a runtime that sequences, branches, retries or routes those steps. Forking a sandbox copies its state, which is compute, not workflow logic.

Sourcee2b.dev/llms.txtread 2026-11-03

Knowledge Grounding & RAG Not documented

There is no retrieval structure over the customer's content, since E2B runs the agent's code. Files uploaded to a sandbox or volume are storage the agent's code can read, not an index a query returns, and the MCP gateway's tools reach outside knowledge sources owned by others.

Sourcee2b.dev/llms.txtread 2026-11-03

Human Oversight & Guardrails Not documented

There is no approval step, consent checkpoint or escalation to a person for work inside an E2B sandbox. Egress control (allow and deny lists for each sandbox, a proxy the customer runs that fails closed, and access tokens on public URLs) limits what an agent's code can reach, but that is isolation the developer configures, not a point where a person reviews the agent's action.

Sourcee2b.dev/enterpriseread 2026-11-03

Security, Identity & Governance Partial

E2B holds SOC 2 Type II, with the report under NDA in its trust center at trust.e2b.dev, and signs HIPAA Business Associate Agreements on Enterprise plans. Its controls protect the sandbox. Every sandbox is its own Firecracker microVM with its own kernel, egress can be allowed or denied for each sandbox, secrets are injected at the egress proxy so no sandbox holds them, and public sandbox URLs can require an access token. Who inside a customer's organization can do what has no published control yet, since E2B lists single sign on, SCIM and role based access as planned.

Sourcee2b.dev/securityread 2026-11-03

Observability & Auditability Partial

The record covers the sandbox, not the agent. Every lifecycle event is available through an events API and delivered as a signed webhook, sandbox metrics report CPU and memory use, template builds keep logs, and on Enterprise OpenTelemetry metrics and logs export to the customer's OTLP endpoint. Prompts, tool calls, retrieved knowledge and outputs cannot be inspected step by step in E2B, since the agent's reasoning runs outside the sandbox, and there is no audit log of user actions apart from the runtime.

Sourcee2b.dev/enterpriseread 2026-11-03

Memory & State Persistence Partial

An agent's working state carries across sessions. A paused sandbox resumes exactly as it was, with filesystem and memory, running processes and loaded variables, and is kept until it is killed. Snapshots and forks copy that state, volumes, in private beta, keep files across sandboxes, and code contexts keep interpreter variables between executions, which the agent's code reads to continue its task. This is machine state the developer manages, with no memory layer of stated types or scope that can be reviewed, edited or deleted as memory.

Sourcedocs.e2b.dev/sandbox/persistenceread 2026-11-03

Deployment & Data Residency Full

Three deployment modes share the same SDK, CLI and API. E2B Cloud defaults to Google Cloud us-west1, and AWS us-west-2 and us-east-1 and Google Cloud europe-west1 and asia-southeast1 are available on request on every plan. With BYOC on AWS, Google Cloud or Azure on Enterprise, the data plane runs in the customer's own cloud account. E2B Embed packages the Apache-2.0 runtime for a single node self hosted install, and a private cloud option is in development.

Sourcedocs.e2b.dev/faq/egress-ip-rangesread 2026-11-03

Prebuilt Agents, Templates & Packs Partial

Starting points ship with the platform, including sandbox templates for Claude Code, a desktop, Docker and web app stacks, a cookbook of examples ready to run, setup guides for more than thirty agents and frameworks, and open source reference apps, Surf, a computer use agent, and Fragments, a builder that turns a prompt into an app. These are environments and examples a developer builds from, not a browsable catalog of agents a customer adopts.

Sourcedocs.e2b.dev/llms.txtread 2026-11-03

Triggers & Channel Coverage Full

A sandbox can start without the customer's code calling it. With auto resume set, a paused sandbox resumes when activity arrives, so an agent served from a sandbox starts on an inbound request, and E2B's guides deploy agent gateways this way, for example OpenClaw answering Telegram. Sandbox lifecycle events are also pushed to the customer's webhook, signed. There is no scheduler.

Sourcedocs.e2b.dev/sandbox/auto-resumeread 2026-11-03

Model Flexibility & Routing Full

Compute is what E2B provides for agents, with the customer bringing its own model and orchestration framework. Sandboxes connect to any LLM and to agents and frameworks such as Claude Code, Codex, the OpenAI Agents SDK, the Vercel AI SDK, LangChain, CrewAI, Mastra and Google ADK. E2B imposes no model, so model choice stays with the customer.

Sourcee2b.dev/llms.txtread 2026-11-03

APIs, SDKs & MCP Extensibility Full

Outside systems can call E2B through Python and JavaScript/TypeScript SDKs, a CLI, a REST API described by a published OpenAPI 3.1 specification, and custom sandbox templates the customer builds, tags and versions. A public MCP server serves E2B's documentation to agents.

Sourcee2b.dev/llms.txtread 2026-11-03

Testing, Debugging & Optimization Not documented

There are no fixtures, scoring, quality gates or comparison of agent runs. E2B is where evaluations and reinforcement learning run, not how they are scored. It lists reinforcement learning among its workloads and runs NVIDIA NeMo Gym environments in sandboxes, but the datasets, reward functions and scoring belong to the customer's framework.

Sourcee2b.dev/llms.txtread 2026-11-03

Browser & Computer Use Full

Agents control real desktops hosted by E2B. E2B Desktop sandboxes are Ubuntu machines with an XFCE desktop and preinstalled applications, and the Desktop SDK gives the agent screenshots, mouse, keyboard and scroll, with a live VNC stream so a person can watch. A cloud browser can also run in a sandbox, and Surf is E2B's open source computer use agent built on it.

Sourcedocs.e2b.dev/use-cases/computer-useread 2026-11-03

The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded

Product updates

·MCP / tool calling / APIVerified

The E2B JavaScript SDK release e2b@2.64.0 lets templates be built with a max vCPU count so each sandbox can pick its own CPU count at create time. The API client now accepts an OAuth access token in an Authorization header with an X-Team-ID header in place of an API key, and commands.run takes a shell option to run commands in a chosen shell. It also adds Template.list() and Template.delete() to the SDK, with a breaking change to the CLI template list JSON output.

Bears on: MCP / tool calling / API

View source
·Security / enterpriseVerified

Secrets, now generally available in E2B, keep credentials outside the sandbox: a team stores a credential from its backend, references it by name in a sandbox network rule, and E2B injects the value into the configured HTTPS request headers after the request leaves the sandbox. Values are encrypted at rest, the management API returns only metadata, and a rotated secret reaches running and resumed sandboxes without restarts.

Bears on: MCP / tool calling / API

View source
·MCP / tool calling / APIVerified

E2B deprecated E2B_ACCESS_TOKEN authentication in favor of E2B_API_KEY. This is a breaking change for existing integrations: legacy access tokens stop working on August 1, 2026, and all SDK and API calls must migrate to API-key auth before then.

Bears on: MCP / tool calling / API

View source
View all 4 E2B updates →Tracked since Jun 2026 · Verified from public vendor sources

Pricing

Hobby is free with a one time $100 credit, and Pro is $150 a month plus per second usage.

usage

Free tier

Included quota

Hobby includes a one time $100 usage credit, sessions of up to 1 hour, 20 concurrent sandboxes and 10 GiB of storage. Pro includes sessions of up to 24 hours, 100 concurrent sandboxes (600 or 1,100 with add ons) and 20 GiB of storage, with sandboxes from 1 to 8 vCPU and 1 to 8 GiB of memory. Compute costs $0.000014 per vCPU second and $0.0000045 per GiB second on every plan, and the default sandbox is 2 vCPU and 4 GiB. Enterprise includes 500 concurrent sandboxes.

What is public

E2B publishes its plans, per second compute rates and concurrency add-ons, with custom Enterprise (BYOC on AWS or GCP) above a monthly minimum. The core runtime is open source under Apache 2.0.

Billing mechanics

E2B bills per second for running sandboxes (CPU and RAM metered separately), layered on a flat plan fee. Billing stops immediately on pause, kill, or timeout, and is postpaid monthly.

Cost watchouts

The $150 Pro fee is a fixed floor paid before any compute. It buys limits on session length and concurrency, not credits. Higher concurrency is a paid add on, and Enterprise starts at a $2,000 monthly commitment. Paused sandboxes stop compute billing, and storage is included.

Variable cost rationale

Per second metering means cost scales directly with sandbox count and lifetime; long lived or highly concurrent agent fleets can dwarf the subscription fee.

Additional watchouts

Budget the Pro floor against actual utilization, and size the default sandbox: at 2 vCPU and 4 GiB it runs about $0.17 an hour. No GPU sandboxes are documented.

Sales call required

Mixed (some tiers require a call)

Free / trial

Free Hobby tier, no card ($100 one time credit, 1 hour max sessions)

Lowest paid plan

Pro at $150 a month plus per second compute usage

Commercial notes

E2B has raised $34.5M+ including a $21M Series A led by Insight Partners (Jul 2025). Customers include Perplexity and Hugging Face, and E2B claims 88% of the Fortune 100 have signed up. Each sandbox is isolated in a Firecracker microVM. A startup program bundles Pro plus $20K credits.

Key ambiguities

Enterprise pricing is custom above a $2,000 monthly commitment that includes 500 concurrent sandboxes.

Missing data

Enterprise pricing is custom; the 1,100-sandbox add-on price is stated two ways across the pricing page and the billing docs.

Agentic Index verified 2026-11-03

Alternatives to E2B

The closest documented capability profiles to E2B among agent infrastructure platforms tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.

Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded

Contact us

Found a vendor we missed? Have feedback on the index? We'd love to hear from you.