E2B

What it does

E2B gives each agent session an isolated Linux machine that boots from a snapshot and works with any model or agent framework. The public GitHub organization describes the stack as open at the core, covering the Firecracker runtime, the control plane, the in-VM agent, the SDKs, and the dashboard. The main SDK repository frames the same idea more narrowly: open-source infrastructure for running AI-generated code in secure isolated sandboxes in the cloud, controlled from JavaScript or Python.

Day to day use starts with a sandbox. The SDK can create a sandbox, run shell commands, work with files, expose ports, pause and resume sessions, and use templates that define a base image, files, environment, and a start command captured in a snapshot. A separate Code Interpreter SDK adds stateful runCode execution on top of the same sandbox model for data work and iterative code loops. E2B also documents an MCP gateway that runs inside sandboxes and connects to tools from the Docker MCP Catalog or custom MCP servers.

Deployment is flexible for a hosted sandbox product. Teams can run on E2B Cloud, use the self-hosting Embed path on their own machine with Docker Compose, or use the broader runtime deployment described for AWS, Google Cloud, Azure, and general Linux in the SDK README. Pricing is usage based with a free Hobby tier, a paid Pro tier, and custom Enterprise terms that add BYOC deployment and larger concurrency.

Verified capabilities

Quick start

Run a first E2B sandbox from Python

Install the Python SDK, set your E2B API key, create a sandbox, and run a shell command inside it. This follows the SDK README quickstart, with a placeholder key.

pip install e2b

from e2b import Sandbox

with Sandbox.create() as sandbox:
    result = sandbox.commands.run('echo "Hello from E2B!"')
    print(result.stdout)

Source: https://github.com/e2b-dev/E2B. Examples use placeholders only. Never paste a real key into a profile, config file you share, or a ticket.

MCP support: E2B documents an MCP gateway that runs inside sandboxes and gives access to tools from the Docker MCP Catalog or custom MCP servers. A separate E2B MCP server was also found in search results, but the gateway is the verified documented path in this run.

Works with

Only sourced support is listed. A missing framework means AgentsUse has not verified it yet, not that it cannot work.

Health and maintenance

Pricing and license

Free Hobby tier to start, with paid Pro and custom Enterprise upgrades. Sandboxes are billed by running time, with separate usage costs and higher session and concurrency limits on paid plans. See the pricing page for current rates and the workload estimator.

Official pricing or docs →

Limitations and safety

• Hosted session length and concurrency are plan gated on the pricing page, with longer sessions and custom sizes on paid tiers.
• Self-hosting the full runtime is an infrastructure project in Go with Firecracker and Terraform or Embed pieces, not a simple local library install.
• E2B is execution infrastructure first. Prebuilt business app actions and end-user OAuth for SaaS tools are not its core surface.

Alternatives to E2B

Related tools

Common questions