Why rights holders, channel operators and playout partners buy MediaBlaze
Three kinds of customer buy this, and they are not buying the same thing. One has footage and no way to air it, one is doing the work by hand, one is doing it for a roster of clients. Here is what each is actually paying for — honestly, including what MediaBlaze does not do for you.
You hold the rights, not a newsroom
You have a sports, business or regional rights deal and a distribution slot waiting, and between them a gap the size of a production department. Hiring one is the obvious answer and the reason most of these channels never launch.
- The wire is the newsroom. If you hold an AP, AFP or Reuters contract, the material to fill a schedule is already arriving. MediaBlaze is what turns it into segments.
- One person can run it. The pipeline needs an operator who can write a shot list and judge a script — not a crew of editors, writers and voice talent.
- Editorial control stays with you, because you write the shot list the script is built from and you approve every clip.
- Your rights stay yours. MediaBlaze never licences, resells or redistributes agency material.
What it doesn't do: get you the rights, get you the slot, or decide what your channel is about.
And if you do already run a newsroom, you have other options — a good few tools now repurpose a newscast you are already making. This is built for the case where there is no newscast, and the wire is the only source you have.
You're already running the channel — by hand
The channel exists. Somebody's whole week is downloading from three agency portals, pasting shot lists into a chat window, running the result through a voice tool, splicing it in a consumer editor, exporting, and pushing the file at a broadcaster.
- It is the same tools, joined up. A wire, a language model, a voice engine and a timeline — except the handoffs are gone, and so is the copy-paste.
- The clip keeps its context. Origin, shot list, script, voiceover, breaks and delivery state all live on the asset, so nothing is reconstructed from a filename.
- Batches state what they will do first — how many clips will run, and every one that will be skipped, with the reason.
- Delivery stops being a leap of faith: a timed log per package, and a failure that names its step.
What it doesn't do: replace a finishing editor. Complex cuts still belong in Premiere — which is why there's an AAF export.
You run channels for other people
Playout partners, channel-as-a-service shops and integrators: your problem is not one channel, it is margin across a roster of them, and the blast radius when one client's credentials touch another's content.
- The team is the boundary. Agency credentials, AI keys, delivery target, assets, packages and feed are all per team. Another client's wires are not yours, and yours are not theirs.
- Each client pays for their own AI. Script provider and key are per team, and the cost ledger records which account was actually billed for each run.
- Roles, invitations and revocation — admin and member, with access you can withdraw.
- Integration certainty over AI claims. Delivery is into Amagi CLOUDPORT ingest with an MRSS feed carrying cue points — a shape you can check against your own pipeline before you commit.
Worth knowing up front: some multi-team handling around delivery targets is still being finished. If you're evaluating for a roster, ask — we'll tell you exactly where that stands.