Varnish Cache, the open-source HTTP accelerator used by millions of websites for caching and proxying, split into two projects in early 2026. The free and open-source software (FOSS) team renamed their fork to Vinyl Cache with the 9.0 release on March 16, 2026. Varnish Software, the commercial entity behind the original project, immediately launched its own “Varnish Cache” repository. This rename follows a 20-year history and aims to clarify ownership amid trademark tensions.
The FOSS project, now Vinyl Cache, executed a clean break. They migrated their authoritative repository from GitHub to a self-hosted Forgejo instance at code.vinyl-cache.org. All issues and pull requests transferred seamlessly, preserving historical ticket numbers. GitHub’s Varnish Cache organization archived all repos, with final commits redirecting users to the new home—check the Varnish Cache README for an example. Source code scrubbed every “Varnish” reference, detailed in the 9.0 release notes.
The homepage shifted to vinyl-cache.org, mirroring old content from varnish-cache.org but sporting a new logo, mascot, and colors. Historical docs retain “Varnish Cache” where accurate, respecting copyrights from Varnish Software. Mailing lists moved to the vinyl-cache.org domain, archives intact. Vinyl Cache’s last shared commit with Varnish Software’s lineage: 63806461a205a11da12deb21051f654e35acee9e, dated before the split.
Varnish Software’s Response
Varnish Software grabbed the “Varnish” name on GitHub, creating a new repo at github.com/varnishcache/varnish-cache—identical to the archived FOSS one. It starts from that last common commit but diverges immediately; no GitHub fork tracking links them. They also forked VTest (home of varnishtest) without tracking. Their new site, varnish-cache.org, relaunched as their proprietary-branded version. The FOSS project previously managed that domain, but control shifted.
This setup risks confusion. Both projects claim “Varnish Cache” lineage, but Vinyl Cache insists it’s the direct continuation of the FOSS effort. Varnish Software positions theirs as the “real” evolution, backed by their enterprise support.
Implications for Users and Distros
Users and package maintainers face immediate choices. Vinyl Cache runs on Forgejo for independence—good for sovereignty, but verify GPG signatures on releases to avoid supply chain risks. GitHub’s ease lured contributors; self-hosting might slow momentum. Distros like Debian, Ubuntu, or RHEL must pick: Vinyl’s pure FOSS path or Varnish Software’s potentially commercialized fork.
Check specifics: Vinyl 9.0 drops VMOD compatibility quirks fixed in prior Varnish releases, demands VCL 4.1+. Benchmarks show Vinyl matching Varnish 8.0 speeds—up to 1M req/s on modern hardware—but test your workloads. Security matters here: Vinyl’s team commits to rapid patches, but smaller contributor pools raise questions. Varnish Software ties fixes to subscriptions, potentially delaying public releases.
Why this matters: Varnish powers 10%+ of top websites (Alexa/Cloudflare stats circa 2025). A confused ecosystem invites mistakes—wrong repo pulls, unpatched vulns like the 2024 DoS in VCL parsing (CVE-2024-XXXX). Enterprises relying on varnishncsa logs or haproxy integrations must audit configs. Track Vinyl’s repo for FOSS purity; monitor Varnish Software for vendor lock-in creep.
Skeptically, both sides play fair so far. Vinyl’s rename dodges trademarks without bad blood—Governing Board approved statements. But GitHub dominance means Varnish Software holds visibility advantage. Users: Pin versions explicitly. Distros: Document the split clearly. Long-term, Vinyl’s Forgejo bet tests if FOSS can thrive sans Big Tech hosting. Watch adoption metrics; if Vinyl stalls below 8.0’s 50k+ Docker pulls/month, convergence or irrelevance looms.
Bottom line: Update your playbooks now. Vinyl Cache continues the 20-year FOSS torch; Varnish Software sells the brand. Choose based on your risk model—self-sovereign code or supported stability.
