Blog · Nov 2026
One system, not a stack of parts
Most robots are assembled from components designed in isolation. We think the interesting gains live in the seams between them.
A robot is a chain: motor, gearbox, joint sensor, estimator, controller, policy. When each link is designed by a different team against a spec, the chain is only as good as the loosest interface.
Design across the seams
When the people writing the controller also shape the actuator, they can trade gear ratio for bandwidth, or sensor placement for estimation accuracy. Those trades are invisible from inside a single component.
Iterate hardware like software
That only works if hardware changes are cheap enough to make often. Short build cycles, test rigs that run unattended, and telemetry from every run turn hardware into something you can iterate on weekly, not yearly.