Account, billing & limits
How do I calculate the price of a sandbox?
E2B bills per second, only while a sandbox is running, based on the vCPU and RAM allocated to it. Paused and killed sandboxes are not billed. Read moreHow do I increase my concurrency limit?
Raise your concurrent sandbox limit with self-serve add-ons in the console billing tab, or contact sales for higher limits on the Enterprise plan. Read moreHow long does a sandbox live?
A sandbox is not session-scoped. Continuous runtime is capped by plan (1 hour Hobby, 24 hours Pro, custom Enterprise) and resets on pause and resume, while a paused sandbox is kept indefinitely with no time-to-live. Read moreDo paused sandboxes count toward the concurrency limit?
No. Only running sandboxes count toward the concurrency limit and only running sandboxes are billed. There is no time limit on how long a sandbox can stay paused. Read moreDoes E2B support GPUs?
No. E2B sandboxes are CPU-only, sized by vCPU and RAM only, with no GPU option in the SDKs, CLI, API, or a template definition. BYOC does not change this. Read moreTemplates & builds
What limits apply to my template builds?
Two kinds of limit apply: plan limits like concurrent builds can be raised by upgrading or contacting support, while build timeouts are fixed for everyone and require restructuring the build. Read moreIs there a limit on how many templates I can create?
No. There is no limit on the total number of templates. The only template limit is on concurrent builds: 20 on Hobby and Pro, custom on Enterprise. Read moreCan I make a template public so other projects can use it?
Yes. Publish a template from the console Templates tab or with the CLI, and any project can then create sandboxes from it by its full project-slug/template-name. Read moreWhy does pip install fail when building a template?
Large packages like PyTorch with CUDA exhaust the build environment: pip caches wheels in memory (MemoryError) and downloads them to the RAM-backed /tmp capped at ~3.9 GB (“No space left on device”). Set TMPDIR to a disk-backed path with --no-cache-dir, or install CPU-only builds. Read more
Why does my template build fail with a Docker push authentication error?
Docker sends no credentials to the build registry. Add E2B’s local registry proxy (host.docker.internal:49984, or localhost:49984 on Linux) to Docker’s insecure-registries and restart Docker. Read more
Storage & volumes
What are the limitations of the Volumes beta?
File locking can hang, file metadata caching is disabled, read/write permission bits are not enforced between users, mounts are fixed at sandbox creation, and snapshots and read-only mounts are not yet supported. Read moreNetworking & deployment
Can I run sandboxes in the EU?
Yes. E2B offers a shared EU cluster for customers on the Pro tier and above. Contact support to get access. Read moreDo you publish egress IP ranges (CIDRs)?
No. Sandbox outbound traffic leaves from ephemeral, rotating IPs, so there is no fixed E2B-owned CIDR list. Allowlist the cloud provider’s published ranges or route sandbox traffic through your own proxy for a dedicated IP. Read moreWhy does iptables fail with ‘xt_owner module missing’ in a sandbox?
The E2B sandbox kernel does not ship thext_owner module, so iptables rules using --uid-owner or --gid-owner fail. Use nftables, which does not need xt_owner for owner-based matching. Read more
Why does my custom template fail with ‘port 49999 not open’?
The Code Interpreter service inside the sandbox did not start, usually because the custom template was not built on thecode-interpreter-v1 base or the start command is missing. Read more