Blend in.
Stay clear.
Clearcote is an open-source, de-Googled Chromium with fingerprint control built into the engine — one coherent, plausible identity instead of an accidentally unique one. A drop-in for Playwright & Puppeteer.
Free & open source (BSD-3) · on npm & PyPI · no phone-home · every change is a readable patch.
$ pip install clearcote
from clearcote import launch
# one coherent identity from a single seed
browser = launch(fingerprint="acct-1", geoip=True)
page = browser.new_page()
page.goto("https://abrahamjuliot.github.io/creepjs")
# navigator.webdriver = false · one real machine · 0% detectedBuilt on & works with
Chromium base
CreepJS checks passed
Trackers & phone-home
Built for builders
Engine-level controls with the ergonomics you already know.
Engine-level, not script injection
Identity controls are compiled into the binary — not bolted on via injected JavaScript that's brittle and self-revealing. Pages see native behavior, not a patched DOM.
Coherent per-site identity
Signals are controlled together so they stay consistent and stable per site — inspired by Brave's farbling.
Drop-in automation
Native Playwright & Puppeteer support. Same APIs — just point them at the Clearcote binary.
De-Googled base
ungoogled-chromium removes Google services, telemetry and integration. Privacy by default.
Tunable fingerprint flags
Seed, platform, brand, GPU, hardware concurrency, timezone, geolocation — all command-line switches.
A drop-in for your stack
Your existing automation, pointed at Clearcote, hitting any site or fingerprint check.
Signals it controls
A thin, transparent stack
Nothing hidden — de-Googling, identity controls, and a build you can run end-to-end yourself.
Chromium
The real engine and ecosystem.
ungoogled
Google services & telemetry removed.
Clearcote patches
Engine-level identity controls.
Reproducible build
Pinned, checksummed, signed.
Browser + SDK
Playwright / Puppeteer drop-in.
Migration is a one-line import
Already using Playwright or Puppeteer? Same objects, same methods.
from clearcote import launch
browser = launch(fingerprint="seed-123", platform="windows")
page = browser.new_page()
page.goto("https://abrahamjuliot.github.io/creepjs/")
browser.close()Why Clearcote instead of the others?
Most anti-detect browsers are closed, paid binaries that rewrite your fingerprint with injected JavaScript or CDP hooks — brittle, self-revealing, and asking you to trust code you can't read. Clearcote inverts every one of those choices.
| Clearcote | Typical anti-detect browser | |
|---|---|---|
| Source | ✓100% open — every change is a readable patch | Closed binary |
| Price | ✓Free (Pro optional) | Paid subscription |
| How signals change | ✓Compiled into the C++ engine — invisible to the page | Injected JS / CDP hooks (detectable artifacts) |
| Coherence | ✓One seed → a whole consistent machine; JS identity and the real TLS/JA3/JA4 + HTTP-2 stack agree | Per-surface values that disagree — with each other or the network |
| Trust model | ✓Signed, checksummed, reproducible from source | “Trust us” |
| Automation | ✓Drop-in Playwright / Puppeteer — returns a standard Browser | Proprietary API / GUI profiles |
| Real identities | ✓Import a real machine and verify it loaded | Rare / unverifiable |
| Privacy | ✓De-Googled, zero telemetry / phone-home | Varies |
The deeper reason it holds up: how bot detection actually works.
Free forever. Pro keeps it alive.
The free build is fully functional and reproducible from source — it is not crippled to sell you Pro. Pro funds the upkeep and gets you a maintained build plus a direct line to the person who makes it.
Free
$0
Open source, forever.
- 100% open source (BSD-3-Clause)
- Reproducible & verifiable from source
- All public patches — full fingerprint control
- Windows + Linux builds
- New Chromium majors land ~2 months after release (Pro gets them first)
- Community support via GitHub issues
Pro
Supports development$49/month
Billed monthly in USD. Cancel anytime.
Everything in Free, plus:
- Latest builds first. A new Chromium major (e.g. 150) is available to you the day it ships — the free build gets it later, roughly 2 months after release.
- The maintained, always-current build — latest Chromium and the newest anti-detection patches, kept up to date for you.
- A few extra stealth patches I keep private so they aren't trivially copied. Being blunt: this build is therefore not reproducible from public source — the free build is.
- Unlimited concurrency — while in beta. No cap today; fair-use limits may come later, with notice.
- Direct email support from me, the owner. You email, I answer.
Straight talk about what you're paying for.
Clearcote is a Chromium fork. Keeping it current with upstream, porting the anti-detection work to every new version, testing it, and building for two platforms is a lot of ongoing effort — mostly mine. $49/month pays for that. You get a build that stays up to date without you lifting a finger, a handful of patches I don't publish, and a direct line to the person who builds it. That's the whole deal — no lock-in, no dark patterns, and the free build stays open and reproducible.
Don't trust us. Verify us.
Every release is checksummed and GPG-signed against a pinned key. Import it, confirm the fingerprint, check the signature — then run a binary you proved is exactly what was built.
Pinned signing key
CA96F185 F96A 693A EDB3 AC1F CB00 D851 B7A8 6B0F
Inspiration & credits
Clearcote is an independent project, grateful to the open-source work it builds on.
Chromium
BSD-3-ClauseThe engine.
ungoogled-chromium
BSD-3-ClauseThe de-Googled base and patch tooling.
fingerprint-chromium
BSD-3-ClausePioneering engine-level fingerprint controls (by adryfish).
Brave
InspirationThe per-site deterministic 'farbling' model.
Camoufox
InspirationA sibling open anti-detect browser (Firefox-based).
Questions, answered
Is it really open source?
Yes — BSD-3-Clause. Every patch is human-readable and the free build is reproducible from source.
What do I actually get with Pro ($49/mo)?
A maintained, always-current build (latest Chromium + newest anti-detection patches), a few extra stealth patches I keep private, unlimited concurrency while in beta (fair-use limits may come later, with notice), and direct email support from me, the owner. Being blunt: it mostly funds the ongoing upkeep. The free build is fully functional and not crippled to sell Pro.
Is the Pro build reproducible too?
No — and I won't pretend otherwise. Pro includes a few patches I don't publish, so it can't be rebuilt from public source. The free build stays 100% open and reproducible; that promise doesn't change.
How is this different from JS stealth plugins?
Those overwrite navigator properties with injected JavaScript, which is brittle and self-revealing. Clearcote changes the C++ engine, so values come from Chromium's own code paths.
Does it phone home or auto-update?
The browser does not phone home or auto-update. The SDK can download the verified archive from GitHub Releases on first use, and auto-update is opt-in.
Which platforms are supported?
Windows x64 today. More platforms are on the roadmap.
Can I keep my existing Playwright/Puppeteer code?
Yes — point executablePath at the Clearcote binary. It's a drop-in browser.
More in the full FAQ.
Go deeper
Documentation
Install, the SDKs, fingerprint flags, deployment and verification.
Research
Deep-dives on bot detection, fingerprinting and how the browser is built.
Q&A & concept map
Plain-English answers and a connected map of every stealth concept.
Alternatives
How Clearcote compares with other anti-detect browsers and stealth tools.
Run a browser you can read.
Read the docs, read the patches, build it yourself. The whole point is that you never have to take our word for it.