1. Define the station before choosing software.
Write down who the station is for, what it will play, when it will broadcast and why a listener should return. A focused weekly station is easier to programme than an undefined promise to be live all the time.
Choose a name you can use, a simple format and a realistic launch schedule. Decide whether the station is music-led, talk-led, community-based, event-based or a mix.
- Audience and editorial purpose
- Music or speech format
- Live versus prepared programming
- Launch date and weekly commitment
2. Confirm content rights and licensing.
Broadcast software does not grant permission to use music, recordings, artwork or syndicated programmes. Requirements depend on where the operator and listeners are located.
Contact the relevant collecting societies or licensing specialists before public launch. Keep records of agreements and understand any reporting obligations.
3. Choose hosting and station software.
A managed platform can combine stream delivery with media, scheduling, AutoDJ, analytics and players. A self-hosted stack can offer more infrastructure control but also makes you responsible for updates, backups, security and stream reliability.
Compare the full operating workflow—not only the advertised listener number. Check storage, team access, scheduling, live handover, public links, support and migration options.
4. Prepare enough programming.
Upload only audio you are entitled to use. Normalise metadata, remove obvious duplicates and build playlists for specific purposes rather than one enormous rotation.
Prepare station IDs and other imaging separately. Build more programming than the minimum needed so AutoDJ does not sound repetitive.
5. Build and test the week.
Place regular shows and prepared programmes on a station-local weekly schedule. Let AutoDJ cover the unattended periods, then inspect conflicts and upcoming gaps.
Listen privately before promoting the station. Check transitions, metadata, artwork, loudness, live-source return and the public player on both phone and desktop.
6. Configure live broadcasting.
Use a dedicated source client such as BUTT or Mixxx, or a compatible hardware encoder. Give each presenter their own credentials and document the correct host, port and mount.
Test what happens when the live connection ends unexpectedly. A safe station returns to automation without asking the audience to reconnect.
7. Launch, measure and improve.
Publish one canonical station page, embed the player on your website and make the listening action obvious. Track listener hours, session duration, concurrency and programme performance rather than chasing a single vanity number.
Start with a stable schedule, learn which programmes earn repeat listening and expand deliberately.