The open-source nodriver alternative
nodriver is the modern successor to undetected-chromedriver — fast, async, no Selenium, straight CDP. But it still drives a stock Chrome and doesn't touch the network layer. Clearcote pairs the same CDP-first ergonomics with an engine that actually changes the fingerprint and a coherent TLS/HTTP-2 persona.
What is nodriver?
nodriver (by the undetected-chromedriver author, ~4.5k stars) drops Selenium and the chromedriver binary entirely and talks the Chrome DevTools Protocol directly, async. That removes the whole WebDriver detection surface and is fast and pleasant to use. It's AGPL-3.0 and actively maintained — the recommended path in that lineage.
But nodriver is a driver/orchestration layer, not an engine. The Chrome it drives is stock, so native fingerprint values aren't changed coherently, and driving over CDP can still exhibit CDP-usage tells (the Runtime.enable class of leaks that separate projects exist to patch). There's no TLS/JA3-JA4 or HTTP/2 control. Note too that AGPL-3.0 is strong network-copyleft — a real consideration for commercial or SaaS use.
Clearcote vs nodriver
| Feature | Clearcote | nodriver |
|---|---|---|
| Approach | Engine-level C++ patches — native values | Direct CDP on stock Chrome |
| Fingerprint control | Coherent persona in the engine | Stock engine values, unchanged |
| TLS / network coherence | Follows the claimed Chrome (JA3/JA4 + HTTP/2) | Stock automation network signature |
| Interface | Playwright & Puppeteer + a standing CDP endpoint | Own async CDP API (Python) |
| License | Open & permissive | AGPL-3.0 (network copyleft) |
| Maintenance | Active | Active |
| Cost | Free & open | Free & open |
Comparison compiled July 2026. nodriver is open source (agpl-3.0); details change — check its project for the latest.
Why teams pick Clearcote
Changes the engine, not just the driver
nodriver removes the WebDriver seam but drives an unmodified Chrome. Clearcote patches the fingerprint into the engine, so canvas, WebGL and navigator present a coherent persona.
A coherent network layer
nodriver leaves TLS/JA3-JA4 and HTTP/2 as a stock signature. Clearcote's handshake follows the claimed Chrome version.
Permissive license
nodriver is AGPL-3.0 (strong network-copyleft), which many commercial and SaaS teams avoid. Clearcote uses a permissive license.
Same CDP ergonomics, more surface
You keep a clean CDP-first workflow — plus Playwright/Puppeteer, Docker, and an MCP server on top.
When nodriver might be the better pick
- You want a lightweight async CDP scraper and AGPL-3.0 is fine for your use.
- Your targets are easy-to-moderate and you don't need engine or TLS coherence.
- It's actively maintained and fast — a solid modern choice in its niche.
FAQ
nodriver vs Clearcote?
nodriver is an async CDP client that drives a stock Chrome; Clearcote is a modified Chromium you drive with Playwright/Puppeteer or its CDP endpoint. nodriver removes the driver seam; Clearcote changes the fingerprint in the engine and ships a coherent TLS/HTTP-2 persona — layers nodriver doesn't reach.
Does nodriver change the browser fingerprint?
Not at the engine level — it drives an unmodified Chrome, so canvas/WebGL/navigator and the TLS stack are stock. It focuses on removing the WebDriver/chromedriver detection surface.
Is the AGPL license a concern?
For some. AGPL-3.0 is strong network-copyleft, which some commercial/SaaS teams avoid. Clearcote uses a permissive license.
Related reading
Try the open-source Chromium alternative
Free and open source, a drop-in for Playwright & Puppeteer, coherent down to the TLS handshake.