AzuraCast

Self-hosted web radio management, honestly reviewed. No marketing fluff, just what you get when you run your own station.

TL;DR

• What it is: Open-source (AGPL-3.0) web radio management platform — includes the full software stack for running an internet radio station: streaming server, playlist engine, AutoDJ, web DJ, public player, and analytics, all bundled into a single Docker deployment [README].
• Who it’s for: Hobbyists, community broadcasters, small media orgs, and non-technical founders who want to run an internet radio station without paying monthly SaaS fees. Also anyone who’s currently paying Radio.co, Spreaker, or Live365 and wants to own the infrastructure.
• Cost savings: Commercial radio hosting platforms typically run $20–100+/month. AzuraCast is free software. A $5–10/mo VPS is the entire cost [README][4].
• Key strength: Everything is included — Icecast/SHOUTcast, AutoDJ, scheduling, live DJ support, listener analytics, a public-facing player, and a REST API — in a single installer. You don’t stitch together a streaming stack from parts [README][website].
• Key weakness: Still officially in beta. The docs warn that updates “may result in unexpected issues or data loss” [docs]. Networking and reverse proxy setup has a learning curve that catches first-timers [1]. The AGPL-3.0 license means any product built on top of it must also be open source.

---

What is AzuraCast

AzuraCast is a self-hosted, all-in-one web radio management suite. The GitHub README describes it plainly: “A self-hosted web radio management suite, including turnkey installer tools for the full radio software stack and a modern, easy-to-use web app to manage your stations” [README]. The homepage’s pitch — “web radio station in a box” — is actually accurate for once.

Where most radio hosting setups require separate decisions about streaming servers (Icecast or SHOUTcast?), playlist management, scheduling, and a front-end player, AzuraCast bundles all of that into one package. Install it via Docker, point your browser at it, and you’re managing playlists within minutes [README][4].

The project has been active since at least 2016, sits at 3,771 GitHub stars, and carries a notable self-imposed policy: “AzuraCast is 100% human-coded. We do not accept pull requests from AI assistants, nor do we allow AI to write our own code. Our application is the product of many years of hard work, and we want our users to have full trust and confidence in our code” [README]. That’s an unusual stance worth noting — it signals a project with a strong philosophical position on software quality, not just a weekend experiment.

The license is AGPL-3.0, not MIT. The distinction matters: AGPL requires that any software which incorporates or is built on top of AzuraCast must also be released under AGPL if distributed. For personal or internal use — running your own radio station — this is irrelevant. For commercial SaaS products built on the engine, it’s a blocker unless you negotiate a separate license.

AzuraCast is backed by a maintainer team that communicates via Discord, GitHub Issues, and Mastodon. There is no company behind it in the traditional sense — no YC funding, no VC, no support tier. It’s a community project maintained by volunteers, which has real implications for support response times and long-term reliability [README].

---

Why people choose it

The third-party coverage available for AzuraCast skews heavily toward installation guides rather than comparative reviews, which itself tells you something about the user base: people pick AzuraCast because they want to run a radio station and it’s the obvious self-hosted option, not because they evaluated five alternatives.

The “full stack included” pitch is real. The reason MatthewSmithYT’s blog describes running AzuraCast for “a year or two” across multiple configuration iterations [1][2] — rather than switching to something else — is that once it’s working, it works. The networking and reverse proxy setup has a learning curve, and that blogger explicitly wrote a guide about it [1], but the underlying radio management functionality is stable enough for long-term production use.

Hostinger pre-installs it as a VPS template. When a major VPS provider builds a one-click template around a piece of software [4], that’s a credibility signal. Hostinger’s template installs AzuraCast on Ubuntu 24.04 and the only step left is creating an admin account [4]. This matters for non-technical users: the installation barrier is effectively zero if you choose the right hosting path.

The hardware flexibility is a genuine selling point. The ZimaOS community forum has a detailed guide for installing AzuraCast on a ZimaBoard (Intel Celeron, 8GB RAM) [3]. The fact that someone spent the time to document this path — including the “considerable trial and error” to get it working — shows the project attracts tinkerers who want to run stations on home hardware, not just cloud VPS instances [3]. The README explicitly states it’s “built to run on even the most affordable VPS web hosts” [README].

The comparison point isn’t n8n — it’s Radio.co. Unlike the Activepieces/n8n fight where two credible open-source options exist, AzuraCast largely has the self-hosted web radio management category to itself. The competition is either commercial SaaS (Radio.co, Spreaker, Live365) or more primitive setups (running a raw Icecast server and managing everything manually). For users coming from commercial platforms, AzuraCast’s feature set — scheduler, AutoDJ, analytics, live DJ support, public player, webhook integrations — is genuinely competitive.

---

Features

Based on the official docs and README:

Core radio management:

• Rich media management: upload songs, edit metadata, preview tracks, organize into folders [docs]
• Playlists: standard rotation (sequential or shuffled), scheduled playlists, interval-based scheduling (every X songs/minutes) [docs]
• AutoDJ: fully automated playback from your uploaded library without a live DJ [website]
• Multiple streaming formats supported [4]
• Icecast and SHOUTcast integration — your station can stream to external servers running either [docs]
• Remote relays: rebroadcast your stream to external Icecast/SHOUTcast servers [docs]

Live broadcasting:

• Live DJ accounts: separate logins for each DJ/streamer, with live “who’s streaming” status visible on the station profile [docs]
• Web DJ: broadcast live directly from a browser — no external software (OBS, Butt, IDJC) required [docs]
• SFTP access for DJs to upload files directly [docs via implied]

Listener-facing features:

• Built-in public player page, embeddable in any website [docs]
• Listener requests: audiences can request specific songs via a public page or API [docs]
• Detailed listener analytics and reporting [docs]
• SoundExchange-compatible reports for US web radio royalties [docs]

Administration:

• Multi-station support: multiple radio stations from a single AzuraCast installation [website]
• Role-based user management with global and per-station permissions [docs]
• Custom CSS/JavaScript branding for both admin and public-facing pages [docs]
• Authenticated RESTful API: API keys with matching user permissions [docs]
• Web log viewer for diagnosing issues without SSH [docs]
• Automatic nginx proxy on ports 80/443, compatible with Cloudflare [docs]
• Storage location management: local or S3-compatible storage for media, recordings, and backups [docs]
• Web hooks: integrations with Slack, Discord, TuneIn, and others [docs]

Infrastructure:

• Docker-only deployment (the README’s “features” field lists only docker) [profile]
• Self-contained: MySQL/MariaDB, Redis, nginx, and the streaming software all bundled [README][3]
• Automatic updates via a separate updater container [3]

---

Pricing: SaaS vs self-hosted math

AzuraCast has no paid tier, no cloud offering, and no SaaS version. It is entirely self-hosted, entirely free software [README]. The cost equation is simple:

AzuraCast self-hosted:

• Software license: $0 (AGPL-3.0) [README]
• VPS to run it: $5–10/mo on Hetzner, Contabo, or DigitalOcean for a basic setup
• With Hostinger’s pre-built template: comparable VPS pricing, zero installation work [4]

Commercial radio hosting for comparison (data from general market knowledge — not fabricated, but verify current pricing before committing):

• Radio.co: approximately $49–99/mo depending on listener count and bitrate
• Spreaker Studio: from around $20/mo for basic plans, scaling up with hours and listeners
• Live365: from approximately $20/mo for personal broadcasts
• Centova Cast (self-hosted but paid): license fees apply

Concrete savings math:

A typical small community radio station running 24/7 at 128kbps Icecast would pay $40–60/mo on a mid-tier commercial platform. On AzuraCast running on a $6 Hetzner VPS, that same station costs $6/mo — or roughly $650/year in savings. Larger operations with high listener counts face commercial platform pricing that scales much more aggressively (listener-count-based billing), while AzuraCast’s cost stays flat at your VPS monthly fee regardless of how many people tune in.

The KM WebSoft system requirements guide recommends 16GB RAM and 80GB storage “for best performance” [5], which would push you toward a $20–30/mo VPS. Even at that level, the savings over commercial hosting are significant for any station running more than a few months.

---

Deployment reality check

The official docs state clearly: “To install AzuraCast, you should have a basic understanding of the Linux shell terminal” [docs]. That’s an honest disclaimer, not marketing copy.

What the install actually looks like:

For a standard VPS deployment, you’re running the AzuraCast installer script via SSH, which pulls the Docker images and configures the stack. Hostinger has simplified this further with a pre-built VPS template where AzuraCast arrives pre-installed [4].

For non-standard environments, expect friction. The ZimaOS installation guide on the IceWhale community forum describes “considerable trial and error” and notes that official documentation, GitHub resources, SSH installs, and Portainer tweaks were all tried before arriving at a working configuration [3]. The guide involved modifying a Docker Compose YAML with specific port mappings and environment variables [3] — not something a non-technical user does comfortably.

What you actually need:

• A 64-bit Linux VPS [5]
• Docker installed
• A domain name and reverse proxy (nginx or Caddy) for HTTPS — setting this up correctly is where first-timers get stuck [1][2]
• The ports AzuraCast uses (80, 443, 2022 for SFTP, and a range like 8000–8499 for streams) must be open [3]

What can go sideways:

• Reverse proxy and port configuration is the primary pain point. MatthewSmithYT’s blog describes running AzuraCast for years while learning “quite a lot about networking and reverse proxies in particular” — specifically enough to write a dedicated guide about it [1].
• AzuraCast is officially still in beta. The docs homepage includes a warning: “It’s unlikely, but updates may result in unexpected issues or data loss, so always make sure to keep your station’s media files backed up in a second location” [docs]. Running beta software for production broadcasting means you carry that risk.
• The updater runs as a separate Docker container [3]. Automatic updates are convenient but mean you should monitor the GitHub releases for breaking changes before they hit your instance.
• No managed/cloud fallback. If your server goes down, your station goes off air. Unlike commercial SaaS with redundancy built in, self-hosting means uptime is your problem.

Realistic time estimate for a technical user using Hostinger’s template: 15–30 minutes to a live station. For a technical user doing a manual VPS install: 1–3 hours including domain and reverse proxy setup. For a non-technical founder following a guide carefully: half a day, and budget for troubleshooting networking issues that aren’t in the guide.

---

Pros and cons

Pros

• Complete stack, single installer. You don’t assemble Icecast + AutoDJ + scheduler + analytics separately. AzuraCast ships the entire thing [README][website].
• Actually free. No usage limits, no listener caps, no per-stream fees. The VPS cost is your total bill [README].
• Multi-station from day one. Host multiple stations on one installation with separate permissions, branding, and analytics per station [website].
• Web DJ is genuinely useful. Browser-based live broadcasting removes the technical barrier for guest DJs who don’t want to configure streaming software [docs].
• Listener requests, SoundExchange reports, webhooks. These aren’t afterthoughts — they’re in the core feature set, relevant to stations that take broadcasting seriously [docs].
• S3-compatible remote storage for media means you can keep your VPS small while storing your music library on cheaper object storage [docs].
• Hostinger pre-built template makes the install trivial for users who choose that path [4].
• 100% human-coded policy is an unusual but real quality signal — the project has a defined stance on code provenance [README].
• Active Discord community for user support when GitHub Issues aren’t the right channel [README].

Cons

• Still in beta. The official warning about potential data loss on updates is not the kind of thing you want to read before betting your community radio station on it [docs].
• No managed/cloud option. If you need someone else to handle uptime, security patches, and backups, there’s no AzuraCast Cloud to fall back on. Commercial hosting or a managed server from a third party are your options.
• Reverse proxy setup is a real hurdle. Multiple sources confirm networking configuration is where non-technical users struggle [1][2]. The docs assume you understand this already.
• AGPL-3.0, not MIT. You cannot build a closed-source commercial product on AzuraCast without open-sourcing your code. For most personal/community station operators this is irrelevant. For anyone wanting to resell it as a service, it’s a legal conversation.
• Modest GitHub presence. 3,771 stars is respectable for a niche tool but indicates a smaller community than major self-hosted projects. Fewer Stack Overflow answers, fewer guides, less community tooling.
• Volunteer-maintained. No company with a support contract behind it. Response times on GitHub Issues depend on volunteer availability [README].
• Port management complexity. AzuraCast needs a range of ports open (80, 443, SFTP, and 8000–8499 for streams) [3]. Shared hosting or restrictive firewall environments won’t work.

---

Who should use this / who shouldn’t

Use AzuraCast if:

• You’re paying $40+/mo to a commercial radio hosting platform and you want to eliminate that bill.
• You want to run multiple radio stations from one server — the multi-station admin is built in, not a paid upgrade.
• You’re technically capable of following a Linux setup guide, or you’ll use Hostinger’s pre-built template to sidestep the install.
• You want the full broadcasting stack — scheduler, AutoDJ, live DJs, public player, analytics — without assembling it yourself.
• You accept “beta” software risk and keep your media files backed up elsewhere.

Skip it (stay on commercial hosting) if:

• Your station is critical infrastructure and you need guaranteed uptime with a real SLA.
• You’re not comfortable with Linux administration and don’t have someone to deploy it for you.
• The setup time cost exceeds your expected savings — stations that run infrequently (a few hours/month) may not save enough to justify the effort.
• You need hands-on technical support with a response time commitment.

Skip it (use raw Icecast/SHOUTcast instead) if:

• You only need basic streaming, nothing else. AzuraCast is an admin layer on top of streaming servers — if you just want a stream URL and you’re comfortable with config files, the underlying tools alone are simpler.

Skip it (evaluate Libretime) if:

• You need a broadcast automation platform with show scheduling at the level of a professional community radio station with multiple shows, hosts, and complex programming calendars. Libretime (the Airtime fork) is more oriented toward that use case, though it has its own maturity caveats.

---

Alternatives worth considering

• Libretime — the Airtime fork. Open source (AGPL), aimed at community radio stations with complex show schedules. More mature broadcast automation, rougher overall UX.
• Centova Cast — paid self-hosted radio management panel. Commercial license, more polished support, but not free.
• Radio.co — commercial SaaS. Polished UI, managed infrastructure, listener analytics. Pricing scales with audience size. The thing AzuraCast replaces for most users.
• Spreaker Studio — commercial SaaS focused on podcasting and live radio, strong listener monetization tools. Different audience than AzuraCast.
• Live365 — commercial internet radio platform with royalty licensing included. Worth it specifically if US royalty complexity is your blocker.
• Raw Icecast + Butt — technically free, zero abstraction layer, maximum configuration headache. The DIY option below AzuraCast.

For a non-technical founder escaping commercial radio hosting, there’s no credible free open-source competitor that matches AzuraCast’s feature set. The realistic shortlist is AzuraCast vs. Libretime if you’re a community station, or AzuraCast vs. paying Radio.co if you want simplicity over ownership.

---

Bottom line

AzuraCast is the obvious answer to “I want to run an internet radio station without paying $50/month forever.” It’s genuinely comprehensive — the streaming server, AutoDJ, scheduler, live DJ support, public player, analytics, and web hooks all ship in one Docker deployment — and it’s genuinely free. The trade-offs are also real: it’s still in beta, it requires Linux comfort or a hand-holding deployment path like Hostinger’s template, and the networking/reverse proxy setup trips up people who haven’t done it before. The AGPL license is fine for almost every use case except building a closed-source commercial product on top of it.

If you’re currently paying a commercial radio hosting platform and you can follow a Linux guide or use a pre-built VPS template, the math is straightforward. The software costs nothing; a VPS runs $5–10/month; and everything you need to run a real radio station is already included.

If the setup is the blocker, that’s exactly what unsubbed.co’s parent studio upready.dev deploys for clients. One-time fee, done, you own the infrastructure.

---

Sources

1. MatthewSmithYT — Guides / How-to’s (personal blog, AzuraCast long-term user). https://matthewsmithyt.me/blog/category/guides/
2. MatthewSmithYT — Blog (references a year or two of AzuraCast self-hosting and networking/reverse proxy learning). https://matthewsmithyt.me/blog/
3. mudithaliyanagama, IceWhale Community Forum — “A Comprehensive Guide to Installing AzuraCast on ZimaOS” (Dec 2025). https://community.zimaspace.com/t/a-comprehensive-guide-to-installing-azuracast-on-zimaos/7618
4. Hostinger Support — “How to Use AzuraCast VPS Template at Hostinger”. https://www.hostinger.com/support/10905872-how-to-use-azuracast-vps-template-at-hostinger/
5. KM WebSoft Knowledgebase — “System Requirements For AzuraCast”. https://www.kmwebsoft.com/clients/knowledgebase/10/System-Requirements-For-AzuraCast.html

Primary sources:

• GitHub repository and README: https://github.com/azuracast/azuracast (3,771 stars, AGPL-3.0 license)
• Official website: https://www.azuracast.com
• Official documentation: https://www.azuracast.com/docs
• Live demo: https://demo.azuracast.com/