Agent Sandboxesagentsandboxes.org
Head-to-head

Hyperbrowser vs Kernel

Answer in brief

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.

By the Agent Sandboxes editors · Updated

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

AttributeHyperbrowserKernel
What it isCredit-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.
TypeHosted platformHosted platform
IsolationSessions 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 machinesEach 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 sourceNoYes (Apache-2.0)
Self-host / BYOCNot documented / Not documentedYes / Not documented
SDKsPython, JavaScript/TypeScript, CLI, REST API, MCP serverJavaScript/TypeScript, Python, Go, CLI, REST API, MCP server
Cold start (vendor claim)Homepage claims under 500 ms from request to a ready browserDocs 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 sessionTeam 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 stopTimeout defaults to 60 seconds and starts when the browser enters standby (5 seconds after the last client disconnects); configurable up to 72 hours
PersistenceProfiles snapshot the user data directory (cookies, local storage, session storage, cache) and reload it in later sessions; persistChanges controls writes; profiles.fork() copies a profileStandby 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 / pauseNot documented / Not documentedYes / Yes
GPUNot documented for browsers; GPU (CUDA) sandboxes exist in the separate Sandboxes productHeadful browsers with GPU acceleration at $0.0008000016 per second on Start-Up and Enterprise plans
NetworkingResidential proxies at $10/GB with country/state/city selection or custom proxies; captcha solving; basic and ultra stealth modesManaged 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
PricingCredits, 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+ concurrentUsage 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 tierFree plan: 5,000 credits (about 50 browser hours at base rate), 1 concurrent session, 7-day retentionFree plan: $5 monthly credits, 5 concurrent browsers, 1-day replays; images are free to run yourself
ComplianceSecurity 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 otherwiseSOC 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
Regionsus-central, us-east, us-west, europe-west; asia-south on Enterprise/Select plansus-east (default), eu-west, ap-southeast; region selection on Start-Up and Enterprise plans
Company headquartersSan Francisco, California, United StatesSan Francisco, California, United States
Good fit forAgents that need cheap browser hours with a built-in path to run computer-use models as one-shot tasksAgents 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?
Neither is better for every workload. Hyperbrowser suits agents that need cheap browser hours with a built-in path to run computer-use models as one-shot tasks. Kernel suits agents that need fast, hypervisor-isolated browsers with pay-only-while-active billing.
What is the difference between Hyperbrowser and Kernel?
Hyperbrowser uses Isolated browser instance; Kernel uses Unikernel VM per browser. Kernel is open source (Apache-2.0); Hyperbrowser is not. Session length: Up to 12 h (Hyperbrowser) versus Up to 72 h (Kernel). Only Kernel lists Go.
Which is open source, Hyperbrowser or Kernel?
Hyperbrowser is not open source; Kernel is open source (Apache-2.0).
How do Hyperbrowser and Kernel isolate code?
Hyperbrowser: 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. Kernel: 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.
How does Hyperbrowser pricing compare with Kernel?
Hyperbrowser: 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. Kernel: 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. Rates change, so check the Hyperbrowser and Kernel pricing pages before deciding.
Do Hyperbrowser and Kernel support GPUs?
Hyperbrowser: Not documented. Kernel: Headful browsers with GPU acceleration at $0.0008000016 per second on Start-Up and Enterprise plans.
Can you self-host Hyperbrowser or Kernel?
Hyperbrowser: not documented. Kernel: yes.
How long can sessions run on Hyperbrowser and Kernel?
Hyperbrowser: 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. Kernel: Timeout defaults to 60 seconds and starts when the browser enters standby (5 seconds after the last client disconnects); configurable up to 72 hours.
Do Hyperbrowser and Kernel support snapshots or pause and resume?
Hyperbrowser: snapshots not documented, pause and resume not documented. Kernel: snapshots yes, pause and resume yes.

Sources

  1. hyperbrowser.ai
  2. hyperbrowser.ai/pricing
  3. hyperbrowser.ai/security
  4. hyperbrowser.ai/docs
  5. kernel.sh/
  6. kernel.sh/pricing
  7. kernel.sh/docs/introduction
  8. kernel.sh/docs/info/unikernels.md

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/