Skip to content
Shotcup
Dashboard

All comparisons

Shotcup vs E2B

E2B: Firecracker microVMs with full Linux. Shotcup: a fresh JavaScript engine per run, with hard limits and files back.

Which to pick

Pick E2B when

your agent needs an operating system: installing packages, running Python or a browser, or a session that lasts hours.

Pick Shotcup when

the code is JavaScript an agent wrote, runs are short and many, and you want a fixed monthly price, repeatable runs and files back.

The facts, side by side

Shotcup and E2B compared
QuestionShotcupE2B
What runs
  • A fresh GocciaScript engine per run in a pooled worker process, with a virtual filesystem. JavaScript only: no operating system, no npm at run time.
Start-up
  • Measured by us: 89.5 ms p50 server time for a whole run on shotcup.dev (2026-10-08), sandbox included.
  • Vendor: each session gets a Linux machine that boots from a snapshot; the site gives no create-time figure.e2b.dev,
How usage is billed
  • A monthly allowance of runs and compute-hours per plan; past it, opt-in overage of $0.05 per 1,000 runs and $0.08 per compute-hour under a spend cap.
Free tier and entry plan
  • Free: 30,000 runs and 3 h of compute a month. Pro: $4.99 a month for 100,000 runs and 10 h.
  • Hobby: $0 with a one-time $100 credit. Pro: "$150 monthly plan fee, plus usage".e2b.dev,
Concurrency and run length
  • 1 concurrent run on Free, 10 on Pro, up to 100 on Platform. A run lasts at most 5 s on Free and 5 min on Scale.
State between runs
  • Disposable by default; saved sandboxes keep their files between runs. Seeded clocks and randomness make runs repeatable, and a run that needs approval pauses and resumes.
MCP and agents
  • A hosted MCP server and a REST API on one key; a TypeScript SDK, an AI SDK sandbox and an eve provider.

E2B's start-up figure is its own claim; we did not measure it. Prices change: follow the links for the current ones. Shotcup's figures are explained on the performance page and the pricing page.