01Unit OS
One live digital twin of everything inside the unit — racks, power, cooling, network, workloads — and a policy-bounded autonomy engine that keeps it healthy. Every action is simulated on the twin before it runs, is reversible, and is logged. One small remote team can operate many units in many places.
02Workload placement
Decides where each job runs — on the robot, at the edge, in the AlteGen unit, or in the cloud — by latency, data residency, power price, and GPU availability. It is what makes “close to the business” real.
03Robot-serviced unit
An on-board inspection and service robot patrols the unit, confirms what fixed sensors report, finds what they miss, and performs first-line tasks — all directed by and written back to the digital twin. No staff on site.
04Fleet data pipeline
A governed path from a robot or machine to a training-ready dataset: policy applied at capture, encrypted with customer-held keys, store-and-forward across connectivity gaps, processed only in attested enclaves, every access logged.