E2B sells isolated sandboxes for agents: a Linux VM created on demand from a template, driven through Python and JavaScript SDKs. It is infrastructure for a product rather than a finished assistant.

Templates define what a sandbox starts with, including images built from Docker images, and the code-interpreter and desktop products run inside the sandbox.

At a glance

Who it is forDevelopers integrating code execution, data analysis or computer use into an agent product.
IsolationFirecracker microVM with its own kernel, not a container. The default template user is user, not root; root can be set in a template. Docker is documented, but kernel features are not unlimited: the sandbox kernel does not ship xt_owner.
SizesSized by vCPU and RAM: up to 8 vCPU, 8 GiB memory on Hobby and Pro, and 10 or 20 GiB of included disk. No GPU on any plan. Regions: US (GCP), US West (AWS), EU and APAC.
A personal agent hereAbout $270.89 a month for one always-on 2 vCPU / 4 GiB machine (2 vCPU / 4 GiB / 20 GiB), before the AI model. The catch: Sessions end after 24 hours, so an always-on machine has to be restarted by your own code. Change the numbers
Recommended in

Fits well, fits badly

Our reading of the sourced material on this page, not a provider claim.

Fits well

  • A microVM with its own kernel, Docker, snapshots that keep memory, and up to 20 forks from a running sandbox.
  • An agent that needs a real API and SDKs, plus templates built from any Docker image.
  • A team that needs a SOC 2 report and a HIPAA path without an enterprise contract.

Fits badly

  • A long-running agent: the default timeout kills the sandbox after five minutes and commands do not reset it.
  • Memory above 8 GiB, or any GPU workload.
  • A client-facing link that must be private: public URLs have no authentication by default.

Compare: alternatives to E2B · E2B vs Daytona · E2B vs Modal · E2B vs Vercel Sandbox · E2B vs Cloudflare Sandbox

How it bills

ModelPer-second usage against a credit balance; Pro adds a monthly plan fee.
Meter$0.000014 per vCPU-second and $0.0000045 per GiB-second of allocated resources while running. Paused and killed sandboxes are not billed.
While stoppedNothing for compute. Volumes and snapshots are separate objects with their own storage.
Plan feeHobby has no fee; Pro is $150 a month plus usage; Enterprise has a $3,000 monthly minimum.
MinimumNo published per-sandbox minimum. Hobby starts with a one-time $100 credit and no card.

How E2B lets you try before paying is on Trials and free tiers.

Where it stands out

  • Snapshots capture memory and filesystem, and the source keeps running.
  • Fork up to 20 sandboxes from a running VM, with a documented pause.
  • Templates can start from any Docker image.
  • Secrets can be injected outside the VM by an egress proxy.
  • SOC 2 Type II and a HIPAA BAA path.

Using it without writing code

DashboardA console exists for support and API keys, but the documented path is SDKs, a CLI and API keys.
Without codeNo documented no-code path. Examples are SDK calls, terminals and templates; the desktop SDK still needs code to drive it.
SignupNo credit card to start, and a one-time $100 credit. When a workspace without a payment method runs out, every project in it is blocked shortly afterwards.
Docs and supportExtensive docs with per-page Markdown. Support is through the console. SOC 2 Type II is reported, and a HIPAA BAA can be requested.

Capability checklist

Every capability the guide checks, with the catch where E2B's version falls short. Compare all providers

The company

From the profile's company section: the legal entity, who funds it, and what a buyer can check before signing.

Legal entity

FoundryLabs, Inc., a Delaware corporation.

“E2B's contracting entity is FoundryLabs, Inc., a Delaware corporation.” docs.e2b.dev docs-confirmed

Founded

2023, by Vasek Mlejnsky (CEO) and Tomas Valenta (CTO).

“E2B was founded in 2023 by Vasek Mlejnsky and Tomas Valenta.” e2b.dev docs-confirmed

Funding

$21M Series A in July 2025, led by Insight Partners; $32M total at that announcement.

“This Brings Our Total Funding to $32M” e2b.dev docs-confirmed

Headcount

About 25, a third-party estimate from June 2026. No company-confirmed figure is published.

“Employees | ~25” rywalker.com third-party

Status and SLA

99.78% for US-West-1 over July–October 2026. Uptime and support terms are set in the enterprise agreement.

“99.78% uptime” status.e2b.dev docs-confirmed

Certification

SOC 2 Type II report and a HIPAA BAA path, both by request through the Trust Center.

“E2B has a SOC 2 Type II report.” docs.e2b.dev docs-confirmed

Caveats and contradictions

Shown as the research found them. A contradiction means the provider's own pages disagree; an open question means the answer is not published.

  1. 01

    The default timeout destroys the sandbox Open question

    Every sandbox has a timeout defaulting to five minutes, and onTimeout: 'kill' is the default. Pausing instead is opt-in.

  2. 02

    The default sandbox size is stated two ways Contradiction

    The pricing page says the default is 2 vCPU / 4 GiB; the billing docs say 2 vCPU / 512 MiB. Both are current provider statements.

    “The default sandbox has 2 vCPUs and 4 GiB of RAM.”
    E2Bpricing-page
    “Start with default resources (2 vCPU, 512 MiB RAM)”
    E2Bdocs-confirmed
  3. 03

    Volumes are in private beta Open question

    Volumes persist across sandboxes but file locking can hang, metadata caching is disabled and snapshots are not supported.

  4. 04

    No static egress IP on any plan Open question

    There are no dedicated or static egress addresses, including Enterprise; a customer-operated proxy is the documented workaround.

  5. 05

    Public URLs have no authentication by default Open question

    A sandbox's public URLs are reachable by anyone who knows them.

Sources

The three shared workloads

List-price illustrations from the calculator, not quotes. Prices checked 29 October 2026.

A · 1,000 short tasks

$27.60

2 vCPU / 4 GiB / 10 GiB (plan: Hobby)

  • CPU166.67 h × 2 vCPU × $0.0504$16.80
  • Memory166.67 h × 4 GiB × $0.0162$10.80
  • Hobby starts with a one-time $100 credit, not subtracted here.
  • Pausing keeps memory and files at no charge; volumes and snapshots are separate.
  • Sandbox storage is included at no extra cost, up to 10 GiB on Hobby and 20 GiB on Pro.

B · One always-on box

$241.78, with a catch

4 vCPU / 8 GiB / 50 GiB (plan: Hobby)

  • CPU730 h × 4 vCPU × $0.0504$147.17
  • Memory730 h × 8 GiB × $0.0162$94.61
  • Hobby starts with a one-time $100 credit, not subtracted here.
  • Pausing keeps memory and files at no charge; volumes and snapshots are separate.
  • Sandbox storage is included at no extra cost, up to 10 GiB on Hobby and 20 GiB on Pro.

It cannot run this exactly as described: 50 GiB of disk is over the 10 GiB limit. Sessions end after 1 hour, so an always-on machine has to be restarted by your own code.

C · Three hours a day

$164.90

2 vCPU / 4 GiB / 20 GiB (plan: Pro)

  • CPU90 h × 2 vCPU × $0.0504$9.07
  • Memory90 h × 4 GiB × $0.0162$5.83
  • Pro: $150.00 plan, $14.90 over.
  • Pausing keeps memory and files at no charge; volumes and snapshots are separate.
  • Sandbox storage is included at no extra cost, up to 10 GiB on Hobby and 20 GiB on Pro.