The questions that actually get asked.
Because upstream's cadence is release-driven, not pipeline-driven. Cryolite adds what IceCat doesn't promise: a fixed 42-day clean-rebuild cycle, a pinned-tag guarantee, a smoke gate, and weekly automated ESR tracking with automatic respins. Same freedoms, stricter clock.
It's Firefox ESR → GNU IceCat (freedom layer, source-level privacy) → Cryolite (pipeline, patch layer, release discipline). Three distinct layers, all documented on this site.
Engine and lineage. Fluorite forks Cromite (Chromium, Bromite's line); Cryolite forks GNU IceCat (Gecko, Firefox's free line). The pipeline philosophy — clean trees, pinned tags, layered patches, weekly watch — is identical. AcreetionOS ships both.
Nowhere inside the browser — the updater is compiled out. You get a new build from the downloads site each cycle or respin, like a package manager expects. This is a feature: the browser can't mutate itself behind your back.
It's Fluorite's cadence, inherited for family coherence. Firefox ESR security releases land roughly monthly; the weekly watch covers anything that can't wait for the scheduled cycle.
Profiles are compatible (same Gecko generation), but the clean-tree discipline is the point: launch with a dedicated --profile directory. Migrate deliberately, not by default.
No. The pipeline targets linux/x86_64 — the same platform AcreetionOS ships. The scripts are portable in principle; patches may need platform work.
Yes, and you should — that's the point of a scripted fork. See Developers. One command pulls everything; one command builds, tests and promotes.