Every story on air the moment it breaks
News, elections and weather graphics that your designers build once, your rundown drives, and your data keeps current. From the designer's desk to the program output in one file, with nothing rebuilt on the way.
What slows a newsroom's graphics down
A graphic is designed in one application and rebuilt in another for playout. Every change travels the same long road.
New data, a new control or a new rule needs someone who writes code, often in a different team.
Air, the studio touch screen and the website each need their own version of the same graphic.
A last-minute fix goes to air without a way to check it first.
Faster to air, fewer hands, less risk
The file the designer makes is the file that plays. No rebuild, no export for air, no second tool.
The designer wires the data and the operator's controls without code, and one file serves air, touch screens and the web.
Preflight checks a graphic before it airs, versions keep every state to return to, and airZ Engine is measured on its own output.
News, elections, weather
Graphics that follow the rundown
Straps, breaking banners, locators and results boards sit on the stories they belong to. Producers fill in the words, operators take them to air, and a newsroom system can send them through MOS.
- Every word and value is a named field, filled in the rundown or from a live source.
- Each part of a graphic can come on with its own cue, so the desk builds the story as it breaks.
- Operators work from any device on the network.

A whole results desk, live all night
Maps, races, margins, swing and turnout, all driven by the count as it arrives. One scene holds the whole night, from poll closings to the last call, with 3D results walls when the story needs them.
- Every figure is data, so the graphics follow the count without a designer on shift.
- Presenters drive it by touch: a click on a state zooms to its race.
- Explore this election desk live →
A weather wall the presenter drives
Radar, the outlook, an explainer and a storm's path in one scene. The presenter switches views and scrubs through the timeline by touch, on air, and the same scene plays on your website.
- Live data and live video inside the graphic.
- One scene for the studio wall, the program output and the web.
- The scenario shown is illustrative, not a forecast.
Built into the way your station works
Rundowns and MOS
airZ Controller works from rundowns and has a MOS gateway for your newsroom system.
Your sources, by name
Databases, spreadsheets and REST sources fill the graphics; a producer picks the subject, and the values follow.
SDI, NDI and HDR
airZ Engine plays to air over SDI fill and key and NDI, with HLG and PQ HDR per channel.
Automation-ready
airZ Engine takes commands over the network from your automation system, with OSC and health checks for monitoring.
What airs is what you designed
Ray-traced 3D at 1080p59.94 over SDI.
A graphic loaded and warmed up ahead renders its first frame in 9 to 15 ms, against 194 to 299 ms played cold.
The colours your designers pick are the colours that air.
The worst error on HLG output is a tenth of one 10-bit step.
Measured live on airZ Engine with an NVIDIA RTX A4500. How we measure →
Start with one show
Pick a show
A bulletin, an election night or a weather slot: one programme with a clear graphics package.
Build it with your team
We design its graphics with your designers in airZ Editor, wired to your data and your rundown.
Go to air
Your operators run it from airZ Controller and airZ Engine plays it on your outputs.
What broadcasters ask us
Are we locked into airZ?
No. airZ Editor exports one standard runtime file. airZ Engine plays it on air, and the same file plays on touch screens and in a web browser.
Do our designers need to write code?
No. Data binds by name and Animation States handle the logic visually. When a graphic needs more, there is a built-in script editor.
Can operators run it without the designer?
Yes. The designer builds the operator's controls with the graphic. Operators work from rundowns in airZ Controller, on any device on the network.
Does it work with our newsroom system?
airZ Controller has newsroom integration and a MOS gateway, so graphics can be prepared in the rundown and played to air by airZ Engine.
What hardware does it need?
airZ Engine runs on a Windows workstation with an NVIDIA RTX-class graphics card and SDI or NDI outputs. The numbers on this page were measured on an RTX A4500. We recommend the configuration for your channels.
What does it cost?
It depends on your channels, operators and outputs. Tell us about your operation and we will put a proposal together.
See your own graphics on your own outputs
Bring a show, or take one of ours: we will play it through airZ Engine with your data.