Roadmap

Built in the open.

A fully open, reproducible Chromium build with engine-level privacy/identity controls and a Playwright-compatible SDK — released with checksums and build attestation so anyone can confirm exactly what they're running. Dates are omitted on purpose: we ship milestones when they're verifiable, not before.

Shipped In progress Planned
Overall progress17/26 milestones

Shipping now

v0.1.0-pre.2 is live — Chromium 149, Windows x64

A signed, checksummed pre-release with engine identity controls and per-site farbling, plus Playwright-first SDKs on PyPI & npm. Passes a 6/6 CreepJS smoke check on real Windows — early and experimental, not yet fully stealth-validated.

Get the build
  1. 0

    Phase 0 · Foundations

    Shipped5/5

    The unglamorous groundwork that everything else depends on.

    • Project scope, principles, and architecture
    • De-Googled base via ungoogled-chromium, pinned to an exact upstream revision
    • Reproducible source-prep pipeline (fetch → prune → patch → verify)
    • Clean, automated build from source on a commodity machine
    • Published patch set — every change human-readable and individually documented
  2. 1

    Phase 1 · First public build

    Shipped4/4

    The moment you can download something and check it yourself.

    • Windows x64 build as the first target
    • Checksummed release artifacts (SHA-256) on GitHub Releases
    • Reproducible build instructions a third party can follow to a matching binary
    • One-command source bootstrap for contributors
  3. 2

    Phase 2 · Coherent identity controls

    In progress3/5

    Engine-level control over the signals a browser exposes — designed to be consistent, not random.

    • Per-profile, deterministic identity seed (stable across sessions, or fresh on demand)
    • Engine controls for canvas, WebGL, audio, fonts, locale/timezone, navigator & hardware
    • Per-site coherence (farbling-style): same site sees a stable identity; different sites don't correlate
    • WebRTC: report the proxy egress IP coherently instead of leaking or blocking
    • Sensible, documented defaults — privacy-respecting out of the box
  4. 3

    Phase 3 · Automation SDK

    In progress3/4

    Make it a true drop-in for the tools developers already use.

    • Python + Node SDKs (clearcote on PyPI + npm), Playwright-first, with verified auto-download
    • launch() returns a standard Playwright object — one-line migration
    • Auto-download + local cache of the verified binary
    • Recipes: persistent profiles, proxy configuration, headless on servers
  5. 4

    Phase 4 · Trust & supply-chain

    In progress2/4

    Raise the bar on verifiability beyond "here’s a checksum."

    • Signed releases — GPG detached signatures against a pinned key
    • SHA-256 checksums + a SHA256SUMS manifest for every release
    • Build provenance / attestation (Sigstore-style) for every release
    • CI that builds, checksums, and publishes in the open
  6. 5

    Phase 5 · Beyond

    Planned0/4

    Where it grows once the core is solid.

    • Additional platforms — Linux and macOS
    • A self-hostable profile manager for organizing identities and proxies
    • Integrations with common automation / agent frameworks
    • Hardening informed by open fingerprinting research
Get involved

How to follow along

This roadmap will evolve as the project does. Nothing here is a promise of a date — but everything is a promise of how we ship: in the open, and verifiable.

Watch the repo

Star and watch to get notified the moment a new build or milestone drops.

Open GitHub

Issues & ideas

Issues track concrete tasks; Discussions are for ideas and proposals.

Browse issues

Help build it

PRs welcome. The repo is laid out so humans and agents can navigate and contribute.

Contributing guide

Don't trust the roadmap. Verify the build.

Every milestone ships as a readable patch and a checksummed, signed artifact. Read the docs, read the patches, build it yourself.

Read the docs Roadmap source