Agent Sandboxesagentsandboxes.org
Head-to-head

Browserbase vs Kernel

Answer in brief

Choose Browserbase for web agents that need managed Chromium at scale with persisted logins and stealth; choose Kernel for agents that need fast, hypervisor-isolated browsers with pay-only-while-active billing. Browserbase uses Dedicated VM per browser isolation; Kernel uses Unikernel VM per browser isolation and is open source.

By the Agent Sandboxes editors · Updated

Key differences between Browserbase and Kernel

  • Isolation: Browserbase uses Dedicated VM per browser; Kernel uses Unikernel VM per browser.
  • Open source: Kernel is open source (Apache-2.0); Browserbase is not.
  • GPUs: Kernel documents GPU support; Browserbase does not.
  • Session length: 6 h (15 min Free) (Browserbase) versus Up to 72 h (Kernel).
  • SDKs and interfaces: Only Kernel lists Go and CLI.

What they have in common

  • Both companies are based in the United States.
  • Both are hosted platforms.
  • Both list Python, TypeScript, REST API and MCP server.

Browserbase vs Kernel at a glance

AttributeBrowserbaseKernel
What it isHosted headless Chromium sessions for web agents, driven over CDP with Playwright, Puppeteer, Selenium or the Stagehand SDK, with Contexts for persisted logins and four regions.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
IsolationEach session is an isolated Chromium instance with its own user data directory, fingerprint and network identity; the enterprise security page states each browser runs in a dedicated VM that is killed and recreated after each sessionEach 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, REST API, MCP serverJavaScript/TypeScript, Python, Go, CLI, REST API, MCP server
Cold start (vendor claim)Vendor blog claims a session is ready to be driven in under 2 secondsDocs 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 sessionMaximum 6 hours per session; Free plan sessions are limited to 15 minutes; keepAlive (paid plans) keeps a session running after disconnect until its timeout or explicit releaseTimeout defaults to 60 seconds and starts when the browser enters standby (5 seconds after the last client disconnects); configurable up to 72 hours
PersistenceSessions start fresh by default; Contexts persist cookies, auth, localStorage, IndexedDB and other profile data across sessions (not the HTTP cache) and are encrypted at restStandby 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
GPUNo — not offeredHeadful browsers with GPU acceleration at $0.0008000016 per second on Start-Up and Enterprise plans
NetworkingManaged proxies with rotation and geo-targeting or bring your own proxy; allowed-domains setting; captcha solving on by default; automatic fingerprintingManaged 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
PricingFree $0: 1 browser hour, 3 concurrent, 15-minute sessions. Developer $20/month: 100 hours, 25 concurrent, $0.12 per extra hour, 1 GB proxy then $12/GB. Startup $99/month: 500 hours, 100 concurrent, $0.10 per extra hour, 5 GB proxy then $10/GB. Scale: custom, 250+ concurrent, usage-basedUsage 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: 1 browser hour, 3 concurrent browsers, 15-minute sessions, 7-day data retentionFree plan: $5 monthly credits, 5 concurrent browsers, 1-day replays; images are free to run yourself
ComplianceSOC 2 Type II; HIPAA BAA and DPA available on request; SSO/SAMLSOC 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-west-2 (default), us-east-1, eu-central-1, ap-southeast-1us-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 forWeb agents that need managed Chromium at scale with persisted logins and stealthAgents 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 Browserbase

  • You want a managed Chromium that works with your existing Playwright, Puppeteer or Selenium code
  • You need persisted logins across runs via Contexts
  • You want EU or Asia-Pacific placement and audited compliance (SOC 2 Type II, HIPAA BAA)
  • You are building with Stagehand or an MCP client and want the hosted server

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

  • Browserbase: Sessions are capped at 6 hours on self-serve plans, and 15 minutes on the Free plan
  • Browserbase: Self-hosting and BYOC are not documented; the platform itself is not open source
  • 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 Browserbase profile and Kernel profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Browserbase or Kernel better for AI agents?
Neither is better for every workload. Browserbase suits web agents that need managed Chromium at scale with persisted logins and stealth. Kernel suits agents that need fast, hypervisor-isolated browsers with pay-only-while-active billing.
What is the difference between Browserbase and Kernel?
Browserbase uses Dedicated VM per browser; Kernel uses Unikernel VM per browser. Kernel is open source (Apache-2.0); Browserbase is not. Kernel documents GPU support; Browserbase does not. Session length: 6 h (15 min Free) (Browserbase) versus Up to 72 h (Kernel). Only Kernel lists Go and CLI.
Which is open source, Browserbase or Kernel?
Browserbase is not open source; Kernel is open source (Apache-2.0).
How do Browserbase and Kernel isolate code?
Browserbase: Each session is an isolated Chromium instance with its own user data directory, fingerprint and network identity; the enterprise security page states each browser runs in a dedicated VM that is killed and recreated after each session. 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 Browserbase pricing compare with Kernel?
Browserbase: Free $0: 1 browser hour, 3 concurrent, 15-minute sessions. Developer $20/month: 100 hours, 25 concurrent, $0.12 per extra hour, 1 GB proxy then $12/GB. Startup $99/month: 500 hours, 100 concurrent, $0.10 per extra hour, 5 GB proxy then $10/GB. Scale: custom, 250+ concurrent, usage-based. 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 Browserbase and Kernel pricing pages before deciding.
Do Browserbase and Kernel support GPUs?
Browserbase: No — not offered. Kernel: Headful browsers with GPU acceleration at $0.0008000016 per second on Start-Up and Enterprise plans.
Can you self-host Browserbase or Kernel?
Browserbase: not documented. Kernel: yes.
How long can sessions run on Browserbase and Kernel?
Browserbase: Maximum 6 hours per session; Free plan sessions are limited to 15 minutes; keepAlive (paid plans) keeps a session running after disconnect until its timeout or explicit release. 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 Browserbase and Kernel support snapshots or pause and resume?
Browserbase: snapshots not documented, pause and resume not documented. Kernel: snapshots yes, pause and resume yes.

Sources

  1. browserbase.com
  2. browserbase.com/pricing
  3. browserbase.com/enterprise
  4. docs.browserbase.com/welcome/introduction
  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). Browserbase vs Kernel. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/browserbase-vs-kernel/