Vinyl Cache and VaaS Console
Vinyl Cache is an open-source web application accelerator and caching HTTP reverse proxy, available in the NetActuate Marketplace as a one-click appliance. It sits in front of an origin (a web app, API, or media packager), serves hot content from memory, and greatly speeds up delivery. Cache policy is written in VCL, its flexible configuration language, so cache keys, TTLs, header normalization, purging, and per-route rules are all under your control. This listing packages Vinyl Cache with the Allegro VaaS web console. It is free and open source, and is grouped under the Media & Streaming and Networking & Security categories.
What It Does
Vinyl Cache accelerates HTTP delivery by caching origin responses in memory and serving them to clients without repeatedly hitting the origin. Common uses include:
- Caching and accelerating web and API responses in front of an origin
- Serving media segments and manifests close to viewers to reduce origin load
- Normalizing headers, rewriting cache keys, and applying per-route TTLs with VCL
- Purging and invalidating cached content on demand
Running it in a NetActuate PoP near your users keeps cache hits local and low-latency, and shields your origin from repeated requests.
Vendor and Project
Vinyl Cache is an open-source project (BSD licensed), packaged here with the Allegro VaaS web console (Apache 2.0). It is offered under the Open Source partner listing with best-effort community support.
- Project home: vinyl-cache.org
NetActuate supports the underlying infrastructure. Application-level support follows the listing's SLA class (open-source, best effort).
Sizing
| vCPU | RAM | Disk | |
|---|---|---|---|
| Minimum | 2 | 4 GB | 40 GB |
| Recommended | 8 | 32 GB | 200 GB |
No VPU (hardware acceleration) is required for this appliance. Because the cache is held in memory, size RAM to the working set of content you want to keep hot.
Configuration Fields
When you deploy, you provide these fields. They are written into the appliance at first boot. Secret fields are stored write-only in your account.
| Field | Required | Default | Notes |
|---|---|---|---|
| Origin host | Yes | none | Hostname or IPv4 of the origin the cache accelerates |
| Origin port | No | 80 | TCP port on the origin |
| Cache size (MB) | No | 1024 | In-memory (malloc) cache size in MB, minimum 64 |
| VaaS console user | No | admin | Username for the VaaS web console superuser |
| VaaS console password | No | generated | Password for the VaaS web console. Left blank, one is generated and stored write-only in your secret list |
Using the Appliance
After the build completes:
- Connect over SSH as the
ubuntuuser with the password or SSH key you set at deploy. - Open the Allegro VaaS web console at
http://YOUR_VM_IP:3030/and sign in with the console user and password you supplied. - The cache is configured to accelerate the origin host and port you provided at deploy. Manage VCL, cache policy, and purging from the console.
FAQ
Is there a software license fee? No. Vinyl Cache is open source and free to run. You pay only for the NetActuate infrastructure and bandwidth.
Where is the console?
The Allegro VaaS web console runs on port 3030.
How much cache memory should I allocate? Set the cache size to hold your hot working set. The default is 1024 MB and the minimum is 64 MB; size RAM accordingly.
Version and Changelog
| Version | Status | Released |
|---|---|---|
| 1.0.0 | Current (default) | 2026-07-09 |
Deploy
- Deploy in the portal: Deploy Vinyl Cache
- View the listing: portal.netactuate.com/platform/marketplace/l/vinyl-cache
- Public listing: netactuate.com/marketplace/vinyl-cache
Need Help?
Contact support@netactuate.com or open a support ticket from the portal.