The Vinyl Cache Project¶
What is Vinyl Cache?
Vinyl Cache (formerly known as “Varnish Cache”) is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. Vinyl Cache is really, really fast. It typically speeds up delivery with a factor of 300-1000×, depending on your architecture.
What is happening¶
Vinyl Cache has a new identity¶
Read more about our new logo and wordmark: The Vinyl Cache Project has a New Identity
Name-change in progress¶
We are still the process changing the project name to Vinyl Cache, so dont be confused if you see Vinyl/Varnish being mixed up for a while. Varnish Software is going to continue to maintain a project called Varnish Cache.
Vinyl Cache has left github: your action is required¶
If you want to continue to interact with us, you need to take action.
Please read Vinyl Cache has left github for more.
Announcing VCOT: OpenTelemetry Instrumentation for Vinyl-Cache¶
We’re happy to announce to have opened the repository of VCOT (VinylCacheOpenTelemetry), a brand new open-source (GPL) Go utility designed to enhance observability in Vinyl-Cache (and, for the time being, Varnish-Cache) environments through an integration with OpenTelemetry.
Up until now Vinyl-Cache was able to produce highly-detailed logs and provide precise insight into the cache behavior, but it was not able to integrate with modern observability standards.
VCOT addresses the need for modern monitoring in high-performance systems by parsing Varnish Shared Logs (VSL) in real-time and exporting telemetry data - traces, metrics, and logs - to OpenTelemetry-compatible backends.
This is just the beginning, VCOT is destined to evolve based on users’ feedback. Please open issue and/or PRs if you wish to see this tool improve.
Vinyl Cache - Logo and Mascot Contest¶
The logo contest is closed and winners have been selected. We missed our target timeline to make the respective announcement in December 2025, but it will be made eventually.
2025-09-15 - New release: 8.0.0 with bonus project news¶
We have a new major release today: 8.0.0, and some major project news for you.
20 years old and it is time to get serious(er)¶
This coming february 22nd, The Varnish Cache Project will officially be 20 years old. And we will change the name of the project.
Read the full post: 20 years old and it is time to get serious(er)
2025-08-20 - New releases: 7.7.3, 7.6.5 and 6.0.16¶
There are new releases available, 7.7.3, 7.6.5 and 6.0.16. These address a regression from the handling of VSV00017.
2025-08-13 - Varnish HTTP/2 Made You Reset Attack¶
2025-08-13 - Security release 7.7.2¶
Varnish version 7.7.2 is now available. This release addresses the vulnerability described in VSV00017.
2025-08-13 - Security release 7.6.4¶
Varnish version 7.6.4 is now available. This release addresses the vulnerability described in VSV00017.
2025-08-13 - Security release 6.0.15¶
Varnish version 6.0.15 is now available. This release addresses the vulnerability described in VSV00017.
2025-05-12 - Security release 7.7.1¶
Varnish versions 7.7.1 is now available. This release addresses the vulnerability described in VSV00016.
2025-05-12 - Request Smuggling Attack¶
Please see VSV00016 Request Smuggling Attack.
2025-05-12 - Security release 7.6.3¶
Varnish versions 7.6.3 is now available. This release addresses the vulnerability described in VSV00016.
2025-05-12 - Security release 6.0.14¶
Varnish versions 6.0.14 is now available. This release addresses the vulnerability described in VSV00016.
2025-03-17 - Varnish 7.7.0 is released¶
Our bi-annual “fresh” release is here: Varnish Cache 7.7.0
The 7.5 series is no longer supported in any capacity.
2025-03-17 - Varnish HTTP/1 client-side desync vulnerability¶
Please see VSV00015 Varnish HTTP/1 client-side desync vulnerability.
2025-03-17 - Security release 7.6.2¶
Varnish versions 7.6.2 is now available. This release addresses the vulnerability described in VSV00015.
Privacy¶
You can access the varnish-cache homepages with HTTP or HTTPS as you like.
We save the logfiles from our Varnish instance for a limited period, in order to be able to debug problems.
We do not use any external trackers and do not analyze traffic.
