RoboParty Opens RP1 Humanoid Designs, From Mechanical Parts to Motion Policies

RoboParty has released an open development stack for RP1 (ROBOTO 01), giving researchers access to humanoid hardware files, control software and motion-learning resources. The announcement follows the robot’s IROS debut, when the company outlined plans for a broader release later in the year.

Key Takeaways

Show all

• RP1’s public repositories span mechanical designs, electronics, robot models and development software.
• The hardware release includes manufacturing files and bills of materials; MimicLite lists motion-policy checkpoints for two RP1 configurations.
• Release contents and licenses vary by component. The announcement does not give a retail price or shipping schedule.

From a demonstration to files developers can use

When we covered RP1’s unveiling at IROS, the broader hardware and software release was still a roadmap item. The new RP1 GitHub hub now connects repositories covering the robot’s structure, electronics, joint modules, firmware, simulation models and training tools.

The hardware repository provides STEP models and drawings for manufactured parts, PCB production files, wiring-harness information and configuration-specific bills of materials. These are useful starting points for teams that want to inspect or modify the physical machine alongside its software.

RoboParty’s argument is that a motion error can originate anywhere from the learned policy to the actuator or mechanical structure. Access across those layers could help developers investigate the cause and test changes on hardware, rather than work around an inaccessible subsystem.

Motion learning and the scope of the release

RoboParty says RP1 has demonstrated continuous walking, disturbance recovery, getting up after a fall and human-motion tracking. It highlights UFO and MimicLite as part of the connection between learning movements and executing them on a robot.

The MimicLite repository lists released policy checkpoints for 24- and 28-degree-of-freedom RP1 configurations, alongside training, data-conversion and deployment resources. Its published comparison plot, however, evaluates a Unitree G1; those results should not be treated as RP1 performance measurements.

The description of a fully open platform also needs to be read at component level. The ROMOMO repository currently identifies its contents as joint-module documentation, specifications, drawings and test materials. It explicitly excludes software and firmware from that repository and refers readers to separately licensed code repositories.

RoboParty-owned hardware designs use CERN-OHL-W-2.0, while the hardware documentation uses CC BY-SA 4.0. Other repositories and third-party materials have their own terms.

For researchers, the immediate development is access to a broader set of engineering resources. Whether outside teams can reproduce RP1’s demonstrated movements—and adapt them to new experiments—will be the practical test of the release.