Ground truth before heuristics
We build a gold set first, with a held-out part scored once per milestone. Nothing lands in a pipeline layer without a before-and-after row against it.
TKO Ventures builds AI for the physical world. We take footage you already have and turn it into structured, measured data: who was where, when, and what it means. Every system we ship is evaluated against ground truth.
The replay could not load its data.
A 2D court view of the kind our basketball pipeline produces from broadcast video. Dashed lines join each attacker to his nearest defender, and the green ring marks the most open attacker. These possessions are simulated.Explore all eight.
Most of the value in a camera feed is lost between the model and the person who needs an answer. We build the whole path: data, models, evaluation, and the screen someone actually uses.
Detection, segmentation, multi-object tracking, re-identification and reading text in the scene, on footage as it really is: moving cameras, cuts, occlusion, glare.
Camera calibration and per-frame homography put every object on a real-world plane, with units, timestamps and identity, so the output can be counted, compared and audited.
Positions become the insight a person acts on: who was open, where space opened up, what changed between two periods. Each claim links back to the frames behind it.
TKO Ventures is how we take an applied AI idea from a hunch to a measured system. We pick problems where the evidence is already on camera and the people involved have a real decision to make: a coach preparing for next week, an operator planning a shift, an engineer looking for the cause of a failure.
We work with the people who own the problem. We build the full system in the open, with its gold set, metrics and costs kept alongside the code, and we grow the projects that hold up into products. Senior engineering and AI agents work side by side, which keeps the team small, the loop fast and the paperwork honest.
Six rules we follow on every project. Each one exists because ignoring it once cost us time.
We build a gold set first, with a held-out part scored once per milestone. Nothing lands in a pipeline layer without a before-and-after row against it.
Each stage is a backend behind one interface and one config. We compare a new detector, tracker or reader by its measured score, not by our opinion of it.
Production runs on open-weight models fine-tuned on the client's own data. We check every licence before the first download, and closed APIs stay out of the per-frame path.
A working end-to-end demo in days, labelled honestly as automatic and uncorrected. Then the slower work of measuring and improving it, layer by layer.
Agents do the first pass on labelling and review. People correct only what is flagged, in sessions sized to their week. Each correction goes back into the training data.
We run inference locally where we can and use per-second GPU rental for training and CUDA-only stages. We log the cost of every job, so the bill is never a surprise.
An offline pipeline that takes broadcast footage of Polish top-league basketball and puts every player on a 28 × 15 m court, with team, identity and jersey number. It started from public models. The court model is now being fine-tuned hall by hall, and every step is scored against a gold set with a held-out game.
Read the case studyDetect, track, map to a plane, explain. The toolkit behind the basketball work carries over to any place where a fixed or moving camera watches people or objects on a known surface.
Positions, spacing, coverage and workload from broadcast or venue cameras.
Flow, dwell and queueing measured on the floor plan rather than estimated.
Zones, near-misses and throughput on lines and yards that already have cameras.
Counts, trajectories and conflicts at junctions, platforms and car parks.
Tell us what the camera sees and what decision you need to make. We will tell you honestly whether today's models can get you there and what a first measured version would take.