Home / Compare / Kernel vs Hyperbrowser
Kernel vs Hyperbrowser
Verdict (2026-11-15): Kernel scores higher: 76/100 vs 60/100 as browser sandboxes for AI agents. Choose Kernel for agents that wait on users or models between actions, since standby stops charges. Choose Hyperbrowser for agents that need both a hosted browser and a code sandbox under one credit balance.
Kernel
Highest scoreCloud Chromium browsers in per-browser unikernel microVMs, billed per second by memory and paused when idle.
$0.06 per browser-hour
Hyperbrowser
Hosted browsers for agents at $0.10 per browser-hour, plus Firecracker VM sandboxes billed by vCPU and memory.
$0.10 per browser-hour
Score by part
Cost at four workloads
| Workload | Kernel | Hyperbrowser |
|---|---|---|
| Short tasks: 1 vCPU, 1 GiB, 50 h/month | $0.00 | $30.00 |
| Dev agent: 2 vCPU, 4 GiB, 176 h/month | $37.24 | $30.00 |
| Fleet: 2 vCPU, 4 GiB, 1,760 h/month | $417.40 | $264.00 |
| Always on: 4 vCPU, 8 GiB, 730 h/month | $345.40 | $219.00 |
Per month, cheapest plan for each, without storage, network or GPU. Lowest cost in bold.
Choose Kernel if
- Agents that wait on users or models between actions, since standby stops charges
- Untrusted pages or code next to the browser, given per-browser VM isolation
- Proxy-heavy work, since proxy traffic is not metered
Choose Hyperbrowser if
- Agents that need both a hosted browser and a code sandbox under one credit balance
- Cheap browser automation at $0.10 per browser-hour before proxies
- Restoring prepared environments quickly from memory snapshots
Side by side
| Kernel | Hyperbrowser | |
|---|---|---|
| Category | browser sandbox | browser sandbox, agent sandbox |
| Our score | 76/100 | 60/100 |
| Isolation | Each browser runs in its own unikernel microVM with its own kernel and filesystem, isolated at the hypervisor | Firecracker microVM per CPU sandbox; GPU sandboxes use a gVisor runtime |
| vCPU per hour | Included in the memory price | $0.045 |
| Memory per GiB-hour | $0.06 | $0.015 |
| Per browser-hour | $0.06 | $0.10 |
| Billing | Per second | Not stated for CPU sandboxes and browsers (rates quoted per hour); GPU time per second |
| Free tier | Developer plan: $5 of usage credit every month, 5 concurrent browsers, no credit card required. | Free account with 5,000 credits ($5), enough for about 50 browser-hours; 1 concurrent session; upgrade required once used. |
| Pause and resume | Yes | Not stated |
| Snapshots | Yes | Yes |
| GPU | Yes | Yes |
| Custom images | Not stated | Yes |
| Network controls | Yes | Yes |
| Max vCPU | Not stated | 32 vCPU |
| Max memory | 16 GiB | 256 GiB |
| Open source | Yes (Apache-2.0) | No |
| Self-host | Yes | No |
| SDKs and interfaces | TypeScript, Python, Go, CLI, MCP server, Playwright, CDP | Node.js, Python, CLI (hx), REST API |
| Regions | US by default; regional browsers are available on the Start-Up and Enterprise plans at the same rates. | US regions (for example us-west); other regions not stated. |
| Facts checked | 2026-11-13 | 2026-11-13 |
Kernel alternatives · Hyperbrowser alternatives
Sources
- Kernel: https://www.kernel.sh/pricing, checked 2026-11-13:
Usage costs: $0.0000166667 per GB-second (no charges for idle time or proxies).
- Kernel: https://www.kernel.sh/pricing, checked 2026-11-13:
$5 / month free credits
- Kernel: https://www.kernel.sh/docs/info/pricing, checked 2026-11-13:
Headless browser |0.0000166667
- Kernel: https://www.kernel.sh/docs/info/pricing, checked 2026-11-13:
Headful browser + GPU acceleration |0.0008000016
- Kernel: https://www.kernel.sh/docs/info/pricing, checked 2026-11-13:
Start-Up |$200 + usage |$50
- Kernel: https://www.kernel.sh/docs/browsers/concurrency-and-limits, checked 2026-11-13:
Memory |8 GB or 16 GB |1 GB, 2 GB, or 4 GB
- Kernel: https://www.kernel.sh/docs/overview/why-kernel, checked 2026-11-13:
Each browser is a microVM with its own kernel and filesystem
- Kernel: https://www.kernel.sh/docs/browsers/standby, checked 2026-11-13:
Kernel browsers automatically start entering standby after ten seconds with no activity.
- Kernel: https://github.com/kernel/kernel-images, checked 2026-11-13:
This image can be used to run headful Chromium in a Docker container or with Unikraft unikernels.
- Hyperbrowser: https://www.hyperbrowser.ai/pricing, checked 2026-11-13:
|Browser usage |100 credits / hour |$0.10 / hour |
- Hyperbrowser: https://www.hyperbrowser.ai/pricing, checked 2026-11-13:
|vCPU |45 credits / vCPU-hour |$0.045 / vCPU-hour |
- Hyperbrowser: https://www.hyperbrowser.ai/pricing, checked 2026-11-13:
|Memory |15 credits / GiB-hour |$0.015 / GiB-hour |
- Hyperbrowser: https://www.hyperbrowser.ai/pricing, checked 2026-11-13:
Both vCPU and allocated memory are billed while the VM runs.
- Hyperbrowser: https://www.hyperbrowser.ai/pricing, checked 2026-11-13:
Enough for 50 browser hours or 5,000 fetched pages at base rates.
- Hyperbrowser: https://www.hyperbrowser.ai/pricing, checked 2026-11-13:
If you use all the credits on Free, upgrade to continue.
- Hyperbrowser: https://www.hyperbrowser.ai/pricing, checked 2026-11-13:
Your plan's credits reset each time your plan renews, and unused plan credits don't carry over.
- Hyperbrowser: https://www.hyperbrowser.ai/docs/pricing, checked 2026-11-13:
| `H100` | 1.097 | $3.9492 |
- Hyperbrowser: https://www.hyperbrowser.ai/docs/pricing, checked 2026-11-13:
GPU sandboxes are billed per allocated GPU-second, plus the vCPU and system memory rates above.
- Hyperbrowser: https://www.hyperbrowser.ai/docs/api-reference/create-new-sandbox, checked 2026-11-13:
Requests without GPU or macOS options create CPU sandboxes (firecracker).
- Hyperbrowser: https://www.hyperbrowser.ai/docs/api-reference/create-new-sandbox, checked 2026-11-13:
description: Outbound internet access policy.
- Hyperbrowser: https://www.hyperbrowser.ai/docs/sandboxes/snapshots, checked 2026-11-13:
When you take a snapshot, you are freezing the sandbox's memory, processes, and filesystem at that point in time.
Questions
Is Kernel or Hyperbrowser better?
Kernel scores higher on our published method: 76/100 vs 60/100 as browser sandboxes for AI agents. Choose Kernel for agents that wait on users or models between actions, since standby stops charges. Choose Hyperbrowser for agents that need both a hosted browser and a code sandbox under one credit balance. Checked 2026-11-13.
Is Kernel or Hyperbrowser cheaper?
Kernel is cheaper: Kernel $0.06, Hyperbrowser $0.10 per browser-hour.
How do Kernel and Hyperbrowser isolate code?
Kernel: Each browser runs in its own unikernel microVM with its own kernel and filesystem, isolated at the hypervisor. Hyperbrowser: Firecracker microVM per CPU sandbox; GPU sandboxes use a gVisor runtime.