Free forever. Pro keeps it alive.

No. The free build has full engine-level fingerprint control and is reproducible from source — every identity surface is free in full: 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. Pro is a maintained build + support + patches 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. Pro is behavioural realism and earlier Chromium majors — not a paywall on core features.

No — this is the main Pro perk. A new Chromium major goes to Pro users the day it's built; the free build gets it roughly 2 months later. Chromium 151 (151.0.7922.108) is live for Pro right now, on Windows and Linux — pick it with the SDK via launch(version="151") or just let Pro default to the latest. Earlier majors stay selectable, so version="150" keeps working if you're pinned to it. The free build stays on 149 until the usual delay elapses. It's an incentive to support the project, not a way to hobble the free build: when a major lands for free, it's the same full open build.

No, and I won't pretend otherwise. 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 free build stays 100% open and reproducible.

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

While Clearcote Pro is in beta there's no concurrency cap — run as many instances as you like. Each running browser leases a slot from the license server and releases it on close; there's a live meter in your dashboard. We may introduce fair-use limits later, with notice.

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.