Solutions
One product, four different realities
Viper is a single installation, but what a small regional broadcaster needs is not what a production company needs. Here is what it solves in each case.
Pick the one closest to yours. If none fits exactly, write to us: in this market almost nobody falls neatly into a category.
Small broadcast channel
Two or three people, daily transmission, a tight budget.
What hurts today
- Someone has to sit watching the screen until the schedule ends.
- The rundown is built by hand every day and the last block is always missing.
- When something fails at 3 a.m., nobody knows what happened or when.
What Viper does
- The day's rundown is loaded once and the channel advances on its own, with automatic continuity.
- Playlists are reused by date and time: build one week, repeat it.
- The As-Run records what aired, at what time, and whether automation or a person fired it.
The modules that matter most
-
Playout
What is on, what comes next, and how long is left. No second window, and nobody to call.
-
Scheduling
Playlists that get reused, assigned to days and hours. And a calendar that shows which slot is still empty before it shows on air.
-
As-Run
The schedule says what was supposed to go out. As-Run says what went out. They are not always the same, and the difference is what you get asked about.
This is the case Viper was designed for first: one machine, one person, and the channel on air with nobody on call.
Cable network
Several feeds or several shifts, rotating operators, and management asking for numbers.
What hurts today
- Every operator does things their own way and nobody knows who touched what.
- You need to separate who can put something on air from who cannot.
- The advertiser wants proof that their spot actually aired.
What Viper does
- Per-person permissions, area by area: who goes on air, who schedules, and who only sees the record of what aired.
- Several seats against the same station, each with its own user.
- The As-Run, with real air times, is the proof the advertiser is asking for, and it exports to CSV.
The modules that matter most
-
Multi-seat
Only one machine goes to air. The others are work seats against that same station: scheduling, ingest and graphics happen without sitting at the one that is broadcasting.
-
As-Run
The schedule says what was supposed to go out. As-Run says what went out. They are not always the same, and the difference is what you get asked about.
-
Scheduling
Playlists that get reused, assigned to days and hours. And a calendar that shows which slot is still empty before it shows on air.
What gets bought here is not playout: it is knowing who did what, and being able to prove it.
Production company
Produces content for third parties and delivers, with workload peaks and changing teams.
What hurts today
- Material arrives in twenty formats and has to be normalised before it can be used.
- Graphics are rebuilt for every delivery because there is nowhere to keep them ready.
- You have to hand over a recording of what aired, not a promise.
What Viper does
- Ingest normalises what comes in and leaves it ready for the rundown.
- Graphics are designed once and fired as many times as needed.
- Output recording produces the file of what was actually emitted — it is licensed separately, like everything each channel uses.
The modules that matter most
-
Ingest
Nobody types in how long a clip runs. It is read from the file, it lands in the catalogue, and it is scheduled from there.
-
Graphics
Graphics are HTML and go out through the same engine as the video. There is no separate character generator to buy, feed and keep in sync.
-
Recording
Recording is switched on from the same Playout screen, with the signal on air. For the complaint, for the archive, or to run it again.
The value is in the round trip: what comes in gets normalised, and what goes out gets recorded.
Streaming channel
Broadcasts over the internet, with no broadcast infrastructure and a connection that does not always cooperate.
What hurts today
- An internet outage leaves the channel black and nobody notices until someone complains.
- There is no budget for capture cards or a dedicated server.
- Programming runs 24/7 and there is no night shift.
What Viper does
- The station stays on air even if the internet drops, for a grace period that has an end: the licence revalidates when the connection returns.
- It runs on your own hardware, with no proprietary cards: a PC that meets the requirements, not a dedicated server.
- The rundown advances on its own, with continuity handled between blocks.
The modules that matter most
-
Stays on air without internet
Air cannot depend on the internet provider. If the link goes down, the station keeps broadcasting on its own for a grace period — and when it comes back, it catches up without anyone doing anything.
-
Playout
What is on, what comes next, and how long is left. No second window, and nobody to call.
-
Scheduling
Playlists that get reused, assigned to days and hours. And a calendar that shows which slot is still empty before it shows on air.
This is the segment where it matters most that the station does not depend on the cloud to stay on air.
Request a demo
Tell us about your channel and what you go on air with today. We'll show you the product running, and then we'll talk numbers.
We use your details only to reply to you. We don't share them with anyone.