Your TV channels do not need a rack of hardware anymore.

Playout has moved into software. Cloud playout runs a 24/7 channel from a browser or an API, with no playout cards, no channel-in-a-box, and no hardware to replace, and finally shows you who is watching.

A migration guide for broadcasters running channels on SDI or PCIe playout cards, channel-in-a-box appliances, or on-prem playout servers. The operator described is a composite.

The number on the quote was the part that stopped Greta cold. She runs playout for a regional broadcaster, a handful of channels that go out to cable and to a few streaming apps, and for years they had run the way broadcast has always run: on a rack of hardware in a room down the hall. Playout cards, a channel-in-a-box appliance per channel, a server tied to the building, spares on a shelf. The channels worked. But the appliances were aging, the vendor wanted six figures to refresh them, and Greta was being asked to sign off on another five-year cycle of owning and maintaining hardware whose only job was to play a schedule she had already built. She kept coming back to the same thought: the channel is the schedule and the content. Why does it have to live in a box?

It does not, and it has not for a while. Playout has quietly become software, and the case for moving is not just the refresh bill. It is that a channel on hardware is tied to a room, a facility and a maintenance cycle it never needed, and it cannot tell you the one thing every channel owner now wants to know: who is on the other end.

She knew the rack more intimately than she wanted to. There was the Saturday a playout card failed mid-schedule and a channel dropped to black, and the only fix was hands on the box, so an engineer drove in at eleven at night to swap a board off the spares shelf. There was the pop-up channel marketing asked for before a regional event, where the honest answer was that a new channel meant a new appliance, a capital request and a lead time measured in months, so the idea quietly died. And underneath all of it sat the same standing assumption: that someone would always be in the building to look after the hardware. The channels on the rack worked. They just could not grow, and they could not run themselves.

What running a channel on hardware really is

Strip the jargon away and traditional playout, or broadcast automation, is a schedule played out by a machine you own. That machine, a Serial Digital Interface (SDI) or PCI Express (PCIe) playout card feeding a channel-in-a-box appliance, or a rack of them, does the job well, and broadcast engineers have kept channels on air with it for decades. The cost is not the picture; the cost is everything around it. The hardware has to be bought, powered, cooled and refreshed on a cycle. It lives in a facility, so the channel is only as reachable as that building and its uplink. Someone has to be able to get to it, which means staff on hand near the rack; a channel that must never go dark quietly assumes a person is always within reach of the hardware. It does not scale on demand either: every new channel is another appliance to buy, rack and maintain, so growth arrives as a capital project rather than a decision. And it produces almost no usable data about the audience, because a playout appliance is built to send a signal out, not to look back down the line and count who received it.

What is cloud playout, and what does it change?

Cloud playout does the same job in software, running in the cloud instead of on a machine you own. There is no rack, no card, no appliance to refresh. You build the channel the same way you always have, a continuous loop of content or a full 24/7 schedule with an electronic programme guide (EPG), and it plays out over the internet. FastPix Cloud Playout takes in live inputs over the standard secure streaming protocols, Real-Time Messaging Protocol Secure (RTMPS) or Secure Reliable Transport (SRT), and outputs HTTP Live Streaming (HLS) that plays on your apps, your website, smart TVs and any HLS-supported surface. You get the broadcast pieces you expect, graphics and overlays, L-bands, slates, intro and outro, and SCTE-35 ad markers, the broadcast standard for signalling ad breaks, without any of the hardware underneath. A channel is $99 a month, and it stays on because keeping it on is the platform’s job, not a rack’s.

Run it your way: a dashboard, or an API

Here is the part that matters whether or not you have engineers. FastPix gives you both doors to the same channel. Your playout operators can run it from a drag-and-drop dashboard with a programme-guide preview, the same way they schedule today, with no code and no new technical skill to learn. And your developers, if you have them, can create, schedule, fill and retire channels entirely from an application programming interface (API), so a channel becomes something your systems can automate rather than something a person sets up by hand. You choose per channel: schedule a flagship channel yourself in the browser, and let code run a hundred pop-up or regional channels beside it. The hardware never gave you that choice; it only ran one way.

And you can finally see who is watching

A playout appliance sends a signal into the dark. Cloud playout does not. FastPix reports server-side analytics on every channel: how many people are watching right now, where they are, how many watched across the day, and which programme held them, measured server-side so it holds across every device and simulcast surface. Few playout systems, on hardware or in the cloud, give you that by default. For a broadcaster who has spent years running channels on faith, being able to read the audience is not a nice-to-have; it is the difference between programming by instinct and programming by evidence.

How much does cloud playout cost versus a playout appliance?

The clearest reason finance signs off is that the cost stops being a capital purchase and becomes an operating line. On hardware, a channel is an appliance you buy, a facility you power and cool, spares you keep, and a refresh you budget for every few years, plus the specialised people who maintain it. In the cloud, a channel is $99 a month plus what it uses, with no hardware to buy, nothing to refresh, and no facility to run. You are not just trading one bill for another; you are removing the whole category of capital, real estate and maintenance that a rack of playout hardware quietly carries.

How do you move a channel off playout hardware?

The move is less dramatic than the rack makes it look, and you do not have to do it all at once. You rebuild your schedule in the cloud, point your live inputs up over RTMPS or SRT, and take the HLS output to the same places the channel goes today. The safe path is to run the cloud channel alongside the hardware for a while, watch it hold through the hours that matter, and cut over only when you trust it. And you do not have to move everything.

Do you still need SDI cards and studio hardware?

To be clear, because broadcast engineers will rightly ask: this is not an argument to throw out your studio. If you run genuine live production, multiple cameras, a vision mixer, master control, that gear does a job cloud playout does not, and you can keep it. Cloud playout is delivered over the internet, not over SDI baseband, so the honest picture is a hybrid: your live production stays where it is and sends its output up over IP, and the always-on channel, the scheduling, the graphics, the origination and the distribution, moves to software. What leaves the building is the box whose only job was to play a schedule. What stays is the craft.

The short version

The channel was never the hardware. It was the schedule and the content. Move those to software and the rack becomes something you used to own.

Greta did not sign the refresh quote. She stood one channel up in the cloud, ran it beside the rack for a month, then moved the rest a channel at a time, and gave the room back. Rebuild the schedule. Point the inputs. Run it from the dashboard, or the API. Read the audience. Retire the rack. Modern video is what we do.