Let's meet at NAB Las Vegas, Booth N1867!

Book your meeting

Cuez Blockz: the shared repository to centralize control over your entire broadcasting infrastructure

Looking to gain centralized control over your broadcasting infrastructure? A shared repository is exactly what the industry has been asking for. The technology exists, it’s called Blockz, and this is the core idea.

Store once,
Reuse every show.

Your automation and rundown building blocks, centralised in the cloud. Change once. Deploy when you’re ready. Update everywhere.

You’ve built it already
many times over.


Every automation engineer knows the feeling. You build a cue block for the show open. It works. Then you rebuild it for the next show. And the one after that.

Then something changes. A graphics template gets updated. A new standard gets rolled out. And suddenly you’re hunting through every rundown, making the same edit twelve times over.

That’s not automation. That’s manual work in disguise.

“Change a block once. Deploy when you’re ready. It updates in every show immediately — everywhere, at once.”

– Jan De Wever
Product Owner of Cuez Automator 

What Blockz does

Blockz is a centralised cloud library for Cuez building blocks. Store any cue block once. Use it across any number of shows and channels. When you update it in the library, every show that references it gets the change — when you choose to deploy it.

No more copy-paste. No more “which version is this?” No more chasing down 20 rundowns when one template changes.

Blockz works across any NRCS. MOS-based systems like iNews or ENPS, or Cuez’s own rundown — it doesn’t matter. Your blocks live in the cloud, not inside a specific system. Switch NRCS and everything moves with you.

Centralised library

All your automation blocks live in one place. Organised, searchable, version-controlled.

Controlled deployment

Update a block, then deploy when you’re ready. Every show using it gets the change — on your schedule.

Works with any NRCS

MOS-based systems, Cuez Rundown — Blockz works across all of them. Switch NRCS and your blocks come with you.

Consistency at scale

One standard across every show, every channel, every platform. Without the overhead.

 

Before and after

Without Blockz
– Rebuild blocks per show
– Manual updates across every rundown
– Version drift between shows
– No single source of truth
– Blocks tied to one specific NRCS
– Engineering bottleneck on every change
With Blockz
– Build once, reuse everywhere
– One change, deployed on your terms
– Every show runs the same block
– Central library, always current
– Works with any NRCS — switch and your blocks follow
– Engineering stays in control

 

Built for the people
who run the show

Automation engineers control the library. They decide what goes in, what gets updated, and what gets retired. No more chasing down every producer when a standard changes.

News directors and producers always work with the latest version. The block in the rundown is the right one. Always.

The biggest broadcasters run dozens of shows a day. Blockz keeps every one of them consistent — without the overhead that normally comes with scale.

See Blockz in action

Talk to us about how Blockz fits into your broadcast automation stack. Request your demo below.