Home / AI agent sandboxes / E2B / Pricing
E2B pricing
In short (2026-11-14): $0.0504 per vCPU-hour, $0.0162 per GiB-hour of memory, plans from $150.00 a month. Free tier: Hobby plan: $0/month with a one-time $100 usage credit, no credit card required; 1-hour sessions and 10 concurrent sandboxes. Source: official pricing page. Prices checked 2026-11-15.
Usage rates
- vCPU
- $0.0504 per vCPU-hour
- Memory
- $0.0162 per GiB-hour
- Storage
- No separate monthly rate published
- Billing
- per second. Wall-clock while the sandbox is running, for allocated vCPU and RAM; compute billing stops when the sandbox is paused, killed or times out.
Plans
| Plan | Per month | Included credit | Limits |
|---|---|---|---|
| Hobby | $0.00 | $0.00 | $100 one-time usage credit (not monthly). Sessions up to 1 hour of continuous runtime, 10 concurrent sandboxes, up to 8 vCPU and 8 GiB RAM, 10 GiB disk, 1 sandbox created per second. |
| Pro | $150.00 | $0.00 | No usage credit included. Sessions up to 24 hours of continuous runtime, 100 concurrent sandboxes (600 with a +$500/month add-on, 1,100 with a +$1,000/month add-on), 8+ vCPU and 8+ GiB RAM, 20+ GiB disk, 5 sandboxes created per second. |
What it costs in practice
| Workload | Usage | Cheapest plan | Total per month |
|---|---|---|---|
| Hobby agent: 1 vCPU, 1 GiB, 20 hours a month | $1.33 | Hobby | $1.33 |
| One dev agent: 2 vCPU, 4 GiB, 8 h a day for 22 days | $29.15 | Hobby | $29.15 |
| Team: 10 sandboxes of 2 vCPU, 4 GiB, 8 h a day for 22 days | $291.46 | Hobby | $291.46 |
| Always on: 4 vCPU, 8 GiB, 730 hours a month | $241.78 | Hobby | $241.78 |
CPU busy 30% (50% always on), which matters only where CPU is billed by active time. Storage, network and GPU are not included. Try your own numbers in the cost calculator.
Billing details that change the bill
- Rates are the same on Hobby and Pro: $0.000014 per vCPU-second ($0.0504/vCPU-hour) and $0.0000045 per GiB-second of RAM ($0.0162/GiB-hour).
- Default sandbox size on the pricing page is 2 vCPU and 4 GiB RAM ($0.000028/s + $0.000018/s = $0.1656/hour); the billing docs' cost tips mention a default of 2 vCPU and 512 MiB RAM, so the actual default RAM depends on the template.
- Disk is included at no charge (10 GiB on Hobby, 20 GiB on Pro); no separate storage or egress rate is published on the pricing page.
- Paused sandboxes are kept indefinitely with no compute charge; the pages checked do not state any storage charge for paused sandboxes.
- Pro concurrency add-ons: 600 concurrent for +$500/month, 1,100 concurrent for +$1,000/month. Enterprise starts at a $2,000/month commit with 500 concurrent sandboxes included.
- Usage is invoiced at the start of each month for the previous month; projects are blocked when credits run out and no payment method is on file.
Price history
List price per month over timeNo change since 2026-11-13
No price change found since we started tracking on 2026-11-13. We check every pricing page daily.
Cheaper or better-fit E2B alternatives →
Sources
- https://e2b.dev/pricing, checked 2026-11-14:
We charge per second of a running sandbox.
- https://e2b.dev/pricing, checked 2026-11-14:
$0.000014/s
- https://e2b.dev/pricing, checked 2026-11-14:
$0.0000045/s
- https://e2b.dev/pricing, checked 2026-11-14:
$100 one-time usage credit
- https://e2b.dev/pricing, checked 2026-11-14:
100 concurrent sandboxes, expandable to 1,100
- https://e2b.dev/pricing, checked 2026-11-14:
Enterprise starts at a $2,000/mo commit, 500 concurrent included.
- https://e2b.dev/docs/billing, checked 2026-11-14:
Upgrading to the Pro tier does not grant additional credits.
- https://e2b.dev/docs/billing, checked 2026-11-14:
Max continuous runtime is the time a sandbox can run without being paused
- https://e2b.dev/docs/billing, checked 2026-11-14:
Once a sandbox is paused, killed or times out, compute billing stops immediately.
- https://e2b.dev/docs/sandbox/persistence, checked 2026-11-14:
A paused sandbox is kept indefinitely.
- https://e2b.dev/docs/sandbox/internet-access, checked 2026-11-14:
You can specify IP addresses, CIDR blocks, or domain names that the sandbox is allowed to use
- https://e2b.dev/docs/faq, checked 2026-11-14:
No. E2B sandboxes are CPU-only, sized by vCPU and RAM only, with no GPU option
- https://github.com/e2b-dev/infra, checked 2026-11-14:
One Firecracker microVM per sandbox, in its own cgroup and network namespace