A Cromite fork · continuing Bromite's line

Hardened Chromium.
Built on a clock.

Fluorite is a hardened Chromium fork of Cromite, rebuilt by a fully scripted pipeline: a clean source tree, a pinned stable tag, a patch layer, an optimized build, a test gate — every six weeks, without fail. Security milestones are tracked weekly in between. Same lineage as Bromite and Cromite; security and stability first.

Get Fluorite The Bromite story
154.0.8021.1Current base tag
42 daysRelease cycle
7×/weekSecurity watch
100%Scripted pipeline

What makes it different

Predictable LTS cadence

Every 42 days the old tree and binaries are thrown away and a fresh cycle begins from the newest upstream stable tag. No drift, no snowballing state — just a reproducible browser, on schedule.

Weekly security watch

A containerized watcher runs weekly against the pinned milestone. When a relevant security fix lands upstream, it files a report, stages the update and kicks the pipeline — automatically.

Layered patches

All modifications live as discrete patches in a dedicated layer, applied fresh onto every new base. Patches queue through pending/, so nothing silently rots inside a fork.

Optimized official builds

Release configuration uses Chromium's official-build path: component build off, symbols trimmed, release optimizations on. What ships is what would ship.

Test gate before promote

Every build passes its suite before promotion. Binaries only land in the dist tree once they've proven themselves against the tagged base they were compiled from.

Clean-tree discipline

User data lives outside the build tree entirely. Each cycle starts from zero, which means every artifact can be traced back to exactly one tag and one patch set.

All features in detail →

Where it comes from

Fluorite didn't appear out of nowhere. It stands on a decade of browser-fork work:

  • Bromite — csagan5's landmark Chromium fork proved a browser could ship with built-in ad blocking and real privacy hardening. Its development eventually stalled around the Chromium 108 era, leaving its patch set frozen against a fast-moving upstream.
  • Cromite — uazo forked Bromite explicitly so csagan5's research wouldn't be lost, restoring maintenance, rebuilding the patch stack and shipping regular releases again.
  • Fluorite — a direct fork of Cromite, continuing that living codebase with a security/stability-first mindset: fresh tree, pinned tag, layered patches, tested artifacts, weekly security tracking.

Read the full lineage

The pipeline

  1. PinResolve the newest stable tag from upstream and pin the cycle to it.
  2. SyncFresh checkout of Chromium at the tag with all dependency repos in parallel streams.
  3. PatchApply the Fluorite patch layer on top of the pristine tree.
  4. BuildCompile with the official release configuration.
  5. TestRun the post-build test suite. Failures stop the line.
  6. PromoteCopy the blessed artifacts into dist/<version>/.
$ ./fetch-chromium.sh && ./fluorite-release.sh FORCE_CYCLE=1

Full pipeline documentation →

Get Fluorite

154.0.8021.1 latest promoted base

Binaries, checksums and per-cycle archives live on the download server. Launch with a dedicated profile directory — your data should live outside the build tree, just like ours does.

Open Downloads Install guide