Free to start. Pro when you run many.

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.

No, and I won't pretend otherwise. The licensed build (Free with GitHub and Pro) includes work I don't publish — see the table above for what that covers — so it can't be rebuilt from public source. The open build stays 100% open and reproducible.

You email me, the owner, and I answer — build questions, detection issues, integration help. Not a ticket queue.

Each running browser leases a slot from the license server and releases it when it closes; there's a live meter in your dashboard. Free with GitHub has one slot, so a second browser is refused until the first one closes (a browser that crashed frees its slot within 6 minutes). Pro covers up to 250 browsers at once, on as many machines as you like. Need more than that? Ask — we raise it per account. Subscriptions started before 26 September 2026 keep their previous uncapped terms.

The same Pro, billed once a year instead of monthly: $441 for 12 months instead of $588 — 3 months free, $147 off, $36.75/month effective. Nothing about the build, the concurrency, or the support changes; you're paying up front and I'm passing back a quarter of the price for the runway. Switch either way from the billing portal in your dashboard — Stripe pro-rates the change, so moving to yearly mid-month credits what you've already paid.

Yes. A 30-day pass is $49, paid once — same build, same private patches, same concurrency, same direct support. The only difference is that it ends on its own instead of renewing, so there is no subscription and nothing to cancel. Buy another one whenever you want more time and it adds to the license you already have: your existing key keeps working, nothing to redeploy. There's a second reason it exists — Stripe can only charge a subset of payment methods on a recurring basis, so subscribing shows most people a card field and not much else. Paying once lets you use PayPal, Apple Pay or Amazon Pay instead.

Anytime, from the billing portal in your dashboard. You keep access until the end of the period. A one-off pass has nothing to cancel — it simply stops at its end date.