Icecast alternative
Replace the whole Icecast stack.
Not just the relay.
Icecast is a solid relay — but a station running on it also runs a source client, an AutoDJ, one encoder per mount, an audio processor and stats tooling around it. Pulse Broadcast is all of those in one production-proven container, deployed at licensed FM stations serving over a thousand concurrent listeners.
Component by component
What Pulse replaces in a typical Icecast installation.
Before / after
The same station, with and without the glue.
Typical Icecast setup
- Icecast server relaying pre-encoded mounts
- Liquidsoap or IceS as source client and AutoDJ
- Separate encoder process for every format and bitrate
- Audio processing in a separate box or not at all
- Stats from XML snapshots and log parsing
- Every piece configured, updated and restarted separately
The same station on Pulse
- One container: ingest, failover, DSP, encoding, delivery, analytics
- Studio feed as uncompressed PCM over RTP or an Icecast source
- AutoDJ and silence generator already running underneath
- Every output encoded from one processed master
- Persistent web admin — no config files, no restart-to-change
- ~400 MB RAM at 1,000+ concurrent listeners in production
Side by side
Pulse Broadcast vs Icecast.
| Capability | Pulse Broadcast | Icecast |
|---|---|---|
| Role | Complete head-end | Relay only |
| Audio processing | EQ + loudness + limiter | None |
| Multi-format, one source | MP3 + AAC + Opus | One encoded source per mount |
| Automatic failover | Built-in AutoDJ + silence | External tooling (Liquidsoap) |
| HLS delivery | Built in | No |
| Historical analytics | Built in | XML snapshot only |
| Configuration | Persistent web admin | XML files + restart |
| Deployment | One Docker container | Icecast + source client + encoders + stats |
Migration
Moving off Icecast, step by step.
01
Inventory the current setup
Mounts, codecs, bitrates, source encoder and where listeners connect from.
02
Run Pulse in parallel
Same stream paths and bitrates, on a hosted trial instance or your own server.
03
Point the studio at Pulse
Your existing encoder connects as an Icecast source, or a broadcast encoder sends clean PCM over RTP.
04
Cut over the domain
Switch DNS or the reverse proxy. Listeners reconnect once and land on Pulse with the same URLs.
Honest scope
When Icecast is still the right choice.
- You only relay streams that are already encoded elsewhere and want nothing else on the server.
- You operate a federation of relays where Icecast’s relay ecosystem is the point.
- You need free, open-source software as a hard requirement rather than a complete operated product.
Questions from Icecast operators
Frequently asked.
Does Pulse accept my existing Icecast source encoder?
Yes. Pulse accepts standard Icecast source connections, so encoders like BUTT, Mixxx and hardware units keep working. For the cleanest results it also accepts uncompressed PCM over RTP from broadcast encoders such as Barix and DEVA, so the server encodes from the original studio audio.
Do my listeners have to change anything?
No. Stream paths are fully configurable, so existing URLs like /stream or /stream.mp3 keep working, and players still receive ICY now-playing metadata exactly as they do from Icecast.
Can we migrate without downtime?
Yes. Pulse runs alongside your current Icecast while you verify outputs, then you switch the domain or reverse proxy. Listeners experience a single reconnect at cutover, not an outage — and AutoDJ failover protects the stream from then on.
Is Pulse open source like Icecast?
No. Pulse Broadcast is a commercial product built and operated by the team behind it, with a free two-month hosted trial so you can verify everything against your real station before committing.
What does it need to run?
One Linux server with Docker. In production Pulse serves 1,000+ concurrent listeners across three simultaneous codecs, with DSP and analytics, in roughly 400 MB of RAM.
Try Pulse next to your Icecast.Two months, hosted by us, with your real studio audio — and help wiring it in.