Today we're releasing E2B Embed, a way to package E2B with your product and run its sandboxes inside your customer's environment.
E2B Embed brings the E2B Runtime and its dashboard to a single machine you control. It sits next to E2B Cloud and E2B Bring Your Own Cloud.
Why we built it
Agent companies need to serve customers whose data has to stay inside their own environment. That is often a requirement for government organizations and companies in regulated industries such as finance and healthcare.
We built E2B Embed so you can include E2B in the software you deliver to those customers. The sandbox stack runs on one machine inside their environment, and you operate it yourself.
What you get
E2B Embed runs the open-source E2B Runtime that powers E2B sandboxes. The databases run on your machine, and the templates you build and your sandbox logs live on its disk.
- Firecracker sandboxes. Every sandbox is a Firecracker microVM, using the same VM isolation as E2B Cloud.
- The same SDKs. Use the Python or JavaScript SDK with your install's team API key and SDK URLs.
- Your own templates. Build custom templates with
Template.buildand start sandboxes from them. Builds run inside a Firecracker VM on the machine. - The dashboard. Browse sandboxes and templates, with a terminal and a file browser for each sandbox. The dashboard is included with every installation option.
- OpenTelemetry export. One setting sends the E2B services' metrics, traces and logs to a collector of your choice.
E2B Embed does not include secrets, volumes, workload identity or bring-your-own proxy.
Getting started
E2B Embed is available in the E2B Runtime repository. Choose the setup that fits your infrastructure. All four options run the same stack on one machine.
| Setup | What you need | Install command |
|---|---|---|
| Docker Compose | A Linux host with KVM | docker compose up -d --wait |
| Terraform on GCP | A GCP project and credentials | terraform init && terraform apply |
| Terraform on AWS | An AWS account and credentials | terraform init && terraform apply |
| Kubernetes | A cluster with a prepared KVM node | kubectl apply -k |
Docker Compose needs a dedicated Linux host with KVM and Docker. Once the host meets the requirements, the install is two files and one command:
mkdir e2b && cd e2b
curl -fsSL --remote-name-all "https://raw.githubusercontent.com/e2b-dev/runtime/main/embed/compose/{compose.yaml,.env}"
docker compose up -d --waitThe first run checks and prepares the host, downloads the Firecracker artifacts, pulls the pinned images, migrates the databases and builds the base template. The command succeeds once that template is ready. Run docker compose logs ready to see your team API key, SDK URLs and dashboard URL.
Embed serves plain HTTP inside your network. Follow the networking guide to configure access to the API and dashboard and keep internal service ports private.
E2B Embed is open source under Apache-2.0, like the E2B Runtime. You do not need an E2B account or a license key. We welcome contributions.
Embed is a single-machine product. If you need to scale across machines or want E2B to operate the deployment in your cloud account, see E2B Bring Your Own Cloud.
Why this matters
An agent that can run code and work with files needs clear limits on what it can access. Companies cannot build a business on the assumption that an agent will always behave correctly.
E2B gives agents isolated VMs to work in. Isolation is one part of safe deployment, alongside the network and access controls around it. Embed lets you bring those sandboxes into the environment your customer requires.
We're bullish on agents. We want more companies to put them to work, including those that need to run them on infrastructure they control.
Install E2B Embed and create your first sandbox.