RoboParty unveils RP1 at IROS; the full open-source drop is still ahead

What did RoboParty unveil at IROS 2026?

IROS 2026 ran in Pittsburgh. RoboParty’s PR states that RP1’s global debut was 28 September 2026 at the company’s booth, with a later English press release issued 3 October. The robot is also called ROBOTO 01 and is framed as the next step after ROBOTO ORIGIN (RPO), the company’s earlier open humanoid project from January 2026.

The release describes a “Kick Me” interactive demonstration in which visitors pushed and kicked the robot while it recovered balance. Supporting software is attributed to PartyOS and to UFO, an unsupervised reinforcement-learning framework for skill transitions, disturbance recovery, and fall recovery without predefined motion trajectories.

Embodied releases this month span simulation policies and renderers as well as hardware unveilings; for a different open robotics software drop see MirroS AgentGarten’s renderer.

IROS unveilings often mix a show robot, a teaser video, and a promise of later CAD/software drops. RP1 fits that pattern on the pages we opened: hardware presence now, “full open-source” still ahead. Cite the booth materials for what was physically shown, and keep repository empty-states or “coming soon” pages out of the “released” column until tags and licenses appear.

Which hardware numbers are vendor claims?

RoboParty says RP1 delivers peak joint torque up to 160 N·m using in-house Romomo actuator modules and a real-time motion-control system. The PR also mentions a dexterous RP Hand as part of the stack evolving from RPO.

Community scale figures in the same release include more than 2,500 GitHub stars for RPO and a global community of more than 5,000 developers. Those counts are the company’s; we did not audit star history or membership lists.

Founder Yi Huang is quoted saying humanoid robots should not be closed systems only a few teams can build. That is a positioning statement, not a license grant for RP1 binaries.

Degrees of freedom, payload, battery runtime, and walking speed are catalog fields until a third party repeats them on a shared protocol. Ask whether quoted payloads are continuous or peak, whether runtime includes compute, and whether the demo gait was teleoperated. Those distinctions matter more than a single highlight reel.

What is open today versus still promised?

The PR defines “full-stack open source” as more than mechanical files and says RoboParty plans to progressively open motion-control systems, simulation environments, SDKs, training tools, and PartyOS. It also says further RP1 open-source roadmap details will be announced in October 2026, with broader releases and a mass-production program later in Q4.

What we opened on GitHub today: Roboparty/roboto_origin aggregates RPO hardware, ROS2 deploy, training, firmware, and related sub-repos; Roboparty/Party_OS outlines the stack roadmap and links UFO and MimicLite; Roboparty/UFO documents an unsupervised RL framework whose best-tested path is currently Unitree G1, not RP1.

Until RP1-specific packages land, “open-source humanoid” in marketing copy should be read as RPO plus planned RP1 openness—not as a completed RP1 dump on 28 September.

If you are planning a lab purchase around “open humanoid” language, require a license file, a bill of materials, and a bring-up guide before you treat RP1 as a research platform. A promised drop after IROS is not the same object as an Apache/MIT tree with CI. Watch for motor controller firmware and safety PLC documentation—those are usually the long pole, not the STL files.

How does this sit beside other physical-AI work?

World-action and long-horizon robot policies are moving quickly on the model side. NVIDIA’s Long-WAM context work and the Arc reasoning recipe for robot foundation models are software/eval stories, not competitors’ biped unveilings.

Foundation world models aimed at interactive environments remain another track; see Odyssey-3 for a recent world-model launch with its own benchmark caveats.

RP1’s differentiator, if the roadmap ships, would be a higher-torque open biped stack researchers can modify end to end. That outcome is still prospective in the company’s own wording.

Put RP1 next to other IROS-week physical-AI notes on AiLookout—such as Sharpa’s tactile stack and simulation-heavy papers like Arc’s robot reasoning recipe—without collapsing them into one platform. Show robots, tactile skins, and latent world-model papers answer different procurement questions.

What should researchers watch next?

Watch for the October roadmap post and for RP1-tagged repositories that include actuators, control, and training—not only marketing renders. Confirm licenses per sub-repo; Party_OS is GPL-3.0 on GitHub while UFO’s license field needs a file-level read before commercial use.

If you need a trainable humanoid baseline today, RPO’s published sub-repos and UFO’s G1 path are the concrete starting points named in RoboParty’s materials.

Independent video of the IROS “Kick Me” demo from attendees would help separate booth choreography from repeatable recovery policies; we have only the company’s description.

What did we not test?

We did not attend IROS, kick RP1, measure joint torque, or train UFO policies. This article reports the 3 October PR Newswire text, roboparty.com, and the Roboparty GitHub repositories we opened on 10 October 2026.