Blend in.
Stay clear.
One coherent, plausible identity — not an accidentally unique one. Fingerprint control compiled into the engine, not injected. An open-source, de-Googled Chromium that drops into Playwright & Puppeteer.
Open source (BSD-3) · Chromium 153 · Windows & Linux · no card needed.
What a page reads
same script · two binaries
- navigator.
webdriver truefalse - UA-CH ↔ platformThe host OSThe persona's OS
- canvas · WebGL · audioSame on every hostUnique per seed
- timezone · localeThe server'sThe persona's
Illustrative.
Run the fingerprint testSet in the engine, not patched on top
Values come from Chromium's own code paths
No injected JavaScript to inspect. The main thread, workers and iframes agree because they all run the same patched engine.
- Chromiumupstream
- ungoogledde-Googled
- Clearcote patchesreadable
- Reproducible buildsigned
- Browser + SDKships
Signals it controls
A drop-in for your stack
Your existing automation, pointed at a different binary.
from clearcote import launch
browser = launch(fingerprint="acct-1", platform="windows")
page = browser.new_page()
page.goto("https://abrahamjuliot.github.io/creepjs/")
browser.close()One browser, four ways to use it
Scraping & data pipelines
SDK & Docker endpoint
launch() from Python, Node or .NET, or a standing CDP endpoint in Docker that any client can attach to.
Deployment docsQA & cross-device testing
Captured device profiles
Reproduce a real machine from a captured profile, and verify every value applied.
Browse the profilesAI agents
MCP server
Claude Desktop, Cursor or Cline drive one shared browser with a fixed identity.
MCP docsPersistent identities, by hand
Profile Manager
A Windows app to create and launch persistent identities. No code.
About the appBuilt for privacy, testing, research and lawful automation. Use is subject to local law and site terms — see our terms.
Where the fingerprint actually changes
Most tools work around the engine. Clearcote changes it.
Where signals change
- Clearcote: In the C++ engine — every realm agrees
- Closed anti-detect browsers: In the engine
- Driver patches: Driver only; the engine reports stock values
- JS stealth plugins: JavaScript injected into each page
Source you can read
- Clearcote: Every change is a readable patch
- Closed anti-detect browsers: Closed binary
- Driver patches: Open source
- JS stealth plugins: Open source
Reproducible, signed builds
- Clearcote: Checksummed and GPG-signed, rebuildable from source
- Closed anti-detect browsers: Prebuilt download you take on trust
- Driver patches: n/a — drives your stock Chrome
- JS stealth plugins: n/a — runs inside your stock Chrome
Network layer
- Clearcote: TLS and HTTP/2 follow the claimed Chrome version
- Closed anti-detect browsers: Varies; vendor-reported
- Driver patches: Stock automation signature
- JS stealth plugins: Stock automation signature
Price
- Clearcote: Free; Pro for many browsers at once
- Closed anti-detect browsers: Subscription, usually per profile
- Driver patches: Free
- JS stealth plugins: Free
Tool-by-tool comparisons: alternatives.
Free to start. Pro when you run many.
One browser at a time is free. Pro is for running many at once, and pays for keeping a Chromium fork current — the same build, no extra spoofing, no lock-in.
Free
One browser at a time$0 · no card
With GitHubNew
The latest Chromium the day it ships, with the private stealth patches.
From sourceNo account
Open source (BSD-3) and reproducible. New majors about 2 months later.
With GitHub needs an account at least 30 days old and SDK 0.30.0 or newer.
Pro
Supports development- As many browsers at once as you need, on any number of machines — no cap while in beta.
- Everything in Free with GitHub, plus older builds, version pinning and the preview channel.
- Direct email support from me, the owner.
Billed monthly in USD. Cancel anytime.
Don't trust us. Verify us.
Every release is checksummed and GPG-signed against a pinned key, so you can prove the binary is what was built.
How to verify a releasePinned signing key
CA96F185 F96A 693A EDB3 AC1F CB00 D851 B7A8 6B0F
Questions, answered
Is it really open source?
Yes — BSD-3-Clause. Every patch is human-readable and the open build is reproducible from source.
Can I get the latest build for free?
Yes, for one browser at a time. Sign in with a GitHub account at least 30 days old and click Get it free under Licenses. It is the same licensed build Pro gets, on a key that renews every 30 days. Needs SDK 0.30.0 or newer.
What does Pro ($49/month) add?
As many browsers at once as you need, on any number of machines, plus direct email support from the owner. Same build as Free with GitHub; nothing in Pro unlocks more fingerprint control.
Is the licensed build reproducible too?
No. It includes unpublished work, so it cannot be rebuilt from public source. The open build stays fully open and reproducible.
Which platforms are supported?
Windows x64 and Linux x64. macOS is on the roadmap.
What is it for, and is that allowed?
It is a browser, built for privacy, testing, research and lawful automation. Whether a specific use is permitted depends on your local law and the terms of the sites you visit, and that is your responsibility. We make no claims about any particular detection product.
More in the full FAQ.
Start with one browser, free.
Install the SDK, sign in with GitHub, keep your existing scripts.
pip install clearcote · npm i clearcote · dotnet add package Clearcote
