The review desk
Four feeds, game state and live metrics, run by one operator.
Photographed at a national-level test in March 2025. The on-screen banner is the CritShot call for that delivery.
What the operator sees
Four panels, one screen, one person.
01
Feed manager
Up to four camera feeds in, with the active broadcast angle selected for the model. Thumbnails of every feed run along the top.
02
Video manager
Frame-accurate playback of the delivery under review, so the operator can confirm what the model saw before a call goes to air.
03
Game state manager
Balls, runs and extras for the innings. Game state feeds the shot model: the right shot on ball 3 of over 2 is not the right shot on ball 6 of over 19.
04
Aggression metrics
A live aggression score and run-rate trend for the batter at the crease, updated every delivery and available to the commentary team.
A DRS day today
15 to 20 people on site.
Camera operators, analysts and a truck, travelling with the fixture.
$20,000 to $30,000 a day.
A review day rate runs $20,000 to $30,000 before logistics, and even a stripped-down four-camera setup starts around $12,000 to $15,000.
With Chrio
One machine. $0 in logistics.
Detection, prediction, render and output run on a single workstation at the ground.
What a review day costs, and what it could cost
Three products
Three products read the same camera feed.
One detection pipeline at the ground produces the tracked trajectory. What each product does with it is the difference between them.
Live
CritShot
Renders the shot the batter should have played as a 3D avatar inside the live broadcast, with a difficulty score.
In development
CritDRS
Adjudicates pitching, impact and wickets from the same tracked trajectory, without a dedicated review crew.
In development
CritRate
A 1 to 10 rating for every player, every match, computed from in-game performance as the match runs.
CritDRS · In development
Review decisions from the same feed.
Where the ball landed, relative to the line of the stumps. Reconstructed from the tracked trajectory rather than a single camera angle.
Ball tracking is already built and shared with CritShot; collision detection and multi-view fusion are the current focus.
One pattern, two products
Fan out in parallel, reconcile what comes back, answer under a deadline.
CritShot runs YOLOv8, YOLOv11 and Detectron2 as a parallel consensus ring with SAHI recovery for what the ring misses, and holds 1.5 ms. Dhundo dispatches one query to 136 store adapters across three independent scraper fleets, then reranks what returns in two stages, a bi-encoder for recall then a cross-encoder for precision, so total latency is the slowest store rather than the sum of all of them.
Cricket and commerce are not two businesses that happen to share a founder. They are the same engineering problem answered twice.
The pipeline
Feed in, overlay out, on one workstation.
Six stages run between the camera and the broadcast, at 30 frames per second, on a single machine at the ground.
01
Feed in
The broadcast camera behind the bowler’s arm, over SDI or NDI.
02
Detect
Three detectors vote on every frame; SAHI recovers what they miss.
03
Read
Game state and field placement are read from the same frame.
04
Predict
An LSTM interpolates the trajectory; XGBoost classifies the shot.
05
Render
Blender renders the recommended shot as a 3D avatar.
06
NDI out
The finished overlay leaves the workstation as an NDI stream.
Models trained with TensorFlow and Roboflow, served on Nvidia GPUs, written in Python.
Tooling credits, not partnerships. Detection accuracy on cricket gameplay footage: 98.67%, model V5, September 2025.
Detection accuracy
From 20.95% to 98.67% in twelve months.
Five model versions over a year, each measured the same way. The methodology, the five versions and what the model still gets wrong are published so the number can be checked rather than taken on trust.
For broadcasters
What it takes to run CritShot on your feed.
What comes to the ground, what feed we need from you, what returns to the truck, how long setup takes, who approves what goes to air, and what it costs against a review crew.
Founders
Two students who built a broadcast product before they graduated.
Abdullah Zubair Ghouri
Co-founder
Started Chrio in May 2024, in his second year of computer science at FAST-NUCES Islamabad, after a run of vision-AI hackathon wins convinced him the same models could read a cricket broadcast.
Saffi Muhammad Hashir
Co-founder
The engineer behind everything Chrio ships. He built the real-time cricket analytics stack that runs at 30 frames per second on one GPU, and cut inference latency from 200 ms to 33 ms.
Both founders, the Trans Group partnership and what Chrio has been recognised for
Bring CritShot to your broadcast.
Abdullah Zubair Ghouri, CEO
abdullahzubair@chrio.siteSaffi Muhammad Hashir, CTO
saffimuhammadhashir@chrio.siteIslamabad
Chrio PVT LTD · Plot No. 24-B, Street No. 6, Sector H-9/1, Islamabad, Pakistan