Broadcast operations software
Every live event. One source of truth.
Cadence is the operations software for television channels running live. 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.
Deployed in your facility · No cloud · No internet dependency
Paris time13:04:12| Start | End | Title | ||||
|---|---|---|---|---|---|---|
| 13:00 | 15:15 | Cycling · Spring Classic, stage 4 | Channel One | Sport | Published | On air |
| 15:30 | 16:30 | Debate · Prime Time | Channel Two | Talk | Published | Upcoming |
| 17:00 | 17:45 | Magazine · Culture Weekly | Channel One | Culture | Published | Upcoming |
| 18:00 | 18:40 | Evening News | Channel One | News | Published | Upcoming |
| 20:45 | 22:30 | Concert · Live Session | Channel Two | Music | To complete | Upcoming |
| 23:15 | 00:40 | Tennis · Evening Session | Replay | Sport | Published | Upcoming |
One place to run it all.
The problem
Your schedule changed after you opened it.
In most television channels, 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. What leaves the platform can be trusted without a second look.
- 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 |
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 broadcast equipment your live chain already runs on, from the same screen your teams schedule in.
Signal path · synthesis of the day
Shared resources: the paths follow one another, they do not overlap.
- Feed 3SwitcherChannel One
- Studio 2SwitcherChannel Two
- Studio 1SwitcherRecording
- Gateway A · MainGateway B · Backup
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 on-air running order, the technical plan, the newsroom requests, the recordings.
- Cycling · Spring Classic, stage 4SportChannel One13:00Live
- Magazine · Culture WeeklyCultureChannel One17:00
- Evening NewsNewsChannel One18:00
- Debate · Prime TimeTalkChannel Two15:30
- Concert · Live SessionMusicChannel Two20:45
- Tennis · Evening SessionSportReplay23:15
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, so the history stays readable.
Who works in it
Six teams, one record, six ways of reading it.
Nobody has to learn somebody else's job to do their own. From scheduling to the control room, each role opens the view that matches the work in front of them, and they are all looking at the same data.
Scheduling
Creates the event once.
Fills in what it owns, sees at a glance what is still missing before the record can be published.
Signal engineering
Sees the day as resources.
Encoders, channels, main and backup paths, assigned automatically and locked by hand when judgement beats the rule.
Newsroom
Asks, and follows the answer.
Requests go to the right desk with the right context, and their status is visible without a phone call.
Operations
Runs the day.
The running order, live countdowns, what is handled and what is not, updated for everyone at the same second.
Digital
Consumes, never re-keys.
Reads validated events through the API. No export, no copy-paste, no waiting for somebody to send the file.
Management
Reads the record, not the room.
Who changed what and when, which events are complete, where the day is under strain.
Open by design
Your published schedule, wherever it needs to go.
Your validated broadcast schedule is 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"
}
]
}Integrations
It plugs into what you already run.
Cadence never talks to a device directly. It states what it needs, start a recording, route a source, publish a schedule, and whatever you already own answers behind that contract. Changing switcher brand means changing one adapter, not changing software.
Video routing
The right source on the right port, at the time that was planned.
Transport gateways
Contribution and distribution, from IP input to SDI output.
Recording system
Start, stop and safety margins driven from the event itself.
Channel traffic system
The commercial schedule comes in without being retyped.
Rights and programme catalogue
What you are allowed to broadcast, and until when.
Playout playlist
What goes to air follows what was actually published.
Media processing chain
Encoding, automated editing, file delivery.
Media library and storage
Files land where your teams already look for them.
Mail and directory
Notifications leave your own server; accounts follow your directory.
As-run logs, subtitling, remote commentary, audience measurement: the list is not closed. A system that is not on it plugs in the same way, without touching anything else.
The architecture
- A contract, not a brandThe core describes what it expects from a recorder or a router. Which brand answers behind it is none of its business.
- Every connector switches offA system you do not own is simply not registered. Nothing degrades, nothing stays half configured.
- No silent failureA command a device refuses is reported and timestamped, and replays without recreating the event.
What Cadence is not.
- Not an editing suite.You edit where you already edit. Cadence triggers the processing and knows where the file lands.
- Not playout.It does not put the signal to air. It brings the right source to the right port at the right time, and declares what is coming.
- Not a media library.It does not store your media and does not replace your catalogue. It references, it does not keep.
- Not your traffic system.Sales and commercial breaks stay where they are. Cadence reads the schedule, it does not sell it.
Cadence feeds and drives these systems. It does not replace them. That is exactly why it goes in without a rebuild.
Sovereignty
Your on-air data never leaves your walls.
Cadence is French software, deployed on your own infrastructure. No shared hosting, no third-party account to open, no transfer outside your network. The day your internet link drops, the control room keeps working.
French software
Designed, written and maintained in France, by a team you can get on the phone. No vendor ten time zones away, no support that wakes up when you go to bed.
Inside your walls
Installed on your servers, in your own machine room. You keep control of the backups, the access and the upgrade calendar, including the right not to upgrade during a season.
GDPR by design
No personal data goes to a third-party service, so there is no transfer outside the European Union to document. The processing register fits on one page.
Offline-first by design
Not a degraded mode: the architecture. Cadence never assumes the internet is available, because a control room cannot assume it either.
No telemetry, no usage statistics sent back to us. What your channel puts to air is nobody's business but yours.
Built for broadcast reality
It runs where your operations run.
Cadence is designed for broadcast facilities and control rooms 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.