Standard Bodies, Software Moats

Diving deeper into

Fauna Robotics

Company Report
the software and dataset layer becomes the primary moat and hardware bodies become more interchangeable
Analyzed 6 sources

This shifts competition away from who can machine the best robot shell, and toward who can collect the best behavior data and turn it into software that works across many bodies. Once open stacks support common humanoid hardware, the hard part is no longer assembling motors and limbs. The hard part is recording useful demonstrations, training policies that transfer to the real world, and packaging deployment software that makes the robot reliable in a store, classroom, or attraction.

  • LeRobot already supports the Unitree G1, including teleoperation, simulation, and whole body control, and its v0.5.0 release added IsaacLab Arena integration. That means a growing share of core robotics tooling can travel across robot bodies instead of staying tied to one chassis.
  • NVIDIA is pushing the same direction. Its Isaac GR00T platform now supports the Unitree G1, and NVIDIA says a GR00T reference humanoid will be available from Unitree in late 2026. That lowers the cost of adopting a standard body and concentrates differentiation in models, data, and deployment workflow.
  • Hugging Face and Pollen Robotics show the clearest analog. Reachy is not just a robot for sale, it is a node inside a broader open ecosystem of code, datasets, simulation environments, and community contributions. As that ecosystem grows, hardware becomes easier to swap while the data network gets stronger.

The next phase of embodied AI will look more like cloud software than traditional robotics. A small number of bodies will become common developer standards, while value pools move upward into data pipelines, policy training, evaluation, and production software that makes robots perform repeatable work in messy public environments.