Does Zeno.FM Work on Alexa? Every Streaming Platform Compared

Yes — Zeno.FM works on Alexa, and so does every other major streaming platform, with one condition: the station can produce an HTTPS stream in MP3, AAC, or HLS. That's the entire compatibility question. Amazon certifies streams, not brands — there is no approved-vendor list, no partnership requirement, no platform that's locked out and none that's preferred. The platforms differ only in how much work it takes you to satisfy those two conditions.

Here's each platform, and what it actually takes — drawn from real submissions, not the features pages.

Zeno.FM — Easiest in Class

Zeno serves HTTPS HLS by default on every station, which means a Zeno station can go to Alexa with zero stream changes. Of all the platforms we handle, Zeno consistently requires the least preparation: the URL is secure, the format is supported, and the answer to "what needs to change" is "nothing."

Shoutcast — Works, SSL Depends on Your Host

Shoutcast streams MP3 and AAC, both fully supported. The catch is older v1-era setups, which often serve plain HTTP. Shoutcast v2 handles this better, and most managed Shoutcast hosts offer an SSL port or proxy on request — usually free, usually within a day. Once the URL starts with https://, a Shoutcast station is fully Alexa-ready.

Icecast — Works, Mind the OGG Habit

Icecast has the same SSL story as Shoutcast, plus one trap that bites more often: Icecast's flexibility means many stations run OGG Vorbis or Opus mounts — the codecs Alexa doesn't support. A stream that plays perfectly in VLC and every desktop player can be completely silent on an Echo. The fix is adding an MP3 or AAC mount and pointing the skill at that.

Radio.co — Clean by Default

Radio.co built their platform modern: HTTPS HLS as the default, which makes Alexa submission essentially zero-work. In our experience Radio.co stations pass stream checks on the first look, essentially every time.

Live365 — Works, With a Note

Live365 serves secure AAC/HLS that passes certification cleanly. One thing worth knowing: Live365 already pushes stations into some smart speaker ecosystems through their own integrations — but those surface Live365's apps, not your brand. A custom skill still gives you the direct voice command and your own Skills Store listing.

AzuraCast — Works, You're the Sysadmin

Self-hosted AzuraCast passes like anything else once it's behind proper HTTPS — typically a reverse proxy (nginx or Caddy) with a Let's Encrypt certificate on port 443, serving an MP3 or AAC mount. AzuraCast's panel SSL covers the web interface, not necessarily the stream port, so verify the actual stream URL, not the dashboard. If your AzuraCast URL has a port number in it, that's the thing to check.

The One-Paragraph Summary

• Zeno.FM: HTTPS HLS default — ready as-is
• Radio.co: HTTPS HLS default — ready as-is
• Live365: secure AAC/HLS — ready as-is
• Shoutcast: works — get the SSL port from your host if needed
• Icecast: works — same SSL story, plus add an MP3/AAC mount if you're on OGG
• AzuraCast: works — you configure HTTPS yourself (reverse proxy + Let's Encrypt)

Switching Platforms Later

Your skill doesn't care where the stream lives. When you move hosts, the skill's endpoint gets updated to the new URL — same invocation name, same store listing, same listeners and reviews. Nothing is rebuilt. This is why free lifetime stream updates is a term worth insisting on when you choose who builds your skill: platform migrations happen to every station eventually, and they should never cost extra.