Browser Use Cloud vs Kernel
Choose Browser Use Cloud for cheap stealth browser hours for agents built on the Browser Use library or any CDP client; choose Kernel for agents that need fast, hypervisor-isolated browsers with pay-only-while-active billing. Browser Use Cloud uses Isolated browser per run isolation; Kernel uses Unikernel VM per browser isolation and is open source.
Key differences between Browser Use Cloud and Kernel
- Isolation: Browser Use Cloud uses Isolated browser per run; Kernel uses Unikernel VM per browser.
- Open source: Kernel is open source (Apache-2.0); Browser Use Cloud is not.
- Session length: 1 h default, 4 h max (Browser Use Cloud) versus Up to 72 h (Kernel).
- SDKs and interfaces: Only Kernel lists Go, CLI and MCP server.
What they have in common
- Both companies are based in the United States.
- Both are hosted platforms.
- Both list Python, TypeScript and REST API.
Browser Use Cloud vs Kernel at a glance
| Attribute | Browser Use Cloud | Kernel |
|---|---|---|
| What it is | Stealth cloud Chromium at $0.06 per browser hour from the makers of the MIT-licensed Browser Use agent library, with profiles, live view, an EU deployment and a hosted agent API. | 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 | Every run gets its own isolated session (a browser, a proxy exit and a model context); the container or VM boundary is not named | 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, REST API | JavaScript/TypeScript, Python, Go, CLI, REST API, MCP server |
| Cold start (vendor claim) | Not documented | 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 | Standalone browser sessions default to 60 minutes with a maximum of 240 minutes; V4 agent browsers stop about 2 minutes after the last run (keepAlive 120 to 14,400 seconds) with a hard cap of 4 hours | 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 persist cookies, local storage and login state across browsers via profileId; local logins can be synced into a cloud profile; recording is off by default | 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 | Headful browsers with GPU acceleration at $0.0008000016 per second on Start-Up and Enterprise plans |
| Networking | Managed home-IP proxies ($5/GB) with country selection, or your own proxy or direct connection ($0.20/GB); captcha solving included; network policies allow or block domains | 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 | Pay as you go, $0/month: browsers $0.06 per browser hour billed by the minute (1-minute minimum); home-IP proxy $5/GB; own proxy or direct $0.20/GB; bu-ultrafast agent $0.006 per median task. Concurrency unlocks by lifetime spend: 10 at $0, 50 at $100, 250 at $1,000, 500 at $5,000, 1,000 at $25,000. Enterprise: custom | 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 | $1 sign-up credit, one per person, never expires; credits top up from $5 | Free plan: $5 monthly credits, 5 concurrent browsers, 1-day replays; images are free to run yourself |
| Compliance | SOC 2 Type II (audit period 17 July to 17 October 2025); HIPAA on enterprise plans (not on the EU deployment); signed DPA; zero data retention projects | 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 by default; EU deployment in Frankfurt (AWS) with its own API base URL and keys | 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 | Cheap stealth browser hours for agents built on the Browser Use library or any CDP client | 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 Browser Use Cloud
- You want browser hours billed by the minute at a listed $0.06 per hour
- You already use the Browser Use library and want its default cloud browser
- You need EU-resident browser runs
- You want captcha solving and residential proxies without a monthly fee
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
- Browser Use Cloud: Isolation boundary is not documented
- Browser Use Cloud: Sessions cap at 4 hours
- 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 Browser Use Cloud profile and Kernel profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Browser Use Cloud or Kernel better for AI agents?
What is the difference between Browser Use Cloud and Kernel?
Which is open source, Browser Use Cloud or Kernel?
How do Browser Use Cloud and Kernel isolate code?
How does Browser Use Cloud pricing compare with Kernel?
Do Browser Use Cloud and Kernel support GPUs?
Can you self-host Browser Use Cloud or Kernel?
How long can sessions run on Browser Use Cloud and Kernel?
Do Browser Use Cloud 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). Browser Use Cloud vs Kernel. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/browser-use-cloud-vs-kernel/