Offline machines · In development

Machines that see, hear and reason, entirely offline.

A fleet of robots built around local models. A central server holds the model, the corpus and the archive. Individual units connect to it, and each one enforces its own permissions.

Three steel gears meshed together, teeth interlocking

The server routes. The unit decides.

The central server resolves a destination and forwards a proposal. The destination unit's own authorization gate decides whether it happens. A compromised server can drop, delay or misroute an instruction. It cannot manufacture one.

That split is affordable because the two halves cost very different amounts. Deciding what to do is expensive and happens on the server. Deciding whether it is permitted is a table lookup and happens on the unit.

Offline is a wiring decision, not a setting.

The main model has no network namespace at all. There is no flag to flip and no misconfiguration that quietly restores it. Where outside data is genuinely needed, it arrives through a separate cheap machine that is physically one-way, so nothing routes back.

Each unit proves its identity by signing a challenge rather than presenting an identifier, and the private half of that key never leaves the hardware that holds it.

The platforms

Barty is the flagship: a head, torso and arms unit, and the full-capability platform every other unit is a subset of. Diu is head only, for perception and presence without a body. Ronny flies a signed mission and reports back, carrying no model of its own. Lugh walks out on multiple legs to collect samples. Picky is a stationary gantry that lifts components out of trays with a vacuum nozzle and places them on a circuit board, down to 0402 parts.

Alnita is the long-term end design, a full humanoid where the other lines merge. It is not built and not scheduled, and we would rather say so than imply otherwise.

Code Start a conversation