E2B

An agent in a sandbox gets actionable reach into 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, with credentials passed as secrets that resolve at egress rather than living in the sandbox.

Sourcedocs.e2b.dev/mcp-gatewayread 2026-09-22

No workflow logic is documented as an E2B mechanism: E2B states that the customer brings its own orchestration framework, and it 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-09-22

E2B does not keep a retrieval structure over the customer's content; it 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-09-22

No approval step, consent checkpoint or escalation to a person is documented for work inside an E2B sandbox. Egress control (allow and deny lists per sandbox, a customer-run proxy that fails closed, and access tokens on public URLs) restricts 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-09-22

SOC 2 Type II compliance is stated, with the report under NDA and a current bridge letter in the Trust Center at trust.e2b.dev, a penetration test report and DPA on request, and HIPAA Business Associate Agreements on Enterprise plans.

The customer-facing controls are documented beside it: every sandbox is its own Firecracker microVM with its own kernel, egress can be allowed or denied per sandbox by IP, CIDR or domain, secrets resolve at egress so no response, log or sandbox holds them, and public sandbox URLs can require a per-sandbox access token. No SSO for the console is documented, and workload identity is in private beta.

Sourcee2b.dev/securityread 2026-09-22

E2B records the sandbox rather than 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 no audit log of user actions separate from runtime is documented.

Sourcee2b.dev/enterpriseread 2026-09-22

An agent's working state carries across sessions: a paused sandbox resumes exactly as it was, filesystem and memory, running processes and loaded variables included, and is kept indefinitely until killed; snapshots and forks copy that state, volumes persist 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-09-22

Three deployment modes share the same SDK, CLI and API: E2B Cloud on Google Cloud in US, EU and APAC regions (regions by plan listed in its FAQ); BYOC on AWS or Google Cloud, where the data plane runs in the customer's VPC and sandbox traffic, template sources, snapshots and logs never reach E2B Cloud; and self-hosting, since the runtime, control plane and Firecracker layer are Apache-2.0 with Terraform deployment. Azure is not yet supported.

Sourcee2b.dev/enterpriseread 2026-09-22

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

Sourcedocs.e2b.dev/llms.txtread 2026-09-22

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. No scheduler is documented.

Sourcedocs.e2b.dev/sandbox/auto-resumeread 2026-09-22

Compute is what E2B says it provides for agents, with the customer bringing its own model and orchestration framework; its docs connect sandboxes 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-09-22

E2B is callable from outside 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 docs MCP server serves its documentation to agents.

Sourcee2b.dev/llms.txtread 2026-09-22

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

Sourcee2b.dev/llms.txtread 2026-09-22

E2B hosts real desktops an agent controls: 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; the docs also cover running a cloud browser in a sandbox, and Surf is E2B's open source computer-use agent built on it.

Sourcedocs.e2b.dev/use-cases/computer-useread 2026-09-22