RoboParty
RoboParty RP1
- Autonomy
- IIAssisted
- Pre-release
- 70/100Plausible
- Readiness
- Not assessed
- Price
- Not tracked
ComparisonRoboParty RP1 and Sanctuary AI Phoenix Gen 8
Sanctuary AI
Sanctuary AI Phoenix Gen 8
- Autonomy
- IIAssisted
- Pre-release
- 37/100Concept Stage
- Readiness
- Not assessed
- Price
- Not tracked
Up to three
Autonomy Ladder
- IManual
- IIAssisted
- IIIConditional
- IVEnvironmental
- VGeneralized
All humanoid robots. Every figure below is placed against the whole class, so a gap can be read against how much the class itself varies.
Where each one suits you.
The conditions each robot was assessed against, side by side. Rows marked in gold are where these machines genuinely differ.
| Condition | RoboParty RP1 | AI Phoenix Gen 8 |
|---|---|---|
| Where it operates | ||
| Home / residentialthey differ | DependsNo consumer home deployment has been announced; RP1 targets labs, classrooms and developer workspaces, not households. | PoorSanctuary has never offered Phoenix for home use; it is an industrial data-capture platform. |
| Office / retail | DependsNo commercial deployment exists yet; RoboParty has described research and development use, not business operations. | DependsNo Gen 8 commercial deployment is documented, and Sanctuary no longer lists Phoenix on its homepage. |
| Warehouse / factorythey differ | PoorRP1 is positioned as a research and development platform; no industrial deployment or ruggedization has been documented. | DependsBuilt with industrial work in mind, but Sanctuary's 2026 factory result used a rival's arm, not Phoenix. |
| Primary tasks | ||
| Household chores | PoorNo household or chore-task capability has been documented; the public demo covered balance recovery only. | PoorNo household task capability is claimed for Phoenix Gen 8 by Sanctuary or in coverage. |
| Social / carethey differ | PoorRoboParty has not documented any social-interaction or companion behavior for RP1. | DependsSanctuary upgraded the audio-video system, but no social or customer-facing deployment is documented. |
| Specialized jobthey differ | GoodBuilt for robotics research and embodied-AI development, with an open stack intended for a team to specialize toward its own project. | DependsSanctuary targets manipulation work, yet no Gen 8 task results have been published. |
| Supervision needs | ||
| Fully autonomous | PoorNo autonomous, unsupervised operation has been documented; the only public demo ran on a staffed show floor. | PoorThe Gen 8 announcement claims no unsupervised task completion; its stated role is data capture. |
| With oversightthey differ | GoodMatches RoboParty's own demonstrated use: a staffed IROS 2026 session with visitors directly interacting with the robot. | DependsSupervised operation fits its data-capture purpose, but no supervised Gen 8 deployment is documented. |
| Teleoperatedthey differ | GoodFits a lab or classroom pilot project, which is the use case RoboParty is building the open stack for. | DependsA pilot would depend on a Sanctuary agreement; none has been announced for Gen 8. |
| Timeline | ||
| Ready today | PoorNo units have shipped to anyone; nothing is available to use today. | PoorNot sold: no price, channel or ship date has been published. |
| Near-term (1–2 yrs)they differ | DependsRoboParty has named a Q4 2026 mass-production target, but with no firm date, price, or confirmed distribution to outside teams. | PoorSanctuary's 2026 focus is licensing its AI for other robots, with no Phoenix sale plan. |
| Research phasethey differ | GoodMatches the platform's stated purpose: an open research and embodied-AI development kit, demonstrated live at IROS 2026. | DependsUseful to follow as a data-capture platform, though Sanctuary has not published Gen 8 results. |
A robot being poor for a condition is a fact about fit, not a fault. “Depends” means the record names a limit worth reading, not that the answer is unknown.
How much the claim can be trusted.
None of these has shipped, so they are assessed on track record, engineering plausibility and how the demonstrations match the claims.
Track Record35% of score
Has this maker shipped what it demoed before, on schedule, with the promised capability?
30
- Sanctuary AI Phoenix Gen 830
28median 66 across 85 pre-release records100
Excluded as unevidenced, so it is left out of the number: RoboParty RP1
Engineering35% of score
Are the demonstrated capabilities achievable in shipping form, or do they need breakthroughs not in evidence?
6850
- RoboParty RP168
- Sanctuary AI Phoenix Gen 850
35median 70 across 95 pre-release records100
Demo Match30% of score
What has been shown to work, against what is claimed in marketing.
7230
- RoboParty RP172
- Sanctuary AI Phoenix Gen 830
30median 66 across 95 pre-release records100
Published beside the number
Never averaged into it. These describe how much the maker has disclosed, not what the machine does.
| RoboParty RP1 | AI Phoenix Gen 8 | |
|---|---|---|
| ReadinessShip-date specificity, pricing transparency, distribution and regulatory status. Published beside the number; never averaged in. | 42/100 | 10/100 |
| DisclosureHow much of the product is disclosed. Higher means fewer fundamental unknowns remain. Published beside the number; never averaged in. | 32/100 | 20/100 |
How far apart is a long way?
A number only means something next to the spread it sits in. Each track is the real range across every classified robot in the class, with the median marked.
These robots share no measured specification with enough published figures to plot. That is a gap in the record, not a finding about the robots.
What the numbers leave out.
Written on each record, and the only thing here every robot on the site carries.
The trade-off
What each design gives up to be good at what it is good at.
RoboParty RP1
RP1 is open by design, but openness is also the only thing proven so far: the IROS demo showed balance recovery, not the manipulation or task-autonomy claims the fuller platform makes.
Building on RP1 today means building on a roadmap, because the motion-control system, simulation environment and SDKs RoboParty calls “full-stack” are still being opened in stages, not shipped complete.
Sanctuary AI Phoenix Gen 8
Each Phoenix generation improved the data it captures, while the company’s newest proof of its AI ran on someone else’s robot.
Who each one is wrong for
Stated by the record itself. A robot being wrong for a household is a fact about fit, not a fault.
RoboParty RP1
- Consumers wanting a household or companion robot
- RoboParty targets researchers, educators and developers; no consumer sales channel, price, or household use case has been announced for RP1.
- Teams needing a supported, production-ready platform today
- RoboParty has named Q4 2026 for mass production with no firm date; nothing has shipped to anyone yet, so there is no delivery timeline a team can commit to now.
- Organizations without in-house robotics engineering support
- An open-source platform assumes the owner can integrate, calibrate and maintain the hardware and software stack directly; no turnkey service or support contract has been described.
- Buyers wanting an established manufacturer track record
- RoboParty was founded in 2025 and RP1 is its first full hardware platform; there is no multi-generation shipping history to weigh.
Sanctuary AI Phoenix Gen 8
- Anyone wanting to buy a humanoid robot
- No price, sale channel or ship date has been published for Phoenix Gen 8, and Sanctuary's homepage no longer lists Phoenix at all.
- Households looking for a home assistant robot
- Sanctuary positions Phoenix as an industrial and data-capture platform; no home use has ever been offered or documented.
- Operators needing unsupervised task completion
- The Gen 8 announcement makes no claim of independent task completion, and no Gen 8 deployment result has been published.
- Buyers who need published specs before committing
- Height, weight, payload and battery figures for Gen 8 are not published by Sanctuary or in the coverage reviewed.
What stays your job
The upkeep ownership hands back to you, whatever the autonomy level says.
RoboParty RP1
- As needed: Actuator and joint inspection after test sessions; no published service interval exists yet.
- As needed: Firmware and PartyOS software updates as RoboParty publishes new releases.
- As needed: Battery charging between sessions; no documented runtime or charge-cycle count has been published.
- As needed: Fastener and cable checks typical of an operator-assembled open hardware platform.
- As needed: Calibration of the Romomo actuator modules following any disassembly or repair.
Sanctuary AI Phoenix Gen 8
- As needed: Sanctuary publishes no owner maintenance schedule for Phoenix Gen 8, which has not been offered for sale.
How much each of these is standing on.
Classifications rest on different depths of evidence. A pre-release assessment and a verified one are not the same kind of claim.
| Robot | Evidence status | Sources reviewed | Last assessed |
|---|---|---|---|
| RoboParty RP1 | Pre-Release | 3 | Oct 2026 |
| Sanctuary AI Phoenix Gen 8 | Pre-Release | 5 | Sep 2026 |
Evidence status counts the sources behind a classification, not their kind. A high count can be maker documentation and price coverage, so read it as how much was reviewed rather than as independent testing. How we weigh evidence.
Keep going.
The full recordRoboParty RP1Specifications, evidence, the Fit Check in full, and every tracked change.
The full recordSanctuary AI Phoenix Gen 8Specifications, evidence, the Fit Check in full, and every tracked change.Robovations classifies robots; it does not rank them. Nothing on this page is a recommendation, and no manufacturer influences a classification or its placement here.
Add a robot
Comparing across classes is allowed — the page will switch to per-class positioning and tell you it has.