Hyperbrowser vs Kernel
Choose Hyperbrowser for agents that need cheap browser hours with a built-in path to run computer-use models as one-shot tasks; choose Kernel for agents that need fast, hypervisor-isolated browsers with pay-only-while-active billing. Hyperbrowser uses Isolated browser instance isolation; Kernel uses Unikernel VM per browser isolation and is open source.
Key differences between Hyperbrowser and Kernel
- Isolation: Hyperbrowser uses Isolated browser instance; Kernel uses Unikernel VM per browser.
- Open source: Kernel is open source (Apache-2.0); Hyperbrowser is not.
- Session length: Up to 12 h (Hyperbrowser) versus Up to 72 h (Kernel).
- SDKs and interfaces: Only Kernel lists Go.
What they have in common
- Both companies are based in the United States.
- Both are hosted platforms.
- Both list Python, TypeScript, CLI, REST API and MCP server.
Hyperbrowser vs Kernel at a glance
| Attribute | Hyperbrowser | Kernel |
|---|---|---|
| What it is | Credit-billed cloud Chrome sessions with profiles, stealth and captcha solving, plus one-shot agent runs (Claude Computer Use, OpenAI CUA, Browser Use) and separate VM-based code sandboxes. | Browsers for agents where each Chromium runs in its own Unikraft unikernel VM, with standby that stops billing, profiles, and open-source images under Apache-2.0. |
| Type | Hosted platform | Hosted platform |
| Isolation | Sessions are described as isolated browser instances running in the cloud; the boundary is not named. The separate Sandboxes product states commands run in isolated virtual machines | Each browser runs in a dedicated Unikraft-based unikernel VM, isolated at the hypervisor level with no shared host kernel; hypervisor not named in the docs |
| Open source | No | Yes (Apache-2.0) |
| Self-host / BYOC | Not documented / Not documented | Yes / Not documented |
| SDKs | Python, JavaScript/TypeScript, CLI, REST API, MCP server | JavaScript/TypeScript, Python, Go, CLI, REST API, MCP server |
| Cold start (vendor claim) | Homepage claims under 500 ms from request to a ready browser | Docs state a browser is created in about 30 ms at p50 and 105 ms at p99; the unikernels page claims cold starts under 20 ms |
| Max session | Team default timeout (configurable in settings); per-session timeoutMinutes from 1 to 720 (12 hours); keepAlive keeps a session running after CDP disconnect until timeout or stop | Timeout defaults to 60 seconds and starts when the browser enters standby (5 seconds after the last client disconnects); configurable up to 72 hours |
| Persistence | Profiles snapshot the user data directory (cookies, local storage, session storage, cache) and reload it in later sessions; persistChanges controls writes; profiles.fork() copies a profile | Standby keeps browser state without billing until a client reconnects; Profiles capture the user data directory (cookies, auth, local storage, tabs) and are saved with save_changes; encrypted per organisation |
| Snapshots / pause | Not documented / Not documented | Yes / Yes |
| GPU | Not documented for browsers; GPU (CUDA) sandboxes exist in the separate Sandboxes product | Headful browsers with GPU acceleration at $0.0008000016 per second on Start-Up and Enterprise plans |
| Networking | Residential proxies at $10/GB with country/state/city selection or custom proxies; captcha solving; basic and ultra stealth modes | Managed residential proxy and captcha solver in stealth mode; configurable and bring-your-own proxies on higher plans; egress allowlists cover browser traffic through the proxy |
| Pricing | Credits, 1,000 credits = $1. Browser $0.10/hour, proxy $10/GB, sandboxes $0.045/vCPU-hour + $0.015/GiB-hour, HyperAgent/Browser Use $0.02/step. Free: 5,000 credits, 1 concurrent. Startup $30/month: 30,000 credits, 25 concurrent. Scale $100/month: 100,000 credits, 100 concurrent. Enterprise: custom, 1,000+ concurrent | Usage per second: headless $0.0000166667/s, headful $0.0001333336/s, headful + GPU $0.0008000016/s; standby and idle pool browsers are not billed. Plans: Free $0 + usage ($5 credits, 5 concurrent), Hobbyist $30/month ($10 credits, 10 concurrent), Start-Up $200/month ($50 credits, 150 concurrent, regions, GPU), Enterprise custom |
| Free tier | Free plan: 5,000 credits (about 50 browser hours at base rate), 1 concurrent session, 7-day retention | Free plan: $5 monthly credits, 5 concurrent browsers, 1-day replays; images are free to run yourself |
| Compliance | Security programme aligned with SOC 2 Trust Services Criteria with independent assessments; the trust centre lists a SOC 2 Type 1 report on request; production data stored in US cloud databases unless agreed otherwise | SOC 2 Type II (report on request); HIPAA; PCI DSS Level 4 (SAQ A); ISO 27001 and GDPR listed as in progress; zero data retention on Enterprise |
| Regions | us-central, us-east, us-west, europe-west; asia-south on Enterprise/Select plans | us-east (default), eu-west, ap-southeast; region selection on Start-Up and Enterprise plans |
| Company headquarters | San Francisco, California, United States | San Francisco, California, United States |
| Good fit for | Agents that need cheap browser hours with a built-in path to run computer-use models as one-shot tasks | Agents that need fast, hypervisor-isolated browsers with pay-only-while-active billing |
Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Hyperbrowser
- You want low per-hour browser pricing with a usable free tier
- You need to run Claude Computer Use, OpenAI CUA or Browser Use as a hosted task
- You want profiles that persist logins and can be forked
- You need a European or Asian region
Reasons to choose Kernel
- You want each browser in its own VM without paying for idle time
- You need long-lived browsers (up to 72 hours) that survive client disconnects
- You want to inspect or run the browser images yourself
- You need GPU-accelerated headful browsers or regional placement
Trade-offs to check first
- Hyperbrowser: Isolation boundary for browsers is not documented
- Hyperbrowser: The security page states alignment with SOC 2 criteria; the trust centre lists a SOC 2 Type 1 report on request
- Kernel: The docs do not say which hypervisor the cloud uses; the unikernel build in kernel-images deploys to Unikraft Cloud, while the Docker image runs locally
- Kernel: Region selection, GPU and BYO proxies require the $200/month Start-Up plan
Both are worth piloting with your own image and region. See the full Hyperbrowser profile and Kernel profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Hyperbrowser or Kernel better for AI agents?
What is the difference between Hyperbrowser and Kernel?
Which is open source, Hyperbrowser or Kernel?
How do Hyperbrowser and Kernel isolate code?
How does Hyperbrowser pricing compare with Kernel?
Do Hyperbrowser and Kernel support GPUs?
Can you self-host Hyperbrowser or Kernel?
How long can sessions run on Hyperbrowser and Kernel?
Do Hyperbrowser and Kernel support snapshots or pause and resume?
Sources
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
Agent Sandboxes. (2026). Hyperbrowser vs Kernel. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/hyperbrowser-vs-kernel/