There is a corner of the home audio world that did not die when Logitech stopped making Squeezebox hardware. The software that drove those little networked speakers now lives on GitHub at lyrion/lms-community, renamed Lyrion Music Server. It still streams to Squeezebox devices, still talks to software players like Squeezelite, and still has the multi-room sync and plugin model that made the original worth buying in 2008.
For anyone who set up a Squeezebox back when WiFi audio was a novelty, this is welcome news. The community picked up the project and it has not lost its edge.
What Lyrion actually does
Lyrion Music Server runs on Linux, macOS, Windows, a Raspberry Pi, or most NAS devices (network-attached storage boxes from Synology, QNAP, Asustor, and friends). It indexes a local music collection, streams to compatible players over the network, pulls in internet radio, and exposes a browser-based UI for control. The server itself is a Perl program, which dates the codebase but also explains why it still runs on hardware most people consider obsolete.
The feature list is longer than most modern streaming services:
- Local library playback. Index FLAC, MP3, OGG, and friends, with album art and metadata.
- Multi-room sync. Run several players in different rooms, group them, ungroup them on the fly.
- Plugin architecture. Plugins add streaming services (Spotify, Tidal, Qobuz), smarter transcoding, visualizers, and new metadata sources.
- Web UI and native apps. Control from any browser, the Orange Squeeze mobile app, or one of several third-party controllers.
- Internet radio. Direct support for streams, plus plugins that pull in podcast-style sources.
The licensed GPL v2 release ships everything you need. The server is the only process you install; players connect over the local network.
Why anyone still cares
Subscribe to a streaming service and buy a Sonos or Echo. For most people that is the right answer. Lyrion exists for two specific cases that the consumer market does not cover well.
FLAC collectors are the first case. Lossless audio is meaningful to a slice of listeners with the gear to hear the difference, and the streaming services that offer lossless still charge a premium and rotate their catalogs. A self-hosted Lyrion server backed by a multi-terabyte drive is the answer that does not depend on a monthly fee or licensing terms.
Squeezebox owners are the second case. Many of them already have the hardware from the original 2008-era WiFi speaker line, the first consumer WiFi speaker worth using. Logitech stopped making them in 2012, but the speakers do not stop working. Lyrion keeps the network functional, which is its own argument.
Installation in practice
The shortest path on a Linux box is the Debian or Fedora package from the project download page. On a Raspberry Pi, the same packages work with no special effort. On macOS, the disk image installs Lyrion as a regular application and adds a menubar item. On a NAS, the package feed the NAS vendor provides (Synology and QNAP both have community packages) is usually the cleanest path.
A working setup looks like this. The server runs on a machine with the music library attached, either internal storage or a mounted drive. Players connect over the network. The browser UI on any device on the same network controls everything. Mobile apps connect over the local network when you are home and over a VPN (virtual private network, an encrypted tunnel back to your home network) when you are not.
Performance is not a concern. A Raspberry Pi 4 streams to a dozen players without breaking a sweat. The bottleneck is your network, not the server.
A few practical notes from real setups. First, point Lyrion at the music library as a symbolic link (a filesystem pointer that makes one path appear at another location) rather than copying the files into the Lyrion data directory. Second, give the server a static DHCP lease (a reserved IP address that your router hands out to the same machine every time) so the mobile apps can find it without manual reconfiguration. Third, enable LMS’s “Save playlist on server” if you have multiple players, since each player otherwise stores its own version of the playlist and they drift.
When Lyrion is not the answer
Lyrion does not solve the “I want my mom to use this” problem. The setup is a Saturday afternoon, not an afternoon in the sense that she could do it. Sonos or Bluesound or WiiM is the right pick if the user is not technical and the household does not want to manage a Linux box.
The other limit is streaming-service integration. Plugins exist for the major services, but they depend on each service’s API (application programming interface, the documented way outside software talks to a service) staying open and unchanged. Spotify’s API has been stable for years. Tidal and Qobuz are similar. Smaller services come and go. If your household’s only music source is one of the smaller streaming platforms, check the plugin status before you commit.
The Perl codebase is also a real consideration. The project is healthy, but a Perl developer shortage is real and the contributor pool is small. The community is not at risk of vanishing, but it is at risk of moving slowly when a major dependency breaks.
Trade-offs
Lyrion Music Server is free and open source, but it is not free in time. Setting it up on a Raspberry Pi with an external drive takes a few hours the first time, plus another hour of fiddling when your music collection has weird metadata or your network has an unusual layout. Migrating from an existing Squeezebox setup is faster because the same plugins and clients still work. Migrating from Sonos is a full re-setup, since Sonos does not interoperate.
The multi-room sync is the killer feature. Sonos invented it for consumers and charges a premium for it. Lyrion has it for free, with the catch that you have to bring your own speakers and amplifiers. Squeezelite on a Raspberry Pi Zero wired to an amp and bookshelf speakers is the cheapest path to the same result.
Updates to the server are infrequent. The community ships releases when something important changes, not on a marketing calendar. If you want weekly new features, look elsewhere. The flip side is that the moving parts are stable; once you have a working setup, it tends to keep working through upgrades without surprises.
In our case, the trade-off favors Lyrion for any household with a NAS and a technical owner. The setup is real work, but the running costs are zero and the local-library control is total.
What I would tell past me
- Start with the Raspberry Pi image. It is the cleanest single-shot setup and you can migrate to a bigger box later without losing your library index.
- Buy a FLAC-friendly player client. Squeezelite on a Raspberry Pi Zero is the cheapest path; iPeng or Orange Squeeze on mobile for control.
- Test your network first. Most multi-room sync headaches are WiFi issues, not server issues. Wired players and a wired backhaul are worth the effort.