Preparing the published article.
Sanctuary AI: Industrial Physical AI and the Phoenix Robotics Roadmap
Vancouver Physical AI developer deploying on existing industrial robots while developing dexterous hands and future humanoids. Separate task-specific proof of concept from Phoenix demonstrations.
Company and current focus
Sanctuary AI, the public brand of Sanctuary Cognitive Systems Corporation, is headquartered in Vancouver, Canada. Its current business focuses on Physical AI for industrial automation across existing and future robotic hardware. This profile is placed with control and AI platforms to reflect that current offering, while retaining the Phoenix humanoid programme as relevant development history.
Industrial deployment strategy
On 17 June 2026, Sanctuary AI announced an expanded strategy to apply its AI to commercial industrial robotic platforms. Its roadmap separates industrial arms with custom end effectors, proprietary hydraulic hands in development, mobile platforms approaching pilots, and future industrial humanoids. These stages should be assessed independently; a deployed industrial-arm application does not establish commercial availability of every later hardware configuration.
Task-specific production evidence
The June announcement describes a proof of concept for inserting flexible wires into moving targets at an unnamed global Tier 1 automotive supplier. Sanctuary reports a task success rate above 99.5% and a 2.54-second cycle against the customer’s production benchmarks. Those figures apply to the reported task and setup. The release does not establish identical performance across arbitrary connectors, conveyors or factory conditions.
Phoenix development history
Sanctuary’s eighth-generation Phoenix announcement describes a wheeled base and changes to cameras, telemetry and the sensor suite for collecting training data. The company connected those changes to faster manufacturing and commissioning. Phoenix should therefore not be described simply as a walking humanoid: buyers and researchers need the generation, mobility configuration and control mode associated with each demonstration.
Pilots and public demonstrations
A historical customer announcement describes a week-long pilot at a Mark’s retail store in Langley, British Columbia, reporting successful completion of 110 retail-related tasks. Separately, the company’s Hannover Messe 2025 account identifies a Gen 8 Phoenix demonstration with Microsoft. A short customer pilot and a trade-show demonstration provide different evidence from sustained production operation; neither establishes an unattended fleet operating continuously at customer sites.
Integration and acceptance questions
For an industrial application, specify the robot brand, end effector, part variability, fixture constraints and the interfaces to existing equipment. Agree task success criteria, recovery behaviour and the treatment of rejected parts before evaluating cycle time. Request a representative trial with changed object positions and production interruptions, and record both autonomous completions and human-assisted recoveries.
Commercial and support scope
Ask the contracting team to distinguish hardware supply, model development, data collection, integration and ongoing support in the proposal. Define who owns collected demonstration data, who approves policy updates and how an unsuccessful update can be reversed. Establish operator training and local maintenance responsibilities for each hardware supplier. Future humanoid or hand development milestones should remain separate from the acceptance obligations for the system ordered today.