Clearcote

A Chromium build with fingerprint control compiled into the engine, plus SDKs for Python, Node and .NET. Run it on your own machines, or use our hosted browsers: it is the same engine either way.

The open build is: BSD-3-Clause, every patch human-readable, reproducible from source. The latest build (free with GitHub, and Pro) adds work that is not published, so it cannot be rebuilt from public source.

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.

Up to 250 browsers at once, 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.

Windows x64 and Linux x64. On macOS, launch() runs the Clearcote Docker image through Docker Desktop (SDK 0.40.0+).

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.

The same licensed build Pro gets — the newest Chromium, recorded human motion, the private stealth patches, the profile library — free for one browser at a time. Free always runs the latest build; choosing an older build or the preview channel is a Pro feature. Sign in with a GitHub account that is at least 30 days old, open Licenses in your dashboard and click Get it free. The key lasts 30 days and renews for free from the same page. It needs SDK 0.30.0 or newer (pip install -U clearcote, npm install clearcote@latest, or the latest NuGet package). One claim per GitHub account.

Two things: running more than one browser at a time (up to 250 at once, on any number of machines), and email support from me, the owner. The build is identical. If you only ever run one browser at a time, Free with GitHub gives you everything the build does.

No. The open build has full engine-level fingerprint control and is reproducible from source — every identity surface is in it: Seeded identities — same seed, same browser; different seed, unlinkable, Full engine-level fingerprint control, Individual metadata overrides — screen, memory, pixel ratio, GPU and more, Light-stealth preset for targets that need a lighter touch, TLS fingerprint matched to the browser version you present, Proxy support with automatic timezone and language matching. The licensed build adds things that do not spoof anything new: humanized input driven by real recorded human motion, higher-fidelity pointer reporting, webrtc reports your proxy's address, not your machine's, local network addresses stay private over webrtc, request-header handling tuned for repeat visits, plus new Chromium majors first. All of that is free with a GitHub account for one browser.

No. A new Chromium major goes to the licensed build — Free with GitHub and Pro — the day it's built; the open build gets it roughly 2 months later. Pick a major with the SDK, for example launch(version="152"), or leave it out to get the latest your key allows. Earlier majors stay selectable. When a major lands in the open build, it's the same full open build.