ArcFlow
Company
Managed Services
Markets
  • News
  • LOG IN
  • GET STARTED

OZ brings Visual Intelligence to physical venues, a managed edge layer that lets real-world environments see, understand, and act in real time.

Talk to us

ArcFlow

  • World Models
  • Sensors

Managed Services

  • OZ VI Venue 1
  • Case Studies

Markets

  • Sports
  • Broadcasting
  • Robotics

Company

  • About
  • Technology
  • Careers
  • Contact

Ready to see it live?

Talk to the OZ team about deploying at your venues, from a single pilot match to a full regional rollout.

Schedule a deployment review

© 2026 OZ. All rights reserved.

LinkedIn
  1. Home
  2. Blog
  3. What Match Day Looks Like with One Person and a Browser

What Match Day Looks Like with One Person and a Browser

Article February 15, 2026

Share this post

The car park is empty. No broadcast truck, no satellite uplink, no crew vans. The gantry is quiet. Six camera pods, permanently mounted, already running. In the stands, the grounds crew finishes the pitch markings, unaware that a production is about to begin. Two hundred kilometers away, a director opens a laptop, loads a browser tab, and checks six green indicators on a system health dashboard. Every camera feed is live. Latency is nominal. In three months of deployment at this venue, the director has seen a red alert exactly once, a network link that diagnosed itself, failed over, recovered, and logged the incident before she could reach for a phone. This is match day with OZ: one person, one browser, and an AI directing engine that handles the 60-decisions-per-second mechanical workload so the director can focus on the only job a machine can't do: telling the story.

Two Hours Before Kickoff#

"The director's first action is a system health check," Sunil says. "They open OZ Studio in their browser (no installed software, no VPN, just a secure login) and the System Health Dashboard loads immediately. Camera pod temperatures, network link quality, GPU utilization, stream health, end-to-end latency. All six camera feeds are live, showing the empty pitch and the grounds crew preparing."

This is the moment that separates managed infrastructure from traditional production. A broadcast crew arriving at a venue two hours before kickoff is beginning their work: cabling, powering up, testing signals, calibrating. An OZ production director arriving two hours before kickoff is verifying that the infrastructure they never need to touch is already running, already calibrated, already producing.

"Every metric has a threshold," Sunil explains. "Green means nominal. Amber means degraded but within operating tolerance. Red means intervention required. In three months of deployment at this venue, the director has seen red once, a network link that recovered automatically within ninety seconds. The system diagnosed the issue, failed over, recovered, and logged the event before the director could have reached for a phone."

The director confirms: six camera feeds live, latency nominal, all systems green. The match is two hours away. Their preparation work begins.

The Director Console#

"The Director Console is where production decisions happen," Sunil says. "It is designed for the same mental model that broadcast directors already use: program and preview outputs, a multi-viewer showing all sources, transition controls, and tally indicators showing which camera is on air."

The multi-viewer displays all six camera angles simultaneously: two wide shots covering the full pitch from opposite sides, two mid-range shots capturing half-field action, and two close-up gimbals with robotic optical zoom capable of isolating individual players from across the pitch.

Below the multi-viewer, program and preview monitors show the current live output and the next queued shot. Transition controls offer cuts, dissolves, and wipes, the same production grammar that directors have used for decades. Tally indicators glow red on the active camera. Everything is familiar. Nothing requires new muscle memory.

"This is deliberate," Sunil says. "We didn't invent a new production paradigm. We implemented the existing one (the paradigm that every broadcast director already knows) and put AI underneath it. The director's hands do the same things they have always done. The difference is what happens between their decisions."

The OZ Action Manager#

Between the director's decisions, the OZ Action Manager is working.

"The Action Manager is the AI directing engine," Sunil explains. "It watches all six camera feeds through the Venue Graph. It knows where every player is, where the ball is, what zone the play is in, what the current game state is, and what the playbook says should happen in this situation. Based on all of that, it selects camera angles, adjusts framing, moves the close-up gimbals to track targets of interest, and queues transitions."

The director sees the Action Manager's recommendations in the preview monitor: the next suggested shot, the reason for the suggestion (ball entering penalty area, counter-attack developing, set piece forming), and a confidence score. The director can accept the suggestion with a single action, override it by selecting a different camera, or switch to full manual control at any moment.

"This is intent-based production," Sunil says. "The director sets the intent ('follow the ball carrier,' 'show the tactical shape,' 'focus on the defensive line') and the Action Manager executes. The AI handles the time-critical, repetitive work: tracking twenty-two moving players, selecting the optimal camera angle sixty times per second, adjusting zoom and framing in real time. The director handles the creative and editorial decisions: when to show emotion, when to hold a wide shot for dramatic effect, when to break from the tactical flow for a reaction shot."

For a production director who has spent years making hundreds of split-second technical decisions per match while simultaneously trying to tell a story, the shift is immediate: the technical decisions are handled. The story decisions remain.

For production directors evaluating OZ: the Action Manager doesn't replace the director. It absorbs the mechanical workload (camera selection, framing, tracking) so the director can focus entirely on storytelling and editorial judgment. Every override is logged, and every logged override improves the AI's understanding of your production preferences. The system learns your style.

Safety Modes: Shadow to Live#

No production team puts an AI in control of a live broadcast without a transition period. OZ's safety mode system makes this transition structured and reversible.

"Every OZ VI Venue starts in twin mode," Sunil says. "The system runs in full simulation (processing all six camera feeds, making all AI decisions, producing a complete virtual program output) but none of it goes to air. The director watches the AI's simulated production alongside their own manual production and compares."

The next step is shadow mode. "In shadow mode, the AI's decisions are visible to the director in real time, but the human makes the final call. Every cut, every camera selection, every transition is the director's decision. The AI's suggestions appear in the preview monitor, and the director can see: would the AI have made the same decision I just made? Over a few matches, the director builds confidence, or identifies specific scenarios where the AI needs playbook refinement."

The final step is live mode. "In live mode, the Action Manager executes. The director monitors and overrides when their editorial judgment disagrees with the AI's selection. The system is designed so that manual override is instant: one action, no delay, no confirmation dialog. The director's override always takes precedence."

"The important thing," Sunil adds, "is that these modes aren't a one-way progression. If a director is uncomfortable with AI directing for a specific high-stakes match, they switch to shadow mode for that match. The infrastructure supports the director's confidence level, not the other way around."

Sunil Kashyap

Sunil Kashyap

Head of OZ Studio Tech Stack

Platform & Product

“We didn't invent a new production paradigm. We implemented the one that every director already knows, and put AI underneath it.”

Replay, Graphics, Audio#

The Director Console is the primary workspace, but OZ Studio includes specialized modules for the production team's other roles.

Replay Workstation. All six camera angles are continuously recorded. The replay operator (or the director, in a lean production) scrubs to any moment in the match and selects the best angle. Frame-accurate in and out points. 4K digital zoom for close-up refinement within the replay. Multi-angle replay packages assembled in seconds. Highlight reels generated from spatial event data. Every goal, every card, every significant tactical moment is already tagged by the Venue Graph.

"In traditional production, the replay operator watches the match and manually tags moments," Sunil says. "With OZ, the moments are already tagged. The Venue Graph detected the goal, the card, the substitution, the corner kick. The replay operator's job shifts from 'find the moment' to 'choose the best angle for the moment.' It is editorial work, not clerical work."

Graphics Panel. Match clocks, scorebugs, lower-thirds, sponsor L-bars, and dynamic statistical overlays. The graphics system is driven by live Venue Graph data. Player statistics update in real time because the spatial tracking is continuous. When a player appears on screen, their name, number, and current match statistics are available without manual lookup.

"Sponsor graphics are particularly important for league economics," Sunil notes. "Every match that OZ produces displays sponsor content with the same consistency and quality as a top-tier broadcast. For a league that previously produced ten percent of its matches, this means sponsors get exposure at every fixture, not just the showcases. The sponsor revenue per match increases because every match looks professional."

Audio Desk. Virtual faders, bus routing, loudness metering, solo and pre-fade listen. Designed for the lean production where the director or a single operator manages audio alongside the visual production. Venue microphones are positioned during installation and mixed through OZ Studio with the same level of control as a dedicated audio console.

The One-Person Production#

This is the part of the walkthrough that production professionals find hardest to believe until they see it.

"A traditional multi-camera football production requires a minimum crew of ten to fifteen people," Sunil says. "Director, vision mixer, camera operators, replay operator, graphics operator, audio engineer, technical director, cable runners. Each person is essential. Each person represents cost: salary, travel, accommodation, per diems."

An OZ production requires one director. The six cameras are controlled by AI. The vision mixing is handled by the Action Manager. The replay moments are pre-tagged. The graphics are data-driven. The audio is pre-configured. One person sits at a laptop, makes editorial decisions, and produces a broadcast that is visually indistinguishable from a full-crew production.

"I want to be precise about this," Sunil says. "I'm not claiming that AI directing is identical to a veteran director with fifteen years of experience and a full crew. A veteran directing a Champions League final will produce artistic decisions that the AI doesn't yet make. What I am saying is that for the ninety percent of matches that currently receive no production at all (because the crew cost makes it impossible) an OZ production delivers broadcast-quality output that serves the fans, the sponsors, the players, and the league. The alternative isn't a full crew. The alternative is no coverage at all."

For league managers, the arithmetic follows directly: if traditional production costs make it possible to produce fifty matches per season, OZ makes it possible to produce five hundred. The cost per match drops by up to ninety percent. Every match receives multi-camera 4K coverage with slow-motion replays, real-time graphics, and AI-driven optical zoom close-ups. The league's content library expands from a fraction of matches to every match.

The question for league managers isn't whether AI-directed production matches a twenty-person Champions League crew. The question is whether it serves the matches that currently receive no coverage at all. For a second-division league, a women's league, or a youth academy, the choice is between OZ production and no production. OZ makes the choice obvious.

After the Final Whistle#

The match ends. The broadcast stream closes. But the OZ VI Venue doesn't stop working.

"Every spatial event from the match is already structured in the Venue Graph," Sunil says. "Highlight packages can be assembled in minutes from pre-tagged events. Post-match statistics are available immediately, not after a human has spent two hours manually tagging footage, but immediately, because the spatial tracking captured everything in real time."

The Spatial API makes this data available to every downstream system the league uses: their website, their social media tools, their analytics platform, their data licensing partners. The match that just ended has already produced its data product.

"And the playbook has already learned," Sunil adds. "Every match refines the AI's understanding of production at this specific venue: the lighting conditions at different times of day, the camera angles that work best for different types of play, the director's override patterns that reveal production preferences the playbook should incorporate. The next match at this venue will be produced better than this one. Not because the director improved. Because the platform did."


This interview is part of the OZ Interview Series, profiling the team building the world model for the physical world.

All InterviewsAll with SunilLearn more about OZ