LIGR Pro/FUSE
The broadcast graphics builder
Your designer's file goes in. A graphic that reads the match, holds its own logic and publishes straight to your theme comes out, without writing code.
Where a graphic gets its logic
A Rive file is a beautiful animation with nothing behind it. FUSE is where it becomes a broadcast graphic: every field pointed at live match data, the logic for what shows and when, and the handful of things you want an operator to be able to change on air.
It is also where the boundary gets set. What the operator can touch is decided here, once, by whoever built the graphic, which is what stops a brand getting broken live.
01
Rive
Your designer draws and animates the graphic, with its states and transitions.
02
FUSE
The file is dropped in. Every field becomes a binding, and you decide what drives it.
03
Theme
Publish a version. The graphic joins the theme your competition runs on.
04
Control Room
The operator sees exactly the control variables FUSE exposed, and nothing else.
Building one, start to finish
Four steps between a designer's file and a graphic that runs itself.
01
Drop in the Rive file
Create a new graphic in the theme and drag the file across from your designer. FUSE reads it and lists every field it can drive.
FUSE. The file, its size and graphic type, with the animation on the canvas. 02
Bind the fields
Point each target at what should fill it. Hard text where it never changes, an expression where it does. Load a real match ID and the graphic fills with that fixture while you work, so you are not building against dummy data.
FUSE › data bindings. Each target field with its expression and the value it computes from the match. 03
Add control variables
Anything the operator should be able to change becomes a control variable. A kick-off time you do not always know, a team toggle, a colour inversion for a white-on-white kit. Set the type and the default, and it appears in Control Room.
FUSE › control variables. Each with its type and the default an operator starts from. 04
Connect external data
For anything the match feed does not carry, such as a ladder, a route to the final or a rundown, add an external data source. Upload a sheet or paste the rows, and every bound field updates with it.

A bracket graphic from the Australia Cup package, rendered with generic clubs.
What you can drive
Data bindings
Every field in the Rive file appears as a target. Bind it to hard text, to live match data, or to an external source.
Expressions
Compute the value rather than typing it. Uppercase a competition name, filter stats to a set, fall back when a field is empty.
Control variables
Decide what the operator can change on air. Boolean, string, number, team, player, round or set, each with a default.
External data sources
Ladders, brackets, rundowns. Upload a file or paste the rows straight in, publish, and the graphic reads from it.
Player data and images
Squad data and player imagery bound to the graphic, so a name change or a new headshot does not mean a rebuild.
Scenarios
Step the graphic through its states against real match data before you publish, rather than finding out on air.
Expressions are just text
Expressions export to a plain text file. That sounds small, and it is the single biggest time-saver in the tool.
Moving a graphic between themes stops being a rebuild. Export from one, import into the other, and sense-check the fields that differ. Because it is just text, bulk changes are a find-and-replace rather than an afternoon: filter every stat to a set instead of the whole match, uppercase every text field, swap a data source across forty bindings. Edit it by hand or hand it to an LLM, then import it back and check what it changed.
Light or dark
Designers live in this tool for hours at a time, often in a gallery or a truck where a white screen is the last thing anyone wants. FUSE runs in either theme.
Client packages on air
Packages for the Australian Championship, the NPL and the Australia Cup, rendered from their production Rive files with generic clubs.
See custom broadcast packagesWatch it work
From a designer's file to air
A custom package on LIGR Pro: drawn in Rive, bound in FUSE, connected to the data, published to the theme and run live.
1:32, with sound.
Questions
FUSE is the LIGR broadcast graphics builder. You import a Rive file, bind its fields to live match data with expressions, expose control variables to operators, and publish the result as a theme.
Where FUSE fits
FUSE is part of LIGR Pro. Studio runs on the theme library: pick a theme, set your look, go live. FUSE is for when the graphic needs to hold logic that a theme cannot, meaning your own Rive files, your own data and your own rules about what shows when.
Graphics
The module FUSE publishes into, with the theme library every Studio plan runs on.
See broadcast graphicsControl Room
Where the control variables you expose end up, for whoever is running the match.
See the Control RoomCustom broadcast packages
Client work built this way, from the first Rive file to the graphics on air.
See the packagesLIGR Pro
FUSE is part of LIGR Pro, with data integrations, multiple feeds per match and managed support.
See LIGR ProPut your next match on air
Tell us about your competition and we’ll show you how it looks with LIGR.