Remote and cloud production
Cloud production means the control room runs as software instead of hardware. The cameras stay at the venue. Switching, graphics, data, playout and delivery happen in the cloud, operated from a browser by people who never travelled. LIGR is built this way from ingest to output.
Cloud production is live video production where the production tools run as software in remote data centres instead of as hardware in a room near the pitch. The camera feeds travel to the software. The software never travels to the camera. Everything else is a question of how far you take it.
Remote production, or remote video production, is the broader term, and the two get used interchangeably. They are not identical. Remote video production means the people are not at the venue. Cloud production means the equipment is not at the venue either. Plenty of broadcasters run remote production into a fixed facility packed with traditional hardware, and that is a legitimate model. Cloud production removes the facility too.
The industry term you will meet most often is REMI.
Model 1
Model 2
Model 3
Most operations sit between models two and three. Cloud production does not mean nothing is at the venue: it means the only things left there are the ones that have to be. Our cloud production versus production truck comparison puts the two models side by side on cost, crew, latency and coverage.
A camera has to be where the sport is. A control room does not. The question is which parts of a traditional outside broadcast have to be at the ground, and which are there only by habit.
The cameras
Manned, robotic or AI. A camera has to be where the sport is. Nothing about cloud production changes that.
Audio capture
Effects mics on the pitch, and commentary if your commentators are courtside rather than at home.
An encoder
A hardware appliance, a laptop running OBS or vMix, or an encoder built into an AI camera. Something has to turn light into packets.
Connectivity and power
A connection with reliable sustained upload, not headline download speed. This is the constraint that decides whether a venue is viable.
A pair of hands
Even a fully automated match usually needs someone to mount the camera, switch it on and confirm the feed is live before kick-off.
The truck
With it goes the hire cost, the depreciation, the maintenance, the fuel and the parking negotiation with the ground.
The gallery
Vision mixer, replay servers, multiviewer wall, audio desk and comms. All of it becomes software someone opens in a browser.
The graphics operator
In a truck workflow, a person keys every lower third, every scoreboard update and every sponsor bug by hand. In cloud production the graphics follow the data.
The hardware refresh cycle
No three to five year replacement plan for kit that spends most of its life in a flight case.
Travel
Flights, hotels, per diems, driving time and the crew hours you pay for before anyone touches a camera.
Look closely at what happened to the graphics operator, because it is the part most remote production solutions leave half-finished. Moving the gallery to the cloud without changing how graphics are made just relocates the person keying lower thirds. They now sit in a different building doing the same job at the same cost. The saving is travel, and that is all.
Data-driven graphics remove the job instead of relocating it. If the score changes, the scoreboard updates because the data changed, not because someone noticed. That is the difference between broadcast graphics software that happens to run in a browser and graphics that are actually bound to the match. We wrote up the trade-offs in cloud versus hardware broadcast graphics.
Cloud playout is the transmission end of the chain running as software. The playlist, the live event windows, the channel branding, the interstitials, the overlays and the failover are all scheduled and executed in the cloud instead of by video servers and a master control room. For sport it is the thing that turns a set of individual match streams into a channel: a league OTT destination or a continuous channel that keeps running between fixtures.
It matters because most rights holders do not have a playout problem for one match. They have one for four hundred. Scheduling and branding at that volume is software work, and cloud playout is where the per-match marginal cost of a channel finally drops to something a second-tier competition can afford.
Automation replaces the operator wherever the decision is deterministic. If the ball crosses the line and the score changes, the scoreboard should update, and no judgement is required. If a fixture starts at 15:00, the pre-match sequence rolls at 14:55 because a rule says so. If a goal is timestamped at 63:12, the clip boundaries around it are arithmetic.
AI cameras extend the same logic to framing. Veo, Pixellot, Spiideo and Hudl Focus capture a wide field of view and pan a virtual camera to follow play, which removes the camera operator from a large slice of grassroots and second-tier sport entirely.
Editorial judgement. The reaction shot of a manager who has just lost a two-goal lead. Knowing that the story of the match is the substitute who came on at 70. Handling something nobody scripted, a crowd incident or a serious injury where the correct decision is to cut away immediately.
Automated framing also degrades in poor light, heavy weather and grounds where the camera cannot be mounted high or central. And automation is only ever as good as the data behind it. A scoring app nobody is operating produces graphics that are wrong, confidently and on air. Automation reduces headcount. It does not remove accountability for the feed.
We set out how far the zero-operator model actually stretches in zero-operator sports broadcasting, and the rule engine itself lives in automation.
Cloud production does not delete cost. It moves it, and it changes its shape. That is worth understanding before anyone builds a business case on it, because the savings are real but they do not arrive where people expect.
Truck and hardware capital
Ownership or hire, plus depreciation, maintenance and the refresh cycle on mixers, replay servers and graphics machines.
Travel and crew time
Not just fares and hotels. The billable hours spent getting to a ground and rigging once you are there.
Fixed crew per fixture
You no longer send the same minimum team to a reserve fixture that you send to a final.
Connectivity at every venue
A convenience becomes a hard requirement. Fixed line where you can get it, bonded cellular where you cannot, and a real budget line either way.
An encoder per venue
One-off, and small next to a truck day rate, but it multiplies by the number of grounds you cover rather than the number of matches.
Platform and delivery
A recurring subscription plus the cost of getting the finished streams to the destinations that carry them.
Central technical cover
Someone who can see every venue's feed health during a match window and act when a link degrades.
The important change is not the total. It is the curve. Truck-based production carries a high fixed cost per match that barely varies with how important the match is. Cloud production carries a low fixed cost per match and a modest recurring cost per venue. The more fixtures you cover, the harder that maths favours cloud, which is exactly why remote production reached lower leagues, women's competitions, youth and community sport first. Those fixtures were never going to pay for a truck at any price.
The variable that actually bites is connectivity. Bandwidth stops being an afterthought and becomes the thing that decides whether a ground is coverable at all. Budget for it per venue, test it before the season rather than on the day, and treat a venue survey as part of the production plan. The full truck comparison walks through where each model wins.
Where cloud production loses, so you can decide whether any of it applies to you.
A local hardware chain, camera to mixer to screen, holds end-to-end latency comfortably under half a second and often within a handful of frames. A cloud path cannot match that. You add encode, a transport buffer sized for retransmission, cloud decode, processing, re-encode and delivery. A well tuned contribution leg over SRT can sit in the high hundreds of milliseconds. The full glass-to-glass figure on a delivered stream is normally measured in seconds, and OTT packaging adds more. If your output feeds in-stadium video boards or anything a crowd will compare against what they can see with their own eyes, that gap is real.
Cloud production turns a ground's internet connection into the single point of failure the truck used to carry with it. Bonded cellular, dual carriers, SRT retransmission and a local recording as insurance all help. None of them turn a rural pitch on one contended line into a good venue. Survey connectivity before you commit a competition to remote production.
Cloud replay works. It does not feel the same. An operator scrubbing a jog wheel expects the picture to respond instantly, and any round trip is felt. For high-value officiating review, you still want the frames on local storage next to the person making the call.
Cloud production wins decisively at one to four feeds and high fixture volume. At twelve or sixteen cameras with a talkback-heavy crew and a live director cutting on instinct, the operational overhead climbs and the argument for a truck returns. Most competitions are not that. Some matches in them are.
None of that is an argument against cloud production. It is an argument for matching the model to the fixture. Most rights holders have a small number of matches that deserve a truck and a very large number that currently get nothing at all. Cloud production is how the second group gets covered.
LIGR is remote production software built for sport specifically, rather than a general video tool pointed at a pitch. The chain runs end to end without a gallery.
SRT and RTMP in, with NDI on the roadmap. That covers hardware encoders, OBS, vMix and the AI cameras clubs already own: Veo, Pixellot, Spiideo and Hudl Focus. You do not replace the venue kit to move production to the cloud.
How ingest worksFUSE binds Rive designs to live match data with no code. Scoreboards, lower thirds, team sheets, statistics and sponsor overlays read the match rather than waiting for a keystroke. Change a design once and the next fixture uses it.
FUSEThe LiveScore app gives a scorer real match-event buttons. Every press is timestamped. That single fact is what makes automated statistics and automated highlights possible later without anyone logging a match by hand.
Scoring and dataAutomation rules trigger graphics from match events or from the clock. Pre-match sequence at kick-off minus five. Scoreboard on every goal. Sponsor bug on a rotation. This is where the operator stops being required.
AutomationControl Room is the manual layer over the automation. Open it on a laptop anywhere, watch the feed, fire a graphic, correct a score, take over a sequence. No gallery, no install, no dongle.
Control RoomMulti-stream orchestration sends the same match to several destinations at once with different graphics, languages or sponsors on each. Broadcast, OTT and social do not need three productions.
Multi-stream orchestrationBecause every event carries a timestamp, clip boundaries are arithmetic. Highlights are ready close to full time rather than the following morning, which is when they are still worth posting.
Automated highlightsThe delivery side is documented in output and streaming, and the reasoning behind running several graphicised feeds from one match is in multi-feed orchestration.
Remote production is easy to demonstrate once. Live sports streaming production is judged over a full season, across venues you do not control, in weather you did not choose, every weekend.
More than 650 matches a season, produced remotely across dozens of grounds with no truck at any of them.
Australian rules at national and state level, with automated data-driven graphics running on live feeds.
Rugby league across a state-wide competition footprint, produced from the cloud rather than from a fleet.
Professional tennis, where fixture volume is high, venues are spread across continents and sending a crew to each one is not a plan.
Football Australia runs LIGR across 4,000+ live matches annually, spanning nine State Member Federations. Alongside that sit Basketball NSW, Cricket Tasmania, the Corsican football league, World Sevens Football in Miami, the Horizon League and the EuroMillions Basketball League in Belgium. If you are a rights holder, start at broadcasters. If you produce for other people, start at production companies.
Cloud production is live video production where the switching, graphics, replay, playout and delivery run as software in remote data centres rather than as hardware at the venue. Cameras, audio and an encoder stay at the ground. Everything downstream is operated from a browser by people who never travelled. It is also called cloud video production or live production in the cloud.
Tell us how many fixtures you have, what is already at your grounds and what your connectivity looks like. We will tell you which of them suit cloud production and which do not.
