Broadcast operations platform
Every live event. One source of truth.
Cadence is the control room for live broadcast operations. One shared record for every event — from the moment it is scheduled to the moment it hits air, and every hand it passes through in between.
Runs entirely on your own infrastructure.
- 13:00→ 15:15Cycling — Spring Classic, stage 4Channel One3.2 → 2.2On air
- 15:30→ 16:30Debate — Prime TimeChannel Two3.3 → 2.3Published
- 17:00→ 17:45Magazine — Culture WeeklyChannel One3.1 → 2.1Published
- 18:00→ 18:40Evening NewsChannel One3.4 → 2.4Published
- 20:45→ 22:30Concert — Live SessionChannel Two—To complete
- 23:15→ 00:40Tennis — Evening SessionReplay3.5 → 2.5Published
| Start | End | Source | Programme | Gateway port | Network | Channel | Status |
|---|---|---|---|---|---|---|---|
| 13:00 | 15:15 | Feed 3 | Cycling — Spring Classic, stage 4 | 3.2 → 2.2 | Channel One | On air | |
| 15:30 | 16:30 | Studio 2 | Debate — Prime Time | 3.3 → 2.3 | Channel Two | Published | |
| 17:00 | 17:45 | Feed 1 | Magazine — Culture Weekly | 3.1 → 2.1 | Channel One | Published | |
| 18:00 | 18:40 | Studio 1 | Evening News | 3.4 → 2.4 | Channel One | Published | |
| 20:45 | 22:30 | Feed 5 | Concert — Live Session | — | Channel Two | To complete | |
| 23:15 | 00:40 | Feed 2 | Tennis — Evening Session | 3.5 → 2.5 | Replay | Published |
The problem
Your schedule changed after you opened it.
Live operations run on tools that were never meant to talk to each other. The cost is not dramatic — it is daily.
The file goes out as an attachment
From that moment it is a snapshot. Everyone downstream works from the copy they received, and hopes nothing moved.
The same event, typed once per department
Every team re-enters it in its own tool, and each copy drifts a little further from the others.
Nobody can point to the version that counts
When two documents disagree, the argument is settled by whoever spoke last — not by the record.
Your digital teams wait on a manual export
Websites and apps cannot consume a spreadsheet. So somebody re-keys it, late, by hand.
One source of truth
Created once. Completed by the right people. Published when it is ready.
An event exists exactly once in Cadence. Each team fills in the part it owns, and the record is only published when nothing essential is missing — so what leaves the platform can be trusted without a second look.
A validation chain, not an honour system
An incomplete event is visibly flagged and stays unpublished. Nothing ships quietly.
Controlled vocabularies
Fields backed by a reference list accept entries from that list — and nothing else. Typos never become data.
Every change attributed
Who changed what, and when. The record answers the question instead of the meeting.
Live orchestration
From the booking sheet to the signal itself.
Cadence does not stop at planning. It drives the equipment your live chain already runs on, from the same screen your teams schedule in.
Gateway assignment (IP → SDI)
- Cycling — Spring Classic, stage 4Feed 33B → 3.2MainAuto
- Debate — Prime TimeStudio 23C → 3.3MainLocked
- Evening NewsStudio 13A → 3.1MainAuto
- Cycling — Spring Classic, stage 4Feed 32B → 2.2BackupAuto
- Debate — Prime TimeStudio 22C → 2.3BackupAuto
- Evening NewsStudio 12A → 2.1BackupAuto
| Programme | Source | In | Out | Path | Assignment |
|---|---|---|---|---|---|
| Cycling — Spring Classic, stage 4 | Feed 3 | 3B | 3.2 | Main | Auto |
| Debate — Prime Time | Studio 2 | 3C | 3.3 | Main | Locked |
| Evening News | Studio 1 | 3A | 3.1 | Main | Auto |
| Cycling — Spring Classic, stage 4 | Feed 3 | 2B | 2.2 | Backup | Auto |
| Debate — Prime Time | Studio 2 | 2C | 2.3 | Backup | Auto |
| Evening News | Studio 1 | 2A | 2.1 | Backup | Auto |
Resources assigned for you
Encoders and channels are allocated automatically across the day — and any assignment can be locked by hand when the operator knows better.
Main and backup, ready before air
Redundant paths are planned with the event, not improvised when something fails.
Recording without a second tool
Start, stop, and pre-roll margins are part of the event, so the recording matches what was actually planned.
Conflicts surfaced early
Overlaps and missing resources are raised while there is still time to fix them.
The daily plan
The whole day, on one screen — and one screen per team.
Everyone works from the same data, but nobody has to read somebody else's job. Each role gets the view that matches its work: the running order, the technical plan, the newsroom requests, the recordings.
Live countdowns
What is on air, what is next, how long you have.
Handled, and it stays handled
Tasks are ticked, timestamped, and visible to everyone at once.
Notes that never overwrite
Operational notes are appended, never replaced — the history stays readable.
Open by design
Your published schedule, wherever it needs to go.
Validated events are exposed through a documented REST API. Websites, apps, and partners read the same record your teams maintain — with no export, no re-keying, and no delay.
- Documented REST API with an interactive reference
- Only validated events are exposed — never a draft
- Push and pull, so partner systems stay aligned automatically
{
"events": [
{
"title": "Evening News",
"channel": "Channel One",
"startsAt": "2026-03-10T18:00:00Z",
"status": "published"
}
]
}Built for broadcast reality
It runs where your operations run.
Cadence is designed for facilities that cannot depend on the public internet, and for teams that cannot afford a tool that is down when the show is not.
12
Recordings today
Recording = yes
18:00
Next recording
Evening News · CH-04
00:14:32
Starts in
Evening News
6
Peak of the day
Simultaneous recordings
| Start | End | Programme | ||
|---|---|---|---|---|
| 13:00 | 15:15 | Cycling — Spring Classic, stage 4 | Feed 3 | CH-01 |
| 15:30 | 16:30 | Debate — Prime Time | Studio 2 | CH-02 |
| 17:00 | 17:45 | Magazine — Culture Weekly | Feed 1 | CH-03 |
| 18:00 | 18:40 | Evening News | Studio 1 | CH-04 |
On your own infrastructure
Deployed inside your facility. Offline-first by design, not as an option.
Roles, not accounts
People see the views their job needs. Access follows the org chart, not a spreadsheet of permissions.
Built by broadcast engineers
Written by broadcast engineers, for the way live operations actually run — not adapted from a generic project tool.
Made to be lived in
The power of an enterprise system with the pace of a modern product. Dense when it must be, never heavy.
See it against your own schedule.
Thirty minutes, your channels, your kind of day. We will show you what the first week looks like.