01
Sectors
02
AgentMesh
03
AgentNexus
04
Agentic jobs
05
Hardware
06
Why Unovie
07
Case study
08
FAQ
09
Pilot on your line →
Home/Research/Case study
Case study · Device test automation · 12 months

One year, one platform: AI-driven certification for satellite set-top boxes.

A national satellite pay-TV provider asked us to replace manual set-top box testing with automation they could trust. In twelve months we designed, built and deployed an air-gapped, GPU-accelerated verification platform in their device lab. It presses real remote buttons, watches the real video output, judges what it sees and hands engineers an evidenced verdict. By the end of the year the whole QA team could test at once, the client was building its own vision models in-house, and every result could be read in plain English.

19 / 19
verification features delivered and verified
16
boxes verified in parallel from one 4K stream
0.836 → 0.961
detection mAP after one in-house retrain
16 / 16
boxes per stream with audio certified, up from 0
8
equipment rooms on one rack blueprint
0
bytes of test data leaving the lab
01 — At a glance

The engagement.

ClientNational satellite pay-TV provider (name withheld)
ProblemManual, unrepeatable certification of set-top box firmware across six product lines
DeploymentAir-gapped, on-premise NVIDIA GPU fabric inside the client's device lab
Duration12 months, from first design to lab-wide operation
Design scale128 boxes per rack · 50 racks · 6,400 devices · 300 ms from frame to verdict (design targets)
02 — The problem

A tester, a remote and a screen.

The lab certifies every firmware build for six product lines, each with several versions in test at once. The goal was never to review faster. It was to make exhaustive certification cheaper than sampling.

/manual

Manual and unrepeatable

Coverage was whatever one person could get through in a day, and no two runs were quite the same.

/brittle

Brittle when automated

Earlier tools compared screenshots pixel by pixel. A font tweak or a new promo tile broke the test, so most failures were the tool's fault.

/evidence

Verdicts without evidence

A note in a spreadsheet is a recollection. An annotated proof frame and a log start a different conversation with a developer.

/audio

No audio at scale

One capture stream showed sixteen boxes, but the audio path reached one box at a time, so audio wasn't verified at scale at all.

03 — Why it's hard

Thousands of screens, judged in 300 ms.

Design targetPer streamPer rack (128 boxes)Full build-out (50 racks)
Devices under test161286,400
4K capture streams18400
Device-lane frames per second9607,680384,000
Uncompressed video~6 Gbps~48 Gbps~2.4 Tbps
Capture → verdict300 ms300 ms300 ms

Engineering estimates at 60 fps, 8-bit 4:2:0 video · design targets, not measured

/copy

Moving data is the bottleneck

At terabits per second of decoded video, frames can't be copied through the CPU. Every step has to run in GPU memory.

/time

Failures happen over time

Freeze, macroblocking, stuck splash screens and audio dropouts only show across a sequence of frames.

/matrix

A matrix, not a checklist

Six product lines × several firmware versions: the same check has a different correct answer on each.

/physical

Physical control at scale

Every verdict starts with a real IR keypress. Thousands of remotes need scheduling, with hardware locked so jobs never collide.

04 — What we delivered

An engine, then a platform.

/engine

The verification engine

Drives the remote, reads the screen with detection and OCR, judges A/V health on the GPU and attaches proof frames and a written report to every verdict. Sixteen boxes per 4K stream, sliced on the GPU. Tests are configuration, not code.

19 of 19 featureson schedule
/factory

The model factory

An on-premise path from raw footage to labelled dataset to trained, versioned model. The client now retrains its own detectors: mAP rose from 0.836 to 0.961 in one cycle.

in-house modelsversioned
/channels

Adding a channel is a data task

Channels are matched against a managed library of reference images, so a new or rebranded channel needs a picture, not a retrain. The library rebuilds in under two seconds. Below a confidence margin the answer is “unknown” and a person looks.

no retraininghonest unknown
/scheduling

Lab-wide scheduling

The whole QA team tests at once across 8 equipment rooms, with hardware locked per job, per-user attribution, a full audit trail and inventory synced from the client's own configuration database.

no collisionsaudit trail
/language

A private language layer

Plain-English reports and plain-English test authoring, on separate inference hardware inside the lab. Facts such as channel numbers come from configuration, never from the model.

no cloudno made-up facts
/audio

Audio, from zero to sixteen

Networked control of the audio routing lets one scenario step cycle through every box and check measured signal level, so audio is certified on all sixteen paths.

16 / 16measured signal
05 — Results

After twelve months.

OutcomeWhat changed
Automation the team trustsInterpretation replaced screenshot comparison, so harmless UI changes no longer cause false failures.
Evidence on every verdictPass, fail or partial, each with an annotated proof frame and a per-lane log, one click away.
In-house model ownershipThe client builds, versions and retrains its own models.
Flat cost as the line-up growsNew and rebranded channels take minutes, not a retraining project.
Fails safelyLow-confidence frames return “unknown” and go to a person. The system never guesses.
Data sovereigntyFully air-gapped. No footage, labels, models or results leave the lab.
06 — What carries over

The same discipline, on the factory floor.

This project was in media device testing, not manufacturing. What carries over is how it was engineered.

/vision

Vision QA at the line

GPU video pipelines that judge what they see, not pixel diffs, are the core of our Vision Quality Inspection kit and DeepVision at the cell.

Vision QADeepVision
/evidence

Evidence first

Every verdict carries its proof. In AgentMesh that becomes the signed Evidence Log and the nightly evidence pack.

Evidence Log
/data

Data over retraining

Where the business changes often, the change goes into managed reference data, not model weights. The same idea runs through Vector Memory and the frozen-base doctrine.

Vector Memoryfrozen base
/sovereign

Air-gapped by default

Nothing left the lab. Nothing leaves your site either.

air-gapped

Client details are withheld under confidentiality. Year-one results were measured in the client's lab; scale figures are engineering design targets.

Still checking by hand?

Bring us a line. We'll make exhaustive checks cheaper than sampling.