The open-source nodriver alternative
nodriver is the successor to undetected-chromedriver: fast, async, no Selenium, straight CDP. But it still drives a stock Chrome, so the fingerprint is your machine's. Clearcote keeps the CDP-first ergonomics and changes the fingerprint and TLS in the engine.
What is nodriver?
nodriver (by the undetected-chromedriver author) drops Selenium and the chromedriver binary entirely and talks the Chrome DevTools Protocol directly, asynchronously. That removes the whole WebDriver detection surface and is fast and pleasant to use. It is AGPL-3.0, has about 4,800 GitHub stars and roughly 290,000 PyPI downloads a month; its latest release (0.50.5) came out in October 2026. A community fork, Zendriver, merges fixes faster and adds Docker support.
nodriver is a driver, not an engine. The Chrome it controls is stock, so native fingerprint values aren't changed, and every session on a machine shares that machine's identity. Driving a browser over CDP can still leave CDP-usage tells, depending on which domains a script enables, and there is no TLS or HTTP/2 control. AGPL-3.0 is also 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 | Your host's real values |
| TLS / network coherence | Follows the claimed Chrome (JA3/JA4 + HTTP/2) | Whatever the local Chrome sends |
| Interface | Playwright & Puppeteer + a standing CDP endpoint | Its own async CDP API (Python) |
| License | Open build BSD-3 | AGPL-3.0 (network copyleft) |
| Maintenance | Active | Latest release October 2026 |
| Cost | Open build free; latest build free with GitHub | Free & open |
Comparison compiled October 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 and HTTP/2 to the local Chrome. 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's open build is BSD-3.
Same CDP ergonomics, more surface
You keep a clean CDP-first workflow, plus Playwright and 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 the host's own fingerprint is acceptable.
- Or combine them: nodriver accepts a custom browser path, so it can drive the Clearcote binary.
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 keeps TLS/HTTP-2 coherent, 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 and chromedriver detection surface.
nodriver or Zendriver?
Zendriver is a community fork of nodriver with faster-merged fixes, typing and linting, and Docker support. The approach is the same; see the Zendriver comparison.
Is the AGPL license a concern?
For some. AGPL-3.0 is strong network copyleft, which some commercial and SaaS teams avoid. Clearcote's open build is BSD-3.
Related reading
Try the open-source Chromium alternative
Free and open source, a drop-in for Playwright & Puppeteer, coherent down to the TLS handshake.
Free for one browser with GitHub. No card.