Hopx vs E2B
Hopx runs untrusted and AI-generated code in microVM sandboxes that start in about 100 ms, billed per second. For agent builders who want E2B-style sandboxes with a large starting credit. A 2 vCPU / 4 GiB sandbox lists at $0.166 an hour on Hopx, exactly E2B's $0.166.
Hopx against E2B, line by line
E2B baseline sourcesPrices are list prices for one hour of a 2 vCPU / 4 GiB sandbox: 2 × the vCPU rate + 4 × the memory rate. Each value links to the page it came from; not published means the vendor states no figure. How we compare.
Pick Hopx instead of E2B when
- your agents run longer than E2B's 24-hour Pro session cap: No execution time limit ("hours, days, or weeks").
- you want a published start time: Hopx states 100 ms (a vendor claim), and E2B publishes no figure.
- you are prototyping: $200 free credits, no credit card.
Stay on E2B when
- pause has to keep running memory as well as files: E2B's pause saves both, and Hopx does not state memory state in our data.
- you need a SOC 2 report: E2B states Type II, and Hopx states none in our data.
- you want managed cloud, your own cloud account and self-hosting from one vendor: E2B offers all three, with BYOC on its Enterprise plan.
All Hopx facts
Source per value- Isolation Isolation technology the vendor states for each sandbox.
- Firecracker microVM 2
- Other isolation options Alternative runtimes the vendor offers besides the default (e.g. VM runtime, gVisor for GPU).
- Not published
- Deployment Managed cloud service, self-hosted software, or both.
- managed 1
- Billing basis What the meter counts: wall-clock allocated resources, active CPU only, requests/plan quota, session-hours, or free software.
- wall clock 1
- vCPU price $/vCPU-hr Published on-demand CPU rate normalised to USD per vCPU-hour (per-second rates multiplied by 3,600; per-core rates divided by vCPUs per core where the vendor defines it). Lowest public tier, default region. 0 means the vendor states no separate CPU charge.
- $0.0504 1
- Memory price $/GiB-hr Published memory rate normalised to USD per GiB-hour (GB treated as GiB where the vendor does not distinguish). 0 means the vendor states memory is free.
- $0.0162 1
- Sandbox from $/sandbox-hr Smallest published per-sandbox hourly price, where the vendor publishes one.
- Not published
- Paid plan from $/mo Cheapest paid platform plan fee (before usage).
- Not published
- Free tier A free plan, free monthly allowance or sign-up credit exists.
- Yes 1
- Free tier detail What the free tier or credit includes, as published.
- $200 free credits, no credit card. 1
- Cold start ms Vendor-published create/boot time in milliseconds (a vendor claim, not our benchmark). Only filled when the vendor publishes a number; see startup_claim for percentile and conditions.
- 100 1
- Resume time ms Vendor-published resume-from-pause/standby/snapshot time in milliseconds.
- Not published
- Startup claim The vendor's startup/resume wording with conditions, quoted or closely paraphrased.
- microVMs "spin up in ~100ms" 1
- Max session length Longest single sandbox session by plan, as published.
- No execution time limit ("hours, days, or weeks") 2
- Persistence / snapshots Filesystem state can be kept between runs (snapshots, persistent disks, volumes).
- Yes 2
- Pause / resume A sandbox can be paused, suspended, hibernated or put in standby and resumed later.
- Not published
- Memory state kept Pause/hibernate preserves running memory state, not only the filesystem.
- Not published
- Fork / branch A running or snapshotted sandbox can be cloned into new sandboxes.
- Not published
- GPU GPU sandboxes are offered.
- Not published
- Self-host Can run on your own hardware or cluster (open source or licensed).
- Not published
- BYOC / VPC Vendor-managed deployment inside your own cloud account.
- Not published
- Open source Core sandbox runtime is published under an open-source licence.
- Not published
- Licence Open-source licence of the runtime, if any.
- Not published
- SDKs / languages Official SDK languages (or supported execution languages where noted).
- Python, JavaScript; MCP server 2
- Regions Published regions or region count.
- Not published
- Max vCPU per sandbox vCPU Largest published vCPU count per sandbox on any self-serve or enterprise plan.
- Not published
- Max memory per sandbox GiB Largest published memory per sandbox.
- Not published
- Concurrency Published concurrent sandbox limits by plan.
- Not published
- SOC 2 SOC 2 status as stated by the vendor.
- Not published
- HIPAA Vendor offers HIPAA-compliant usage/BAA (on any plan).
- Not published
- 2 vCPU + 4 GiB per hour $/hr Hourly list price of one 2 vCPU / 4 GiB sandbox: 2 x the vCPU rate + 4 x the memory rate, from the two published rates. Left empty for self-hosted software and for vendors without both rates. Vendors that bill CPU only while busy (Vercel, Cloudflare, Upstash, Tensorlake, AWS AgentCore) cost less for idle agents than this shows.
- $0.1656 1
- Price vs E2B x E2B The 2 vCPU + 4 GiB hourly price divided by E2B's own ($0.1656 at $0.000014/vCPU-s and $0.0000045/GiB-s). Under 1 is cheaper than E2B.
- 1 1
- Status Preview, experimental, beta, sunset or self-hosting caveats the vendor documents.
- Not published
- Pricing model
- usage
- From
- $0.0504 vCPU-hour
- Pricing note
- Published per second: $0.000014/vCPU-s, $0.0000045/GiB-s, $0.00000003/GiB-s storage; hourly values are x3,600. Pricing checked 2026-11-09.
Sources
- Hopx Pricing accessed 2026-11-09
- Hopx homepage accessed 2026-11-09
Hopx in the E2B comparisons
- E2B alternatives with microVM or VM isolationWhich E2B alternatives give each sandbox its own kernel? 26 listed.
Compare with other E2B alternatives
All 41- Fly.io Sprites vs E2B $0.165/hr, 0.99x E2B, VM
- Hyperbrowser vs E2B $0.150/hr, 0.91x E2B, VM
- Cloudflare Sandbox SDK / Containers vs E2B $0.180/hr, 1.09x E2B, Firecracker microVM
- Together Code vs E2B $0.149/hr, 0.9x E2B, microVM
- Freestyle vs E2B $0.132/hr, 0.8x E2B, VM
Get a quote from Hopx and similar alternatives
Tell us what you need once. We send it to matching alternatives and they reply to you directly.