Relling Systems ↗

Skipped outright on phones and data saver, warmed only when the browser is idle, booted by an observer while still a screen away. Three.js is self-hosted: the CDN copy kept dying on phone ad blockers.

Each one pre-steps about two seconds before its first frame is shown, so it fades in on a settled pose. The camera reframes by aspect: wide is the whole bench, narrow crops to the handoff.

Spec’d and assembled the compute units, including NVIDIA Jetson modules sized to run perception and video inference at the cell rather than in a datacentre. Bench-built, burned in, and racked as part of the cell instead of arriving as somebody else’s black box.

Ran the harnessing and the routing: arm, sensing, tooling, safety and compute wired into one unit that a shop can power on. The parts of a deployment nobody photographs and everybody feels when they are done badly.

Live video capture and training run on site, on the customer’s own hardware, behind their boundary. That is a hardware decision before it is a software one: enough compute at the edge that nothing has to be shipped out to be useful.

Defense and controlled work cannot send footage of a line to a cloud. Keeping capture, storage and inference inside the facility is what lets a buyer with ITAR obligations get past the first question and actually evaluate the cell.

Small leader arms assembled from an open kit: servos, linkages, the handle an operator grips. Cheap enough to build several, which matters when the point is collecting hours of data rather than owning one perfect rig.

Bimanual stands so one operator drives two arms at once. Most of the work worth automating takes two hands, and a rig that only captures one teaches the model half a task.

The driver and control loop that turn a stand of servos into something an operator can feel through: low latency, live scene state, and precision tight enough that contact-rich work stays legible instead of turning into a fight.

Sessions record to MCAP logs, the format the policy training reads. Everything above exists so that file is clean: if the capture is wrong, the hardware and the interface were wrong first.