Browser Use Rebuilds Its Cloud Stack to Beat Antibot Systems at 81%
Browser Use rebuilt its cloud browser stack from bare metal up, cutting costs 3x and hitting #1 on every major stealth benchmark
Running an AI agent against a real website is harder than it sounds. The moment your agent fires up a headless browser, most major sites detect the automation signal and block it before a single task completes. Browser Use just shipped a ground-up rebuild of its cloud browser infrastructure that attacks this problem at the kernel level, not with patches on top of stock Chromium.
What actually shipped
The new stack is built on a custom Chromium fork, a Firecracker fork, and a custom Linux kernel. That's three layers of infrastructure Browser Use now owns and maintains themselves, rather than renting from third parties. It runs on bare metal, costs $0.02 per hour, starts in under a second, and can handle up to 10,000 concurrent browsers.
The new pricing is more than 3x cheaper than the previous offering, which puts it at a price point where browser time becomes a rounding error even across thousands of agent sessions. The infrastructure is live now and applies to all cloud browsers on the Browser Use Cloud.
The stealth problem is worse than most people think
The bottleneck for agents is not their intelligence. On most websites users care about, agents get blocked by a CAPTCHA or an antibot challenge. Browser Use collected 300,000 security check events from production traffic, and the data made it clear: agent intelligence and browser stealth are orthogonal. You need to measure them separately.
To quantify how bad the baseline is, a plain headless Chromium scores just 2% on the Browser Use Stealth Benchmark, while headful Chromium scores 50%. That gap exists purely because headless mode is trivially detectable. Most cloud browser providers don't solve this; they just run headful Linux Chromium behind a residential proxy and call it "Advanced Stealth."
How the stack is built
Firecracker is a microVM technology originally built by Amazon for AWS Lambda. It launches microVMs with a stripped-down device model, minimal attack surface, and KVM-based virtualization, fast enough for serverless workloads and isolated enough to run untrusted code. Firecracker can initiate user-space code in as little as 125ms and supports microVM creation rates of up to 150 microVMs per second per host. Browser Use forked Firecracker and paired it with a custom Linux kernel to squeeze out even more performance and density for browser workloads specifically.
On the browser side, every cloud browser session runs in a hardened Chromium fork with stealth enabled by default, no configuration needed. Canvas, WebGL, fonts, navigator, and other browser fingerprints are randomized per session to appear as a real user, passing CreepJS, BrowserLeaks, and other fingerprint detectors. Crucially, this is done at the source level inside the fork, not via JavaScript injection or flags, which means detection systems can't spot the patches.
The full feature set of a session includes:
- Fully headless operation with a custom Chromium fork that beats antibot systems even without rendering a visible window
- Real device fingerprints from macOS, Windows, and Linux profiles, with browser-level consistency across all signals
- Ad and cookie banner blocking built in, so agents see clean pages and execute faster
- Cloudflare, PerimeterX, and other antibot bypass out of the box
- Residential proxy routing across 195+ countries at $5/GB, included by default
- In-house CAPTCHA solving that runs inside the browser, no external solver service needed
The benchmark numbers
Browser Use runs two benchmarks to validate stealth. The first is their own BU Stealth Benchmark, built from 300,000 real production security check events across 71 high-security sites spanning Cloudflare, PerimeterX, Datadome, Akamai, reCaptcha, and others. The second is Halluminate's third-party BrowserBench, which covers 296 tasks across antibot-protected sites.
| Provider | BU Stealth Benchmark | BrowserBench (Halluminate) |
|---|---|---|
| Browser Use Cloud | 81% | 84.8% |
| Anchor | 77% | 76.0% |
| Onkernel | 67% | -- |
| Hyperbrowser | 40% | 76.4% |
| Steel | 47% | 73.3% |
| Browserbase | 42% | 70.3% |
Browser Use Cloud achieves the highest scores of any provider: 81% of protected sites on the stealth benchmark and 84.8% on BrowserBench. The vendor breakdown shows the strongest bypass rates against Cloudflare at 93%, Akamai at 85%, and PerimeterX at 81%.
Plugging it in
Sessions are remote and CDP-compatible, meaning Chrome DevTools Protocol, the standard interface Playwright and Puppeteer already speak. Existing automation code connects without changes. Here's how to spin up a session via the API:
import requests
API_KEY =