Turn Spotify playback into a stable HTTP / Icecast stream for Roon, LMS (Lyrion), Volumio and network players.
Restore the radio-style endpoint your audiophile stack is missing.
Many audio stacks break at the exact place that should be the simplest: the reusable source endpoint.
DACs are fine.
Renderers are fine.
Network players are fine.
What often disappears is the stable HTTP radio URL you can point everything to.
Spotycast solves that gap by republishing Spotify playback to Icecast, so your stack gets one resilient LAN stream endpoint that can be consumed almost anywhere.
It is especially useful when you want:
- Spotify with Roon
- Spotify to Icecast
- a headless Spotify Connect endpoint on Debian
- a single HTTP stream URL for mixed players
- a practical workaround for Spotify in ecosystems that do not integrate it natively
Spotify → PulseAudio → Liquidsoap → Icecast → Roon / LMS / Volumio / Players
Stable path
Spotify Connect or app upstream, one reusable stream downstream.
Single URL
One Icecast mountpoint for the whole LAN stack.
LAN friendly
Works like a radio endpoint that many players already understand.
-
Spotify with Roon
https://spotycast.ovh/spotify-with-roon/ -
Spotify to Icecast
https://spotycast.ovh/spotify-to-icecast/ -
Installation guide
https://spotycast.ovh/how-to-install/ -
How it works
https://spotycast.ovh/how-it-works/ -
Spotify Lossless with Roon
https://spotycast.ovh/spotify-lossless-roon/
Spotycast republishes Spotify playback as a standard HTTP audio stream:
Spotify → PulseAudio → Liquidsoap → Icecast → Player
That means you stop depending on native Spotify support on every playback device.
Instead, you expose one stable radio-style endpoint on your LAN and feed it to:
- Roon
- LMS / Lyrion Music Server
- Volumio
- hardware streamers
- embedded players
- any device that accepts a radio URL or HTTP stream
This is why Spotycast is useful in heterogeneous audio environments: old devices, mixed ecosystems, abandoned firmware, single-zone DACs, or setups that simply work better with one canonical stream source.
If you searched for Spotify with Roon, Spotify in Roon, Roon Spotify workaround, or Spotify lossless Roon, this repository is probably relevant.
Roon still does not provide native Spotify integration, so many users end up needing an external bridge.
Spotycast does not make Spotify natively appear inside Roon.
What it does is often more practical in real-world systems:
- create an HTTP stream endpoint
- make that stream stable and reusable
- let Roon consume it as a radio source
- keep your downstream playback topology consistent
That makes Spotycast a good fit when the goal is not theoretical purity but operational reliability in a real network audio stack.
Read more:
Spotycast is centered around the same downstream idea:
publish one reliable Icecast / HTTP endpoint for the rest of the system
This path uses spotifyd and focuses on simplicity and robustness.
Use it when you want:
- headless deployment
- Debian-friendly setup
- Spotify Connect behavior
- predictable operation
- a stable lossy path up to Spotify’s standard quality ceiling
This path is for more advanced scenarios where the objective is to preserve as much quality and control as possible in systems where native options are limited or missing.
Use it when your priority is:
- higher-quality workflows
- more advanced automation
- stronger control over the bridge behavior
- working around ecosystem limitations in legacy or hybrid environments
Details:
A radio-style endpoint is valuable because it is:
- simple
- portable
- inspectable
- compatible with many players
- decoupled from app-specific integrations
When your whole system can consume one HTTP stream, your stack becomes easier to reason about and easier to keep stable over time.
That is the core idea behind Spotycast:
not “Spotify everywhere natively”
but “one reusable endpoint everywhere reliably”
Spotify Connect or Spotify app
PulseAudio + Liquidsoap
Icecast mount / HTTP stream
Roon / LMS / Volumio / network players
- Spotify provides the source playback
- PulseAudio captures or routes the audio
- Liquidsoap republishes it
- Icecast exposes the resulting mountpoint
- your playback clients consume the stream like a standard radio source
Architecture page:
docker compose up -dThen inside the container:
cd /root/binaries
./spotifyd-freeOpen Icecast in your browser:
http://<HOST>:28000
Copy the relevant mountpoint URL and add it as a radio stream in your player.
Full installation walkthrough:
You want a simple, stable HTTP stream exposed from Spotify playback.
Read:
You want Roon to consume Spotify through a stable endpoint.
Read:
You have multiple players, some modern, some old, some native, some not.
A single Icecast mountpoint simplifies everything.
You want a self-hosted, LAN-local audio bridge that behaves like infrastructure rather than a consumer app.
Spotycast is intentionally a bridge, not a claim of native ecosystem integration.
Important points:
- it is not a native Spotify integration inside Roon
- it is not a strict bit-perfect DAC path
- it introduces a republishing layer
- it depends on Spotify playback behavior upstream
- it adds normal stream-style buffering and latency
That trade-off is explicit:
- you give up strict theoretical purity
- you gain a stable network-wide endpoint
For many practical systems, that is the better engineering compromise.
More context:
Use Spotycast if:
- you use Roon but want Spotify as a source
- you need Spotify over HTTP
- your devices accept radio URLs more easily than apps
- your firmware ecosystem is fragmented or aging
- you want one stable stream URL for your whole stack
- you prefer infrastructure-style audio plumbing over app-specific integrations
Do not use Spotycast if:
- you need strict bit-perfect output directly to a DAC
- you already have a native workflow that fully satisfies your needs
- you only listen from one local desktop app and do not need a reusable endpoint
No. Spotycast does not create native Spotify integration inside Roon.
It exposes Spotify playback as an HTTP stream that Roon can consume.
No. It is a republishing bridge, not a strict bit-perfect transport chain.
Yes. The whole idea is to expose a standard HTTP / Icecast stream that LMS-compatible players can consume.
It helps create a usable bridge workflow, but it is not the same thing as native lossless Spotify integration inside Roon.
Because Icecast gives you a standard, reusable, inspectable HTTP endpoint that many devices already understand.
- https://spotycast.ovh/
- https://spotycast.ovh/spotify-with-roon/
- https://spotycast.ovh/spotify-to-icecast/
- https://spotycast.ovh/how-it-works/
- https://spotycast.ovh/how-to-install/
- https://spotycast.ovh/spotify-lossless-roon/
- https://spotycast.ovh/faq/
- https://spotycast.ovh/version-premium/
If you want to maximize discovery on GitHub, these are strong candidate topics for this repo:
spotify
spotify-connect
spotifyd
icecast
liquidsoap
roon
lms
lyrion
volumio
http-stream
internet-radio
self-hosted
docker
docker-compose
debian
network-audio
headless-audio
spotify-lossless
spotify-bridge
icecast-stream
MIT — see LICENSE.
Spotycast
Bring back the stable HTTP radio endpoint in your audiophile network stack.