Your 24/7 channel should not depend on a computer staying awake.

The call came at three in the morning, the way it always does. Theo runs a channel, a 24/7 loop of his company’s content that plays in the app and on a couple of connected-TV surfaces, and for a year it had run off a dedicated PC in the corner of the office with OBS open on it and a stream key pointed at a server. That night the machine had crashed, the way machines do somewhere in the small hours of a long run, and the channel had been a black screen since one. Nobody noticed until a viewer emailed. Theo got dressed, drove in, and restarted a computer. The channel, the thing his company had told viewers they could always turn to, had been held up the whole time by a tower under a desk that no one was watching.

Nothing was wrong with Theo’s setup, exactly. OBS and vMix are excellent at what they are for. The problem is what he had asked them to be: not a tool for producing a show, but infrastructure that has to stay on forever.

What running a channel on a machine actually is

OBS and vMix are switchers. You point cameras and clips and graphics at them, you mix a live production, and you push the result somewhere. For an event, a broadcast, a show with a beginning and an end, they are the right tool and a lot of professionals rely on them. A 24/7 channel is a different animal. It has no end. It has to keep playing at four in the morning when no one is in the building, through driver updates and memory leaks and the slow accumulation of whatever makes a graphics card give up two hours into a render. Ask any long-running stream operator what happens overnight and you will hear the same stories: the crash no one caught, the black screen at four in the morning, the drive back to the office to press a button.

Underneath the crash are four constraints that a channel on a machine can never escape. There is the hardware: a computer and a graphics card that have to run flat out, forever, and that you own and maintain. There is the network: the channel is only as reliable as that one office uplink. There is the location: someone has to be able to physically reach the box, which means the channel is tied to a room. And there is the thing that hurts quietly, the blindness: OBS and vMix push a stream out and tell you almost nothing about who received it. You are broadcasting, and you cannot see your audience.

What “always on” actually takes

The word people underuse is uptime. A channel your viewers are told they can always turn to is a promise, and keeping it means far more than leaving an app open on a computer. It means something is watching the channel around the clock and restarting it the instant it drops. It means a second path when the first one fails, so a single crash does not become a black screen nobody catches. It means a person reachable when it all goes wrong at the hour no one wants to be reachable. A PC running OBS gives you none of that: one machine, one connection, one person who might notice. Every serious broadcaster solves this with redundancy and monitoring, and building that yourself around a tower under a desk is a project that quietly turns one channel into a second job. Cloud playout treats uptime as the default, because staying on air is the entire point of a channel.

What cloud playout changes

Cloud playout moves the channel off your machine and into software that runs in the cloud. There is no PC in the corner, no graphics card to nurse, no stream key to restart at 3am. FastPix Cloud Playout runs the channel for you: you schedule it, in a drag-and-drop dashboard or from the application programming interface (API), whichever suits the channel, and it plays. It runs two kinds of channels, looped for a continuous set of content on a shorter or simpler channel, and scheduled for a programmed 24/7 timeline with an electronic programme guide (EPG). You can take in live inputs over RTMPS or SRT, the secure protocols encoders use to push a live signal, mix them with video-on-demand (VOD) assets in one timeline, drop in SCTE-35 ad markers, and simulcast an HTTP Live Streaming (HLS) output. No hardware, no FFmpeg to wire up, no babysitting. A channel is $99 a month, and it stays on because keeping it on is our job, not a tower’s.

And you can finally see who is watching

Here is the part that OBS and vMix never gave you, and that most cloud tools skip too. FastPix reports server-side analytics on the channel itself: how many people are watching right now, where in the world they are, how many watched across the day, and which programme held them. Because it is measured server-side rather than inside one player, it holds up across devices and on the surfaces you simulcast to, and few playout providers give you that by default. A channel you cannot measure is a channel you are running on faith. This is the difference between broadcasting into the dark and running something you can actually read.

A stream can live on a laptop. A 24/7 channel is infrastructure, and infrastructure should not have a power button someone can trip over.

Moving is a day, not a project

The move is smaller than the fear of it. You do not rebuild anything; you point what you already have at a channel that runs itself.

Point your inputs first: your live feeds over RTMPS or SRT, and the video-on-demand assets you loop or schedule. Build the schedule next, looped or programmed, in the dashboard or from the API, with an EPG if you want one. Then take the HLS output and play it wherever the channel lives today. The safe way to do it is side by side: stand the cloud channel up next to the machine, watch it hold for a week through the exact hours that used to break, and only then turn the tower off. The cutover is the easy part. Trusting it takes a week, and then you never think about the machine again.

Where OBS and vMix still belong

To be clear, because it matters: this is not an argument to throw out your switcher. If you produce a genuine live show, multiple cameras, live graphics, a person mixing it in real time, OBS and vMix are built for exactly that and they are very good at it. Cloud playout does not replace the studio; it replaces the always-on channel you turned a studio tool into. In fact the two work together: keep producing your live show in vMix if that is your craft, and send its output into a cloud channel as one block in the schedule, sitting alongside your VOD. What moves to the cloud is the part that never should have been a person’s job at three in the morning: keeping the channel on.

The costs that never show up on the machine

The PC in the corner looks free because you already own it, and that is the trap. It is not free. There is the hardware and the refresh cycle that replaces it. There is the graphics card running flat out every hour of every day. There is the person whose evening gets interrupted, the drive back to the office, the apology to the viewer who caught the black screen. And there is the cost you can least afford and cannot see: the person who tried the channel during an outage you never knew about and did not come back. A channel that runs itself in software does not send you those bills. The signs you have already outgrown the machine are simple, and you probably recognise at least one: you have missed a crash, you want a second channel and cannot run it, or you have realised you can never be more than a car ride from the box.

The short version

Theo moved his channel in an afternoon and ran it beside the tower for a week, through every hour that used to wake him. The machine never got to prove itself again; he turned it off and gave the desk back. Turn the machine off. Schedule the channel. Point the inputs. Watch who shows up. Modern video is what we do.