What is Fluorite?

Fluorite is Chromium, rebuilt from a pristine source tree at a pinned upstream stable tag, carrying a small reviewed patch layer, compiled with the official release configuration, tested, and promoted as versioned artifacts. It is part of the AcreetionOS ecosystem.

The name comes from the mineral: fluorite crystals form in clean, ordered lattices and glow in bands of green, purple and blue — the same palette this site wears. Order plus color; discipline plus personality.

1. A fork is a pipeline, not a place

Most browser forks live in a long-lived git tree that slowly diverges from upstream until every rebase is a crisis. Fluorite has no precious tree. Every cycle the old tree and binaries are deleted outright and rebuilt from scratch at the newest stable tag. If the machine dies tomorrow, the entire project can be reconstructed from scripts plus one tag number.

2. Security is a schedule, not a scramble

Cycles run every 42 days by design. In between, an automated watcher compares the pinned milestone against upstream fixes weekly. Known vulnerabilities don't wait for the calendar — a detected milestone fix triggers an immediate rebuild instead of sitting until the next scheduled release.

3. Patches are guests, not residents

Modifications queue through a pending directory, get applied fresh onto every new base, and must justify themselves each cycle. Nothing hides in years of accumulated drift. This is where ideas inherited from the Bromite and Cromite line land — deliberately, visibly, reviewably.

4. Your data is yours — and outside the tree

User profiles must live outside the build directory (launch with a dedicated --user-data-dir). The build tree is disposable; your browsing life is not.

5. Honesty over marketing

This site documents what the pipeline actually does today. No roadmap theater, no fake checksums, no invented release dates. The tooling is real and inspectable.

Fluorite continues the work of two important ancestors: Bromite, csagan5's pioneering ad-blocking, privacy-hardened Chromium fork whose development ended around the Chromium 108 era, and Cromite, uazo's maintained revival of that work. Fluorite is a direct fork of Cromite, continued with a security- and stability-first mindset and an automated release pipeline. Read the full story on the lineage page.

The Bromite → Cromite → Fluorite story

• The Chromium project — for the enormous open codebase this all builds on.
• csagan5 (Bromite) — for proving engine-level ad blocking and hardening were worth doing.
• uazo (Cromite) — for refusing to let that research die. Fluorite exists because Cromite did.
• The AcreetionOS community — for hosting, testing and putting up with build-machine fan noise.