Self-host on E2B sandboxes
E2B runs each Session inside a hosted Firecracker microVM. It is the simplest hosted backend for the Node self-host: one API key, no infrastructure to run, and provider memory snapshots for suspend/resume.
Prerequisites
Section titled “Prerequisites”E2B_API_KEY= # requiredSANDBOX_IMAGE= # E2B template reference used as the Environment imageFor E2B-compatible endpoints, the connection details stay in the same environment map:
E2B_API_URL= # or E2B_SANDBOX_URL / E2B_DOMAIN, depending on deploymentOMA_E2B_TEMPLATE= # explicit template overrideConfiguration
Section titled “Configuration”On the standalone Node server, select the adapter directly:
SANDBOX_PROVIDER=e2bE2B_API_KEY=...SANDBOX_IMAGE=...To embed the driver in the Runtime Host composition instead, use
createE2BManagedRuntime / createE2BManagedRuntimeDriver from
@open-managed-agents/managed-runtime-e2b:
const driver = createE2BManagedRuntimeDriver({ leaseTtlMs: 90_000, environment: { E2B_API_KEY: process.env.E2B_API_KEY!, SANDBOX_IMAGE: process.env.SANDBOX_IMAGE!, },});The factory also accepts a per-scope environment function, an explicit
outputStore (null disables the S3 default), credentialEgress,
sessionInputs, runtimeEnvironment, context, and a test seam
provider.
Capabilities
Section titled “Capabilities”| Harness lanes | ama_worker, openma_supervised |
| suspendResume | supported (provider memory snapshot) |
| Workspace | retained_runtime + checkpoint_restore, durable |
| Outputs | final_collect, durable (S3 store when configured) |
| Process checkpoints | none |
| Credential egress | unsupported/snapshot by default |