Why your agent gets caught
CHAPTER 01
by Scalebrowser | 2026
Read this chapter →Run your whole fleet with agents that pass as human.
Self-host Scalebrowser, point your agent at it over MCP or CDP, and launch profiles that stay coherent and unlinked — captchas handled, one flat price, nothing metered.
CHECKED EVERY MONDAY, IN PUBLIC
12 detectors run against a live fleet every week — last run 22 Jul 2026, 0 fails. Every result raw, dated and reproducible on your own machine.
One daemon runs the fleet. Every profile stays coherent.
Your agent asks for work. The daemon samples a persona, binds the exit, checks that the story holds together — and refuses to launch when it doesn't.
Fail-closed, not best-effort. A Windows persona without its font bundle, a GPU string that contradicts the host, an exit country that doesn't match the timezone — each one refuses the launch instead of shipping a tell.
One seed per profile. Canvas, WebGL, audio and text metrics answer from a single deterministic seed, so a profile looks the same tomorrow as it did today — and never like a randomiser.
Credentials stay inside. Proxy passwords are injected at launch and never reach the agent; it only ever gets a CDP socket.
Learn the ban wall before it learns you.
Four chapters on why fleets die and how to keep one alive. Free, no gate.
Build a profile that holds
CHAPTER 02
by Scalebrowser | 2026
Read this chapter →Run a fleet without linkage
CHAPTER 03
by Scalebrowser | 2026
Read this chapter →Keep the accounts alive
CHAPTER 04
by Scalebrowser | 2026
Read this chapter →A fork we actually maintain
The anti-detect work sits in C++ inside our own Chromium fork — not in a JavaScript patch that becomes the fingerprint itself. Chrome bumps are our problem, not yours.
Your agent drives it directly
Direct CDP and an MCP server — no Playwright control plane in the way, which is what gets blocked regardless of how good the patches are. Bring the framework you already use.
A fleet that can't be linked
Every profile carries its own persona, its own exit and its own seed — and keeps them. No re-randomising between sessions, because a profile that changes shape is a profile that dies.
Captchas and exits, handled
A datacenter IP is a tell before a single line of JavaScript runs. The daemon injects your residential or mobile exit, keeps DNS remote, closes the WebRTC leak — and clears the challenge when one appears.
It runs where you run it. Nothing phones home.
Three promises the metered clouds can't make — and the reason operators move their fleets onto their own hardware.
Eight operations are hiding in this grid.
The things people actually run on a fleet. Hover a word to keep it lit.
Pay for profiles. Never for minutes.
Every feature is in every tier — the engine, the MCP server, captcha handling, the AdsPower adapter. The only thing that changes is how many profiles you keep.
STARTER
€19
- Maintained engine, signed builds
- MCP + direct CDP + REST
- Captcha handling included
- Self-hosted, one machine
PRO
€45
- Everything in Starter
- Unlimited concurrent launches
- Zero-knowledge profile sync
- Weekly masking report, per fleet
SCALE
€139
- Everything in Pro
- Multi-host fleets
- Priority engine channel
- Migration kit from AdsPower
BUSINESS
€349
- Everything in Scale
- Founder on your Slack
- Custom detector targets
- Annual billing −40%
Pass-or-We-Fix
30 days. If Scalebrowser doesn't pass the detector tests on your setup, or doesn't handle your captchas, we fix it — or you get every euro back. No ticket maze.
The questions everyone asks first.
Does it really work, or will my accounts still die?
We publish a dated detector run every week — CreepJS, BrowserScan, iphey, Pixelscan and Cloudflare Turnstile among them — against a live fleet, with the raw output. You can reproduce every line on your own machine. If it doesn't hold on your setup, the guarantee applies.
Isn't this just another Playwright wrapper?
No. Playwright's control plane is detectable no matter how good the patches under it are, so we don't use it. Scalebrowser drives Chrome over raw CDP, and the fingerprint work lives in C++ inside our own maintained fork — not in an injected script.
Self-hosting sounds like work. What do I actually install?
One installer on Windows, one binary or container on Linux. The daemon serves the API, the desktop client bundles and supervises it. First profile running takes minutes, not an afternoon.
Where do my cookies and proxy credentials live?
On your machine. Profiles never leave your infrastructure, sync is zero-knowledge, and proxy passwords are injected at launch — your agent only ever sees a CDP socket, never a credential.
Do I need proxies as well?
Yes, and it matters more than any patch: a datacenter exit is scored before JavaScript runs. Bring residential or mobile exits; Scalebrowser injects them, keeps DNS remote and closes the WebRTC and QUIC leaks at launch.
What happens when Chrome updates?
We rebase the fork and ship a signed engine. That treadmill is the product — it's the reason free stealth patches rot within weeks of every Chrome bump.