ESR stability, frozen in ice
Cryolite rides the Firefox Extended Support Release: the branch Mozilla itself considers stable enough for enterprises. Fewer surprises, longer support windows, security fixes without churn.
Cryolite is a hardened GNU IceCat fork — Firefox ESR with the GNU freedom layer, rebuilt by a fully scripted pipeline: a clean source tree, a pinned ESR tag, a scripted rebrand, a patch layer, an optimized build, a smoke gate — every six weeks, without fail. ESR security advisories are watched weekly in between. The Chromium side of the family is Fluorite; this is its Gecko twin.
Cryolite rides the Firefox Extended Support Release: the branch Mozilla itself considers stable enough for enterprises. Fewer surprises, longer support windows, security fixes without churn.
Inherited from IceCat: only free software licenses for built-in extensions, LibreJS to detect non-free JavaScript, and trademark-safe rebranding. Your browser respects you and the four freedoms.
The mechanical IceCat→Cryolite pass is one audited script, exactly like upstream's own makeicecat. Everything else lives as discrete patches in a reviewable layer.
Official-build configuration: optimizations on, debug symbols trimmed, updater and crash reporter off. What ships is a browser, not a development snapshot.
Every build must introduce itself (--version) and render a page headlessly before it earns a place in the dist tree. Binaries only land once they've proven themselves.
Profiles live outside the build tree entirely. Each cycle starts from zero: every artifact traces back to exactly one ESR tag and one patch set.
Cryolite didn't appear out of nowhere. It stands on decades of browser work:
makeicecat pipeline since 2008: free licenses only, LibreJS, privacy defaults, no trademark strings.vX.Y.Z-gnuN tag from the gnuzilla repository and pin the cycle to it.makeicecat: Firefox ESR sourceball, GPG-verified, GNU patches and freedom layer applied../mach build.dist/bin into cryolite/dist/<version>/.$ ./fetch-icecat.sh && ./cryolite-release.sh FORCE_CYCLE=1
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.