Website Radio Operator Guide: Setup, Hosting, Pricing

Gary Whittaker
OPERATOR-LEVEL TRAINING GUIDE

How to Add Live Radio to Your Website

Complete training guide to hosted trials, hosted paid platforms, self-hosted systems, hosting requirements, domain decisions, real pricing, one-time costs, post-trial outcomes, and what to do next.

This page is built to function as a premium decision guide, buyer’s guide, and execution manual at the same time. It is not here to sell one platform as the hero. It is here to teach the system clearly enough that you can choose the right path, understand what you are actually paying for, and avoid building the wrong thing too early.

Fastest first test
RadioKing or Radio.co trial
Licensing-aware hosted path
Live365
Ownership path
Self-hosted radio engine + paid hosting
Worst mistake
Custom build before proving the station matters

Start Here: The Decision Framework

Website radio is not one product. It is a system with multiple valid operating models. The decision should be made in this order:

  1. Validate whether live radio belongs on your site at all.
  2. Choose whether you want convenience or ownership.
  3. Choose whether licensing support is central to your decision.
  4. Only after that consider custom experience layers.
Operator rule: validate first, operate second, customize third. Reversing that order is where wasted money usually begins.

1) What you are actually building

Every live radio setup has three layers. The radio engine controls playlists, scheduling, automation, and station behavior. The streaming layer delivers audio to listeners. The website layer is the page or player your audience actually sees. Different solutions give you different levels of control over those layers.

Layer What it does Why it matters
Radio engine Manages media, playlists, scheduling, automation, DJs, and metadata Determines how the station is run day to day
Streaming layer Sends audio to listeners in real time Determines reliability, bitrate, and listening capacity
Website layer Displays the player or live page on your site Shapes the visitor experience and conversion flow

2) The four real operator paths

Path A: Hosted trial

Fastest validation path. No server setup. Best when you want to test the concept before carrying infrastructure responsibility.

Path B: Hosted paid

Stay on the managed platform after trial. Best when convenience matters more than ownership.

Path C: Self-hosted

Use free radio software with paid hosting. Best when you want more control and lower software cost over time.

Path D: Custom platform layer

Add submissions, custom UX, moderation, and product features later. This is not the starting point.

3) What you should prepare before choosing any platform

Every path gets easier if the preparation is done first. Have a working station name, 10–20 test tracks, clean file names and metadata, a basic station purpose, and a page on your current site where the player can live.

  • Station name
  • 10–20 test tracks
  • Basic metadata and clean filenames
  • Simple content purpose
  • Existing page or planned page on your site
  • Commitment to keep the first version small

4) Operator chapters: equal-depth platform breakdowns

RadioKing operator guide

What it is

RadioKing is a fully hosted radio platform. You are using their infrastructure, their station management tools, and their streaming layer. You are not installing a server-side radio system yourself.

Who it is for

Best for fast validation, low technical friction, and operators who want to test radio on a website quickly without learning infrastructure first.

What the free path really means

The free path is a 14-day trial with no credit card required. That means you get time to test the hosted environment, not a permanent free station.

What setup actually involves

  1. Create the trial account.
  2. Name the station.
  3. Upload your test tracks.
  4. Create one playlist or default programming block.
  5. Enable automation.
  6. Generate or copy the player/embed details.
  7. Place the player on your site.
  8. Test on desktop and mobile.

What you get

You get a dashboard, media library, automation tools, schedule options, player sharing tools, and basic stats inside a managed environment.

What happens after the trial

If you pay, the station continues inside RadioKing. If you do not, the trial environment ends. If you want to move elsewhere, you treat the trial as a test build and recreate the station in the new system.

Pricing structure

Plan Monthly price Listening hours Storage
Discover $19 150 1 GB
Start $34 20,000 5 GB
Pro $64 150,000 10 GB
Business $119 500,000 20 GB

One-time costs

Normally none on the technical side. This is a monthly-cost-first path, not a one-time-build-first path.

What you are responsible for

Content, station logic, metadata quality, and how the station fits your site. RadioKing handles infrastructure.

Radio.co operator guide

What it is

Radio.co is a managed radio SaaS platform with a more conventional plan-and-add-on structure.

Who it is for

Best for people who want a managed environment, clearer tier progression, and optional expansion into mobile apps or other managed extras later.

What the free path really means

The free path is a 14-day trial on any plan. Some features are limited to paid plans or add-ons, so the trial is primarily there to evaluate the environment and workflow.

What setup actually involves

  1. Create the trial.
  2. Choose the plan level you want to test.
  3. Create the station.
  4. Upload media.
  5. Build playlists and schedule logic.
  6. Generate the output.
  7. Embed the player on your site.
  8. Evaluate the experience and workflow.

What you get

You get managed storage, listener allowances, bandwidth or monthly usage allowances by plan, player tools, scheduling, and optional expansion through higher tiers or paid extras.

What happens after the trial

You subscribe and continue, or the trial ends. If you want to move to a self-hosted system later, you rebuild there rather than converting the hosted environment into owned infrastructure.

Pricing structure

Plan Monthly price Notes
Lite $35 Entry managed plan
Standard $59 Broader feature access
Plus $139 Higher-tier plan
Premium $199 Top standard public tier

One-time costs

Minimal unless you add optional extras or outside work. This remains a recurring-cost-centered model.

What you are responsible for

Programming, media, and the site experience. The infrastructure is still handled for you.

Live365 operator guide

What it is

Live365 is a managed broadcaster platform that distinguishes itself by including music licensing on broadcaster plans in supported markets.

Who it is for

Best for operators whose decision is heavily shaped by licensing support rather than only by the lowest apparent monthly entry price.

What the free path really means

The free path is a 7-day broadcaster trial. It is meant to validate the hosted workflow, not to create a permanent free station.

What setup actually involves

  1. Create the broadcaster trial account.
  2. Set up the station profile.
  3. Upload media.
  4. Configure the station and launch the stream.
  5. Connect the player to your website.
  6. Test the listening and operating workflow.

What you get

A hosted station environment, licensing on broadcaster plans, tier-based storage and total listening hour limits, and higher-plan access to distribution and app-oriented features.

What happens after the trial

You upgrade into a broadcaster plan or the trial environment ends. Staying means remaining inside the managed platform. Leaving means rebuilding elsewhere.

Pricing structure

Plan Monthly price Total listening hours Storage
Broadcast 1 $59 1,500 30 GB
Broadcast 2 $99 3,500 50 GB
Broadcast 3 $199 7,000 100 GB
Broadcast 4 $499 10,000 200 GB
Broadcast 5 $999 20,000 500 GB

One-time costs

Normally limited unless you build outside the platform. The main cost is ongoing monthly subscription.

What you are responsible for

Programming, content quality, metadata, and how the station fits your site and audience.

Self-hosted operator guide

What it is

A self-hosted radio system runs on infrastructure you control. The software itself may be free, but the hosting and operational responsibility are yours.

Who it is for

Best for operators who want ownership, lower software cost over time, flexibility, and independence from a managed platform.

What the free path really means

Free means the radio software itself does not require a paid software subscription. It does not mean hosting, bandwidth, installation, maintenance, or uptime are free.

What setup actually involves

  1. Choose a compatible server environment.
  2. Provision the server.
  3. Install the radio software.
  4. Create the station.
  5. Upload media.
  6. Configure playlists and automation.
  7. Start the stream.
  8. Connect the public player or stream to your website.

What you get

Ownership of the station engine and more control over how the whole system is run. What you do not get is a platform company absorbing operational responsibility for you.

What happens after setup

There is no hosted trial cliff. The system continues as long as the hosting, software, and operations are maintained.

Pricing structure

The core recurring cost is the server or managed self-hosting environment, not a radio SaaS subscription. For many operators this becomes the lower-cost ownership path after validation.

Cost category Typical cost What it covers
Radio software $0 Software itself
VPS / server About $5–$20/month Infrastructure
Managed self-hosting Varies Less setup friction, still not pure hosted radio SaaS
Domain $0 if you already own one Only needed if you want a new domain

One-time costs

Can be almost nothing if you do the setup yourself. One-time costs appear when you pay for setup, migration, or custom work.

What you are responsible for

Server health, uptime, updates, backups, maintenance, troubleshooting, and the station itself.

5) Pricing models explained properly

This is where most readers make the wrong comparison. Monthly numbers alone do not tell the real story. The pricing model tells the real story.

  • Hosted plan pricing: pay for managed convenience and infrastructure.
  • Listening-hour pricing: cost grows when real usage grows.
  • Tier-based SaaS pricing: easier to read up front, but useful features can move into higher plans or add-ons.
  • Free software + paid infrastructure: lower software cost, higher operational responsibility.
  • Custom build costs: one-time development cost starts to matter only after the station itself is proven useful.
Translation: the cheapest-looking plan is not automatically the cheapest operating model once real listeners, storage, features, and responsibility are accounted for.

6) Hosting requirements, fully clarified

Hosting is only a direct requirement in the self-hosted path. A hosted radio platform already includes the infrastructure layer.

What works

  • VPS
  • Dedicated server
  • Managed host that explicitly supports self-hosted radio software

What does not work

  • Normal shared website hosting
  • Standard Shopify hosting
  • Basic WordPress hosting packages
  • Any environment that does not support the required installation method and admin control

What you are looking for

Linux server support, administrative access, sufficient RAM and CPU for continuous streaming, adequate storage for your library, and network capacity appropriate to your expected listeners.

Important distinction: your website can stay where it is. The radio engine can run somewhere else. You are connecting the website layer to the radio layer, not replacing your site hosting with radio hosting.

7) Domain and subdomain decisions

You do not need a new domain to add live radio to your site. The cleanest first move is usually to use your current domain and add a page like:

  • /radio
  • /live
  • /listen

A subdomain such as radio.yourdomain.com is optional and makes sense only when you want more separation or cleaner organization later.

Do not buy a new domain just because you are testing radio.

8) Rights and licensing basics

The cleanest test uses music you fully control. Once the station moves beyond that, rights and licensing stop being a side issue and become part of the real platform decision.

This is exactly why a platform with licensing support can make more sense than a cheaper headline price if your use case depends on it.

9) What happens after testing?

There are only three real outcomes after a good test:

  1. Stay hosted. Best when convenience is worth the recurring platform cost.
  2. Move self-hosted. Best when ownership, flexibility, or long-term cost control matters more.
  3. Stop. A test that proves the feature is not worth continuing is still a success.
A hosted trial is not ownership. A self-hosted deployment is not a managed convenience purchase. Keeping those two truths clear is what makes the decision clean.

10) When to move from hosted to self-hosted

Move only when the reason is operationally real:

  • You want ownership.
  • You want lower software cost over time.
  • You need more control than the hosted system offers.
  • You are willing to carry the infrastructure responsibility.

Do not move just because self-hosting sounds more advanced.

11) Final recommendations matrix

Situation Best first move Why
You want the fastest possible first test RadioKing or Radio.co Minimal technical friction
Licensing support is central to the decision Live365 Licensing is part of the value structure
You want ownership and long-term control Self-hosted path Best control model
You are tempted to build custom features immediately Do not Prove the station matters first

12) What not to do first

  • Do not buy a new domain just because you are testing radio.
  • Do not confuse a hosted trial with infrastructure you own.
  • Do not assume free software means the entire system is free.
  • Do not skip mobile testing.
  • Do not jump to custom development before validating the core use case.
  • Do not choose the most advanced path just because it sounds powerful.

Final takeaway

The right website radio build starts with the right decision order. Validate the feature first. Choose convenience or ownership second. Add custom product layers only after the station itself has proven useful.

That sequence is what turns this from an expensive distraction into a disciplined build.

Regresar al blog

Deja un comentario

Ten en cuenta que los comentarios deben aprobarse antes de que se publiquen.