OpenViSTAI · Agents · Blockchain · Crypto
Menu
Agent Infrastructure

E2B Runtime

E2B Runtime is an open-source Go backend that provisions and manages isolated Linux sandboxes for AI-agent code using Firecracker microVMs, snapshots and a control-plane API.

Independent OpenViST project profile, based on linked sources.

E2B Runtime — OpenViST project profile in Agent Infrastructure.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use E2B Runtime when your application needs the infrastructure for isolated agent-code execution and you need snapshot-based sandbox lifecycle management, or when evaluating the backend behind E2B Cloud.

Who it is for

  • Teams building AI-agent applications that need isolated environments to execute generated or otherwise untrusted code.
  • Infrastructure engineers evaluating or operating the runtime behind E2B Cloud, dedicated deployments or a single-host Embed installation.

Documented uses

  • Run agent-requested code in an isolated Linux microVM.
  • Pause and resume sandboxes from snapshots.
  • Build reusable sandbox templates and fork a running sandbox from a checkpoint.
  • Operate a self-hosted, single-machine runtime using E2B Embed.
Before you choose

Requirements & limits

The repository documents E2B Cloud access using an API key and JavaScript or Python SDK. E2B Embed is described for a Linux host with KVM. The runtime is open source under Apache-2.0.

  • The deployment model ranges from E2B Cloud to dedicated deployments and a single-machine Embed package.
  • Embed requires Linux and KVM and is designed for one machine.
  • Sandbox execution interfaces include process, PTY, filesystem, file-watching and port-forwarding operations exposed by envd.
  • The runtime separates API control-plane decisions from per-node orchestration and sandbox traffic handling.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Set up E2B Embed on one Linux machine

Start the documented single-host E2B Embed stack.

Before you start

  • A Linux host with KVM.
  • Docker Compose.

Steps

  1. Create an e2b directory and change into it.

  2. Download compose.yaml and .env from the runtime repository's embed/compose directory.

  3. Run docker compose up -d --wait.

Expected outcome

The Embed stack is started on the single Linux host.

Guide limitations

  • Embed is designed for one machine.
  • The README describes this setup but does not provide application-specific sandbox execution steps in the available text.
Evidence and transparency

Sources & review

Source record details
Source availability
Active
Sources checked
10 October 2026
Original website title
e2b-dev/runtime · Official homepage title · retained in its source language