Radio automation software in 2026: desktop, self-hosted and cloud compared

A radio station is a 168-hour-a-week product made by people who sleep. Radio automation software is what covers the difference: it decides what plays next, keeps the transitions tight, runs your shows on time, and — if it is any good — keeps automated playout inside the rules your music licence depends on. The category spans free Windows applications, self-hosted servers, and cloud platforms where automation is the product and the stream server is plumbing. This guide explains what the software really has to do, and which generation of it fits which station.

1. What automation software actually does

Underneath the different interfaces, every automation system is doing the same five things. Judge any of them on how well they do these, not on the length of the feature list.

• Playout. Play the next item cleanly — correct levels, sensible crossfade, no gap and no collision. Boring, constant, and the first thing listeners notice when it goes wrong.
• Selection. Decide *what* the next item is. This is where the difference between “radio” and “a folder on shuffle” lives.
• Scheduling. Put the right programming in the right hours — the breakfast show, the specialist Friday-night slot, the overnight bed — and hand control over and back at the right moment.
• Live handover. Get out of the way when a presenter goes live, and pick the station back up the instant they leave, including when they leave involuntarily.
• Logging. Record what actually played, with artist and title, because that log is your royalty reporting and your only honest answer to “what was that song?”.

2. The three generations, and what each one costs you

Automation software arrived in three waves, and all three are still in active use — which is why comparisons get confusing. They are not really competitors; they are different bets about where the station should live.

3. Five features that decide how your station sounds

Rotation rules, not shuffle

Shuffle is random, and random sounds wrong: the same artist twice in twenty minutes, three ballads in a row, the one novelty track surfacing every afternoon. Real programming uses separation rules (how long before that artist, that title, that album can return), categories (currents, recurrents, gold, local) and clocks that say what kind of thing plays in each slot of the hour. That is the difference between a playlist and a station — rule-based rotation shows what it sounds like in practice.

Scheduling that survives contact with a week

Any system can play a file at 9 a.m. The useful questions are what happens when a live show overruns, whether a scheduled block picks up where it left off or restarts from the top every week, and how it behaves the day nobody remembers to schedule anything. Schedules and shows covers how we handle it; whatever you use, test that third case deliberately.

Transitions you did not have to hand-tune

Crossfades, level matching and a clean segue out of a talk break are what make a station sound produced. If getting a decent transition requires per-track cue points on a library of thousands, the software has handed you a second job.

Compliance enforced by the sequencer

If you broadcast commercial music in the US under the statutory webcasting licence, your automated hours must respect the performance complement: limits on how many tracks by the same artist or from the same album can play in a rolling window, and no pre-announcing exact play times. No human can hold that while programming. In Nobex, Cloud AutoDJ simply will not schedule a track that would break the window, and tracks you flag as your own recordings are exempt from it. Ask any automation system what it does here — most do nothing, which makes the rule your problem forever.

A play log you can actually export

Reporting to the societies means handing over what played, with clean artist and title on every entry. That is trivial if the metadata was right on upload and archaeological if it was not — see now-playing branding and royalty reports.

4. The free options, fairly

Free automation software is genuinely good and worth knowing about. RadioDJ is a capable Windows automation system with rotation rules and event scheduling, free to use. Mixxx is open-source DJ software with broadcasting built in — excellent live, lighter on unattended programming. AzuraCast and LibreTime are full self-hosted station platforms with web interfaces, both free software. Rivendell is broadcast-grade Linux automation used by real terrestrial stations.

What they have in common is the thing that is never free: somewhere to run, and someone to keep it running. A Windows box that stays awake, or a VPS with TLS, backups, monitoring and updates. That is the honest comparison against a subscription — not “free versus $19”, but “free plus your evenings versus one line item”. The software round-up goes through the individual tools in more detail.

5. What moving automation to the cloud changes

When the automation runs on the platform rather than on your machine, four things change, and they are the reasons the category moved:

• Your computer stops being infrastructure. Close the laptop; the station keeps playing. The single largest cause of dead air in small radio simply stops existing.
• Live handover becomes automatic in both directions. Go live from a browser or a phone and automation steps back; drop the connection and it resumes in the same instant, rather than after you have driven home.
• The library, the schedule and the stream are one system. No syncing a local library to a remote server, no wondering which copy is current.
• Programming becomes portable. You can fix the rotation from a phone on a train, which is where a surprising amount of radio programming actually happens.

What you give up is absolute control of the stack. If you need a specific desktop tool in the chain, keep it — a good platform still accepts any Icecast-compatible encoder, so you can run your own rig and let cloud automation cover the hours you are not at the desk.

6. Choosing, in three questions

1. 1Where will this run at 4 a.m. on a Tuesday? If the honest answer is “my computer, probably”, choose the generation that removes that sentence.
2. 2Can I express my station’s rules in it? Write down three real rules — “never the same artist within two hours”, “no two ballads back to back”, “the specialist show owns Friday 9–11”. If the software cannot say them, you will be doing it by hand forever.
3. 3Does it keep me legal without me remembering to? Automated compliance and a clean, exportable play log. Rules you have to hold in your head are rules you will eventually break on the night you are busiest.

7. Radio automation software, asked and answered