Docker-based audio bridge

Using Spotify as a Network Audio Source

Spotycast exposes Spotify playback as a standard HTTP / Icecast stream on your local network. Reuse the same playback chain (DAC / amp / speakers) with Roon, LMS/Lyrion, network players, or anything that can play a web radio URL.

Headless Spotify Connect endpoint Icecast mountpoints LAN-only by design Works with Roon/LMS as “Radio URL”
Already installed? Jump to FAQ or How it works.

How it works

Spotycast provides a headless Spotify Connect endpoint on the host, captures the audio output, and publishes it as a clean network stream (Icecast-style). Existing players then consume Spotify as a standard network source — without requiring native Spotify Connect support on the playback device.

Design goal: keep a predictable playback path in mixed setups by exposing a “radio URL”. Installation path: How to install.

Typical use cases

Reuse one DAC

Keep a single high-quality playback chain for Spotify and other sources (local files, network audio, etc.).

Add Spotify to Roon / LMS

Consume Spotycast like any other HTTP radio stream (Roon, LMS/Lyrion, network players).

Avoid extra devices

No need to add a dedicated Spotify Connect box just to feed your existing ecosystem.

Predictable audio path

Maintain stable behavior in mixed networks where discovery and platform changes can be disruptive.

LAN-first

Designed for private networks. The goal is local playback, not public broadcasting.

Self-hostable

Docker-based deployment on your VM/host, with a clean “bridge” mindset.

Audio quality and expectations

Audio quality depends on the playback path used. Open Spotify Connect implementations are typically limited to Spotify’s “Very High” quality (often up to ~320 kbps). Spotycast also provides an optional setup designed to expose the stream as FLAC over HTTP. When Spotify’s lossless tier is available for the account/region and enabled, this approach is intended to avoid unnecessary transcoding at the bridge level.

This is not a blanket claim that playback is always lossless; availability depends on Spotify and client behavior. Premium details: Spotycast Premium.

Two editions

Free

Stable lossy stream (MP3/AAC)

Standard installation, reliable and simple.

  • Up to ~320 kbps (depending on client behavior)
  • Great for day-to-day listening
  • Fast setup, minimal assumptions
Premium

Lossless + convenience features

For users who want the cleanest path and more operational comfort.

  • FLAC over HTTP support (where Spotify lossless is available)
  • Update / rollback support
  • Premium key required to install

What this is not

Not an official Spotify client

It doesn’t replace Spotify’s official apps; it exposes playback externally as a stream.

Not deep library integration

Metadata/features depend on the consuming player (Roon/LMS/web radios).

Not a public broadcast tool

Designed for private LAN playback — not redistribution over the internet.

Background and motivation

Integrating Spotify Connect into high-end or legacy streaming devices can be difficult, especially as Spotify evolves its client stack over time. Some older integrations are no longer maintained, and user setups can also be affected by network discovery behavior (for example, environments where mDNS support varies). Spotycast aims to reduce the moving parts by exposing a stable stream interface.

Frequently asked questions

Can Spotify be used with Roon or LMS/Lyrion?

Spotify is not natively supported by Roon or LMS/Lyrion. Spotycast exposes Spotify playback as a standard network audio source (HTTP stream) that these systems can consume, typically as a “Radio URL”.

Is Spotycast a replacement for Spotify Connect?

No. Spotycast uses Spotify playback and exposes the audio externally rather than replacing Spotify Connect.

Is this a public broadcast?

No. Spotycast is designed for local playback within a private network (LAN) and is not intended for public redistribution. If you’re curious about the boundaries, the FAQ goes deeper.

For advanced troubleshooting and networking topics, see FAQ and How it runs.