A story in three browsers:
Bromite → Cromite → Fluorite
Fluorite is not a fresh idea invented in a vacuum. It is the current chapter of a direct line of hardened Chromium forks, and it only makes sense once you know what came before it — and why each project passed the torch.
Bromite (2017 – 2022): the original
Bromite, created by developer csagan5, was a landmark Chromium fork. Its pitch was simple and radical at the time: a Chromium browser with built-in ad blocking — no extensions required — plus meaningful privacy hardening patches on top.
What it proved
- A Chromium fork could strip out platform-level tracking surfaces and still track upstream closely.
- Ad blocking belonged in the browser engine layer, not in a fragile extension sandbox.
- A small, focused patch set maintained against fast-moving Chromium releases was sustainable — for a while.
What happened to it
Bromite's development slowed through 2022 and effectively stopped around the Chromium 108 era (late 2022 / early 2023). Releases ceased, the issue tracker went quiet, and the patch set froze while Google shipped new Chromium milestones every four weeks. An unpatched browser fork ages quickly from "hardened" to "risky", so users were left with a choice: run a frozen build, or move on.
The lesson: a fork is not a product you ship once. Without an industrial process behind it, even the best patch stack rots against upstream.
Cromite (2023 – ): the revival
In late 2023, developer uazo launched Cromite, explicitly described as "a Bromite fork". Its stated purpose was to make sure csagan5's research work would not be lost: resurrect the patch stack, restore maintenance, and resume regular releases across Android, Windows and Linux.
Cromite's goals, straight from its own documentation
- Limit the features built into the browser that can be used as a platform for tracking users' habits — disable them or leave the choice to the user.
- Limit close integration between the browser and its manufacturer.
- Not let the research done by csagan5 with Bromite be lost.
- Collaborate with other non-profit open source browsers and push mature improvements upstream into Chromium itself.
Cromite succeeded at its core mission: Bromite's approach lives again in a maintained browser with continuous releases. But it also demonstrated something else — keeping a long-lived fork tree healthy against upstream takes enormous ongoing effort, and that effort competes directly with time spent improving the patches themselves.
The lesson: reviving the patches is half the problem. The other half is the machine that keeps producing rebuilt, tested, up-to-date binaries week after week.
Fluorite (now): the continuation
Fluorite is a fork of Cromite. It starts from uazo's codebase and patch stack, maintained within the AcreetionOS ecosystem with one change in emphasis: a security- and stability-first mindset. Where upstream must balance many platforms and priorities, this fork doubles down on the discipline that keeps a browser safe over time — pinned tags, clean trees, automated weekly security response, and gates before anything ships:
| Bromite | Cromite | Fluorite | |
|---|---|---|---|
| Era | 2017–2022 | 2023– | today |
| Author | csagan5 | uazo | AcreetionOS project, forking uazo's Cromite |
| Approach | Patch stack + releases | Maintained Bromite fork | Cromite fork, pipeline-produced builds |
| Priority | Ad blocking + hardening | Balanced continuation | Security & stability first |
| Base strategy | Track upstream | Track upstream | Pinned tags, 42-day cycles |
| Security response | Manual | Manual | Automated weekly watch |
| Fate | Unmaintained (~Chromium 108) | Active | Active |
What was inherited
- From Bromite: the conviction that hardening belongs in the engine, that defaults matter more than options, and that csagan5's original patch ideas remain worth studying. They are exactly the kind of work the patch layer carries.
- From Cromite (the actual codebase): the tree Fluorite forks, uazo's restored maintenance of Bromite's research, and its collaborative, upstream-friendly attitude.
- Fluorite's own contribution: release engineering. A clean tree every cycle, pinned stable tags, a discrete pending-review patch queue, official-config optimized builds, a test gate before promotion, and a containerized weekly security watcher that rebuilds mid-cycle when upstream ships a fix.
In one sentence: Bromite wrote the ideas, Cromite kept them alive, and Fluorite forks that living work to continue it — rebuilt by an automated pipeline where nothing ships until it proves itself.