Can only our employees listen to the company radio?

Yes. List your intranet in the embed settings so the player loads only there, and choose an access mode for the broadcast: link only, signed-in viewers only, private, or a passphrase you share internally. The chat is closed by the same lock as the broadcast.

Do we need a studio to run a company radio on DCAST?

No. A host with a laptop and a good microphone can broadcast from a browser tab. OBS, vMix or a hardware encoder over RTMP or SRT work the same way when you want a bigger setup.

Can our AI assistant set up and run the station?

Yes. Connect it through the DCAST MCP connector and give it a role, as you would a team member. It works through the whole DCAST API, asks you before it does anything its role does not cover, and never handles payments, API keys or team members.

Which plan do we need for a weekly show?

The free plan is for rehearsals: it stops a broadcast after one hour and gives 10 live hours a month. STAR at $49 a month removes those limits and adds moderators and a co-host, which is enough for one weekly show.

Company Internet Radio Station on Your Own Website | DCAST

A radio station used to mean a transmitter, a licence and a building. Today a company radio is a page on your intranet: a live player, a chat next to it, a host in a small studio (or at a desk with a good microphone), and a weekly slot people look forward to.

Companies already run them: a Friday music hour for the whole office, a weekly news show from the CEO's team, a morning programme for warehouse and field staff, a quarterly town hall with live questions. What they have in common is that the show belongs to the company — on the company's site, under the company's name, for the company's people.

This article shows how to build exactly that on DCAST, step by step, and how to hand the routine work to your own systems or to your AI assistant.

Why a company radio works

Email newsletters get skimmed, and recorded videos pile up unwatched. A live show is different: it happens at a known time, people can answer back, and the host can react to them. That is why internal radio keeps coming back in companies of every size.

It reaches people who are not at a desk. Warehouse teams, drivers, shop floors and field engineers can listen on a phone while they work.
It gives leadership a human voice. A short weekly update with live questions builds more trust than a memo.
It connects offices. A show that every location listens to at the same time is one of the few shared moments a distributed company has.
It is cheap to run once it is set up. One host, one microphone, one page. The station does not need a studio building; it needs a schedule.

What a modern station looks like

It lives on your page. Listeners do not go to a video platform; the station comes to them. You place two pieces on your page — the player and the live chat — wherever your layout wants them: side by side on desktop, chat below the player on a phone, or the chat on its own page for the moderator's second screen.

It is live. A real host, real-time chat, polls during the show ("which track next?"), a quiz before the weekend. The host sees the audience count and the questions as they arrive.

It is for your people only. Internal shows are internal. The station is visible only where you allow it and only to whom you allow it.

It remembers. Every show becomes an episode you can replay the next morning, so the shift that missed it is not left out.

It runs itself. After the first setup nobody has to remember which buttons to press on Thursday. The weekly show is created, started, recorded and archived from your own systems.

Planning your first shows

Before any technology, decide what the station is for. The stations that last start small and keep a steady rhythm.

Pick one slot and keep it. The same day and time every week matters more than the length of the show. Thirty minutes every Thursday beats an ambitious two-hour show that happens once.
Give it a format people can predict. For example: five minutes of company news, a guest from one team, listener questions from the chat, and a track or a quiz to close.
Choose a host, not a speaker. The best internal hosts are curious colleagues who enjoy talking to people, not necessarily the most senior ones. Leadership works best as a regular guest.
Prepare a simple run sheet. One page with the segments, who speaks when, and the poll or quiz questions you plan to ask. It keeps a live show calm.
Invite the audience in. Ask for questions in advance, read names on air, and let listeners choose the next track. A chat that gets answered fills up quickly.
Measure and adjust. Look at how many people listened live, how many replayed the episode later, and which segments got the most chat. Change one thing at a time.

Building the station on DCAST, step by step

1. The broadcast

Create a broadcast in DCAST and send your signal to it from whatever you already have: OBS or vMix on a studio PC, a hardware encoder (RTMP or SRT), or simply a browser tab (WHIP) for a host working from home. A setup with several cameras and a mixing desk works the same way as a laptop with a microphone — DCAST receives the signal, shows you a preview, and when you press Start delivers it to listeners in several quality levels, so it plays smoothly on the office Wi-Fi and on a phone on mobile data alike.

Many stations show a still cover — the station logo, the name of the show — with the audio on top; others show the studio and the host. Both are just what your encoder sends.

2. The player and the chat on your page

Open the broadcast's Embed dialog. It gives you two codes: the player and the live chat. Paste them into your page. They are independent on purpose: you decide the layout, and a redesign of your page never has to wait for us. The chat follows a light or dark theme, so it fits the look of your intranet.

3. Employees only

Two locks, used together:

Where the station may appear. In your embed settings, list the sites allowed to show your content — for example intranet.yourcompany.com. Everywhere else, the player refuses to load.
Who may listen. Each broadcast has an access mode: shared by link only, signed-in viewers only, private, or a passphrase you announce internally ("this week's code is in the Monday newsletter"). The chat is closed by the same lock as the broadcast: whoever may not watch may not read the chat either.

4. The show with your audience

The chat is part of the show: the host reads messages on air, runs a poll for the next track, posts a quiz question and announces the winner. A moderator with their own login (a team member on your plan) keeps the chat tidy while the host talks.

5. The archive

Turn recording on and each broadcast becomes an episode as soon as it ends. Through the API (next section) your page can list past episodes next to the live player, so Monday's listeners can catch up on Friday's show.

Running the station from your own systems

Everything above is also available through the DCAST API: create next week's broadcast, start it, end it, read its status and audience, read and moderate the chat, keep the recording, set the list of allowed sites. That means the station can be run from your intranet, your scheduler or your internal tools — nobody needs to log in to DCAST every week.

The DCAST API reference and its OpenAPI description are public, so your developers, or any tool that can call a REST API, can do the wiring. You keep the result: your page, your code, your station.

Prefer to do it by hand? The Embed dialog and the dashboard stay exactly where they are.

Or just ask your AI assistant

You do not even have to write that integration yourself. DCAST has an MCP connector at https://api.dcast.pro/mcp. Add it to Claude (or another assistant that supports remote MCP connectors), sign in with your DCAST account, and the assistant can work with your whole DCAST account through the API — not a short list of radio buttons, but the same operations your developers would use: broadcasts, chat, recordings, videos and playlists, embed settings, statistics. Radio is just one thing you can ask it to build. Then ask:

"Set up our weekly company radio: a broadcast every Thursday at 4 pm called Office Hour, recorded, visible only on intranet.ourcompany.com. Put the player and the chat on our intranet page and show past episodes under it."

The assistant joins your team with a role

An AI assistant connected to DCAST is treated like a new member of your team, not like an all-powerful key. It gets a role, in the same team settings where you manage people:

When you connect it, DCAST asks in plain words what the assistant may do, area by area: watch the statistics, run broadcasts, moderate the chat, manage videos, change the site's appearance. At first it can only look; before it changes anything, it asks you.
When it needs more, for example to delete spam in the chat during a show, it does not fail silently. You get a request in your dashboard that says exactly what it wants to do and why, with Allow, Allow once and Deny. After you allow it, the assistant simply repeats the step.
It can do what a person in that role can do. An assistant with the moderator role moderates the chat like a human moderator; one with the stream technician role starts and stops broadcasts.
Some things stay with people. Payments, payouts, API keys and inviting or removing team members are never available to an assistant, whatever role it has.
You can change or revoke its role at any time, and the change applies to its very next step.

That is what makes it practical for the people who actually run internal communications: they do not need to know what an API scope is to see exactly what the assistant is allowed to do.

Or let us build it for you

If you would rather not deal with any of this, we build the station for you: the page with the player and the chat, access for your employees only, the studio or encoder settings, the weekly schedule and the archive. And if you want a produced show — cameras in the office, a live host or DJ, chat and audience games — our streaming crew can run it. Both are quoted per project.

Which plan a station needs

The free plan is a real test drive: go live, embed the player, try the chat. It stops a broadcast after one hour and gives 10 live hours a month, which is enough to rehearse but not to run a weekly show.

STAR ($49/month) — no limit on broadcast length or monthly live time, 1080p, a co-host and moderators with their own logins, 500 GB for the archive. The plan for one weekly show.
PRO ($149/month) — your brand only (no DCAST logo, your own domain), a backup encoder that takes over if the studio PC drops, extra language audio tracks for international teams, your own web player on your site.
VIP ($299/month) — company-wide broadcasts for thousands of employees, 4K, the DHUB multi-source production set included.

Start this week

Create a free DCAST account and a test broadcast.
Paste the player and chat codes onto a test page, list your site in the embed settings.
Do a 20-minute rehearsal with your host.
Pick the plan that fits your show and go on air.

Or tell us about your station and we will set it up for you.