E2B Embed runs E2B's Firecracker sandboxes on a single machine you control

E2B released Embed, an Apache-2.0 package that runs the E2B Runtime and dashboard on one machine inside a customer's environment.

E2B has released E2B Embed, which packages the E2B Runtime and its dashboard to run on one machine inside a customer's environment. If you build agent tools for finance, healthcare or government clients whose data can't leave their network, this gives you E2B sandboxes you can ship and operate yourself.

According to E2B, each sandbox is a Firecracker microVM with the same isolation as E2B Cloud. You keep the Python and JavaScript SDKs, pointed at your install's API key and SDK URLs, and get custom templates, the dashboard and OpenTelemetry export. Databases, templates and logs stay on the machine. Embed does not include secrets, volumes, workload identity or bring-your-own proxy. E2B says it is Apache-2.0 and needs no account or license key. It installs via Docker Compose, Terraform on GCP or AWS, or Kubernetes. Compose requires a dedicated Linux host with KVM and Docker.

The limits are real. Embed is single-machine. E2B points multi-machine needs to Bring Your Own Cloud. It serves plain HTTP, so you have to configure networking yourself. Minimum hardware, concurrency limits, failover and support terms aren't documented. One early user reports that a snapshot marked successful crashes Firecracker on every restore, so test pause and resume before relying on it.

There are alternatives. The older Terraform self-host path lists only AWS and GCP as supported. NVIDIA OpenShell uses kernel-level controls with policy enforcement and credential brokering. AgentENV exposes an E2B-compatible API on Firecracker, needs kernel 6.8+, and doesn't encrypt traffic.

Sources