The five detection layers
Bot detection stacks in five layers, and tools differ by which they address. Layer 1 — Protocol: CDP tells like Runtime.enable timing (Patchright, XDriver, CloakBrowser address it; Camoufox sidesteps it with Juggler). Layer 2 — Fingerprinting: canvas/WebGL/audio/screen — only the C++ tools (Camoufox, CloakBrowser) spoof these natively; JS-injection tools leak. Layer 3 — Behavioural: mouse and timing — Botasaurus and CloakBrowser lead. Layer 4 — Network: TLS (JA3/JA4) — only Scrapling's curl_cffi tier and Obscura's stealth build impersonate it; WebRTC/DNS leaks need handling. Layer 5 — Layout/rendering: getBoundingClientRect and real canvas output — passed only by real-browser tools, which is why Obscura (no layout engine) fails here.
How the eight tools compare
| Tool | Engine | Stealth approach | Best for |
|---|---|---|---|
| Camoufox | Firefox | C++ fingerprint + Juggler | Fingerprint rotation |
| CloakBrowser | Chromium | 33 C++ patches + humanize | Chromium C++ stealth |
| Patchright | Chromium | CDP patch (no Runtime.enable) | Playwright stealth |
| XDriver | Chromium | In-place driver patch | Quick Playwright stealth |
| SeleniumBase | Chrome | UC/CDP + PyAutoGUI | CAPTCHA solving |
| Botasaurus | Chrome | Bézier mouse + CDP events | Human behaviour |
| Scrapling | Mixed | Orchestrates the above + TLS | Full pipeline |
| Obscura | Rust/V8 | JS shim + optional TLS | Lightweight bulk |
Realistic success rates from the analysis: basic protection (Cloudflare Free) 90%+ tool-alone; medium (CF Pro, PerimeterX) 60–80%; enterprise (Akamai, DataDome) only 20–40% — rising to 70–85% with residential proxies. Custom ML defences sit under 20% even with good tooling.
The hard truth — and where a managed API fits
No tool is truly undetectable, and detection is an arms race. The signal the analysis returns to repeatedly: IP reputation matters more than stealth sophistication — the best fingerprint fails from a datacenter IP, and TLS fingerprinting is nearly impossible to fully spoof from a real browser. Behavioural patterns also accumulate, so the same scraping rhythm eventually gets caught regardless of mouse realism.
This is why high-volume teams often move the hard parts server-side. A managed API like Scrappey handles fingerprinting, CAPTCHA, residential proxies, and TLS impersonation behind one request — trading the control of running your own browser stack for not having to maintain it as detection evolves. For learning, testing, and self-hosted control, the open tools above remain the right choice; for production scale on hard targets, a managed layer removes the maintenance treadmill.
