Skip to main content
E2B uses usage-based pricing - you pay only for what you use. New users receive $100 in free credits to get started. Manage billing in dashboard

​
Plans

FeatureHobbyProEnterprise
Base price$0/month$150/monthCustom
Free credits$100 (one-time)$100 (one-time)Custom
Max session length1 hour24 hoursCustom
Concurrent sandboxes20100 - 1,1001,100+
Pro plan includes 100 concurrent sandboxes. Higher concurrency up to 1,100 is available as a purchasable add-on.
Plans have different API rate limits. To upgrade your plan or purchase add-ons, visit the dashboard billing tab. For Enterprise plans, contact sales.

​
Usage-based pricing

You pay per second for compute resources while your sandbox is running.

​
Compute costs

Use the usage cost calculator on our pricing page to estimate costs for your specific configuration.

​
Customizing compute resources

You can customize allocated CPU and RAM when building custom templates by specifying cpuCount and memoryMB in the build configuration. 
import { Template, defaultBuildLogger } from 'e2b'

await Template.build(template, {
  alias: "my-template",
  cpuCount: 8,
  memoryMB: 4096,
  onBuildLogs: defaultBuildLogger(),
})
See template quickstart for more details on building custom templates.

​
Monitoring usage

Check your usage and costs in the dashboard usage tab.

​
FAQ

Automatically at the start of the month for the previous month’s usage.
Your account will be blocked. Add a payment method to continue using E2B.
Yes, you can set spending limits on the budget page in your dashboard.
  • Always kill sandboxes when done - Use sbx.kill() to stop billing immediately
  • Enable autopause - Automatically pause sandboxes after a period of inactivity to stop billing while preserving state
  • Allocate only what you need - Start with default resources (2 vCPU, 1 GB RAM) and increase only if necessary
  • Implement automatic timeouts - Set max session lengths to prevent forgotten sandboxes from running
  • Monitor actively running sandboxes - Use the CLI or dashboard to track active sandboxes
  • Use lifecycle events - Set up webhooks to get notified when sandboxes are created
No. You only pay while a sandbox is actively running. Once a sandbox is paused, killed or times out, billing stops immediately.