Hardware-Software Decoupling

The robot's intelligence isn't tied to one specific hardware platform, and can run on different robots.

Hardware-software decoupling means developing a robot's “brain” (the perception and decision-making model and software) separately from its “embodiment” (mechanical structure, motors, sensors), with the model adapting to multiple robots through a unified interface, while the hardware can also be paired with models from different vendors. This is the business premise behind “brain” companies: building only the model, not a complete robot, and training a general-purpose policy on cross-embodiment data. The opposite is hardware-software integration, where one company designs both the hardware and the model together and deeply co-optimizes them. Proponents of decoupling value scale and reuse; skeptics argue control performance can't be separated from deep knowledge of the specific hardware.

ExamplePhysical Intelligence doesn't build robots itself; its π0 model is trained on data from robots with many different configurations, and can control single-arm, dual-arm, and mobile robots alike.

Also called

Model–Embodiment Decoupling

Related

Robot-Brain (Model-Only) Company · Hardware-Software Integration · One Brain, Multiple Robots · Cross-Embodiment · Embodiment-agnostic

Sources

π0: A Vision-Language-Action Flow Model for General Robot Control (arXiv)