Lyrion Music Server

Last reviewed Sep 13, 2026 · 798 words

Logitech stopped making Squeezebox hardware in 2012 and the server outlived it by a wide margin. Renamed Lyrion Music Server after Logitech handed the project fully to the community, it remains, in 2026, the most reliable way I know to play one library on six rooms in perfect sync from your own hardware. If synchronised multi-room playback of local files is the requirement, nothing else self-hosted does it as well. If you only want a Spotify-like app for your own MP3s on one device at a time, Navidrome is simpler and you can stop reading.

The players cost 20 dollars and you build them yourself

The trick to the whole ecosystem is that the server speaks a simple protocol, slimproto, on TCP port 3483, and free software players implement it. Squeezelite runs on anything: a Raspberry Pi with a 10 dollar DAC hat, an old laptop, a Docker container on the media box itself. piCorePlayer packages it as a bootable Pi image that also runs the server if you want. Squeezelite-ESP32 puts a player on a 5 dollar microcontroller with an I2S DAC. Original Squeezebox hardware from eBay still works and still sounds good.

Every player you add appears in the server, and any set of them can be synchronised. The server handles the clocking; the players buffer and start on cue. This is the feature people buy Sonos for, and here it costs the price of the hardware and an afternoon.

The stack is Perl, and the web UI shows its age

Lyrion is GPL-2.0, written in Perl, first released in 2002, with 1,770 GitHub stars at the time of writing on the slimserver repository. The Perl is not a problem for a user; the Docker image and the distro packages hide it. It is a problem for contributors, which is why the core moves slowly and the plugin ecosystem, which is also Perl, is where most new functionality appears.

The stock web interface looks like 2008 because it is. Install the Material Skin plugin on day one; it is a modern responsive interface that most people run as the only interface, and it works as an installed web app on phones. For control apps there are also third-party iOS and Android clients, and the Music Assistant project can drive Lyrion players from Home Assistant.

The container is small; the library scan is not

services:
  lms:
    image: lmscommunity/lyrionmusicserver:stable
    ports:
      - "9000:9000"
      - "9090:9090"
      - "3483:3483"
      - "3483:3483/udp"
    volumes:
      - ./lms-config:/config
      - /mnt/music:/music:ro
    restart: unless-stopped

Port 9000 is the web interface, 9090 the command-line interface that automation tools use, and 3483 is player discovery and control. If players cannot find the server, it is almost always because 3483 UDP is not reaching the host; network_mode: host fixes discovery on a flat LAN at the cost of tidiness. 256 MB of RAM is fine at idle. The first scan of a 50,000 track library takes an hour or more and uses noticeably more, so give it 1 GB while the scan runs and it will settle down afterwards.

Plugins carry the streaming services and the radio

Lyrion's plugin library is large and old, which means most things you want exist and some are abandoned. Internet radio and podcasts are built in. Qobuz, Tidal and Deezer have maintained plugins; Spotify support depends on third-party work that Spotify's API changes periodically break, so do not buy in expecting it to be stable. Local files, and anything with an open stream, are where the server is unconditionally reliable.

The comparison to the rest of the media server category is straightforward. Jellyfin and Navidrome are libraries you browse from a client on a phone; Lyrion is a control plane for physical players around the house. Snapcast does the sync part with any source and no library at all, and Music Assistant sits above all of them and can use Lyrion players as outputs. If you are starting fresh in 2026, Music Assistant plus Squeezelite players is a plausible modern route; Lyrion is the proven one.

What I'd do

For a house with three or more rooms and a local music library, I would run Lyrion in Docker with host networking, Material Skin installed, and a Squeezelite player per room on a Pi or an ESP32 board. I would keep Navidrome alongside for listening on the phone away from home, since Lyrion is built for players, not for a mobile library. It is a 24-year-old Perl codebase with a dated default UI, and it still does the multi-room job more reliably than anything newer. That is the whole recommendation.