Browser Infrastructure

Built to look like a person. Measured on the sites that check.

Our own Chromium fork, new fingerprints every session, residential IPs in 195+ countries. 81% of the hardest 71 sites we could find, for $0.02 per browser-hour.

Create a stealth browser How we measured

Browser Use Cloud: 81% bypass rate. 4 points ahead of Anchor, the next best.

Browser Use Cloud81%
Anchor77%
Onkernel67%
Steel47%
Browserbase42%
Hyperbrowser40%

Bypass Rate · longer is better · scale 0–100%

BU Stealth Benchmark · updated 2026-03-21 · all benchmarks

81%
of 71 protected sites reached: 77%
Anchor, the next best provider: 2%
plain headless Chromium, the baseline

Why sites let it in.

The fingerprint layer makes the browser look like a person's machine: canvas, WebGL, fonts and navigator randomized per session, headless signals gone. The network layer gives it a residential address in the country the site expects. And if a challenge still renders, the browser solves it in place. Most sessions never reach that third step.

Residential exits in 195+ countries · pick one per session

Stealth is not a flag. The country is.

Every browser you create runs the hardened build. The one thing worth choosing is proxyCountryCode, because most protected sites score the IP and the locale together. Or route through your own proxy.

# Stealth is on. The one decision is the proxy country.curl -sS https://api.browser-use.com/api/v4/browsers \  -H "X-Browser-Use-API-Key: $BROWSER_USE_API_KEY" \  -H "Content-Type: application/json" \  -d '{"proxyCountryCode":"de"}'

create-browser.sh·Stealth on by default · CDP endpoint

Where each provider landed

Browser Use Cloud: 81% of 71 sites
Anchor: 77% of 71 sites
Onkernel: 67% of 71 sites
Steel: 47% of 71 sites
Browserbase: 42% of 71 sites
Hyperbrowser: 40% of 71 sites

Questions people ask

What makes it hard to detect?

It is our own Chromium build. Canvas, WebGL, fonts, navigator and the other fingerprint surfaces are randomized per session, headless signals are removed, and the build is rebuilt against upstream Chromium releases so detectors do not get ahead of it.

How is the number measured?

71 real sites behind Cloudflare, Akamai, PerimeterX and DataDome, picked from 300,000 security-check events in production traffic. Every provider ran the same tasks, repeatedly. The chart on this page is the result; plain headless Chromium scores 2% on it.

Does it get through Cloudflare?

On the benchmark, 93% of Cloudflare-protected sites, 85% of Akamai, 81% of PerimeterX. Nobody gets 100%, and detectors change, so the benchmark is re-run as they do.

Are proxies included?

Residential proxies in 195+ countries are on every browser at $5/GB, chosen per session by country code. Bring your own proxy and egress is $0.20/GB.

Does my Playwright or Puppeteer code need changes?

No. The browser is a normal CDP endpoint. connectOverCDP or puppeteer.connect, and your script runs as it did.