Review the subsystem interfaces before selecting a quote path.
Humanoid projects usually combine compact joint actuation, reducers and encoders, moving servo harnesses, lightweight links, hand or end-effector interfaces, multi-camera sensing and high-density host compute.
Core Hardware Subsystems
Frameless torque motors, servos and joint drives
Strain wave reducers, bearings, encoders and brakes
Dynamic servo, encoder and power harness routing
Carbon fiber or lightweight frame and link structures
Hands, grippers and end-effector adapters
Head, torso and body camera or depth sensor stack
Jetson Orin or x86 host compute with controlled CAD/STEP
ENGINEERING FILES / CONTROLLED ACCESS NOTES
Public previews can support early screening, but original STEP/STP files, complete drawings, internal BOMs and supplier-sensitive records require controlled access review through RFQ. Application pages prepare that context; they do not auto-release engineering files.
Humanoid file requests should name the joint, link, hand, sensor or host interface involved and state whether the decision concerns envelope, mounting, routing, mass, thermal path or connector access.
Camera or depth sensor type, GMSL2 / Ethernet, host platform, SDK and mounting location.
Procurement Fit
Choose the path that matches the decision currently blocking the project.
Catalog
Use Products for defined frameless motors, servo motors, reducers, encoders or force sensors when the joint envelope and performance targets are already known.
Custom Build
Use Custom Builds for moving joint harnesses, carbon fiber links, lightweight structures, tooling adapters or host-to-sensor interface hardware shaped by the robot geometry.
Integration Package
Use an Integration Package when joint drive, sensing, host compute, teleoperation or electrical interfaces must be reviewed as a coordinated humanoid subsystem.
Engineering Files
Use Engineering Files for motor/reducer drawings, joint envelopes, STEP/STP, link CAD, pinouts, interface maps and supplier-controlled documents needed for packaging review.
Total Degrees of Freedom (DoF), joint count, torque, speed and duty targets
Hollow-shaft joint routing, joint envelope and high-density cable path constraints
Harmonic drive size or reducer size, if supplied
Motor power bus separation from absolute encoder feedback
Encoder feedback protocol: SSI, BiSS-C, incremental or absolute
Dexterous hand payload, wrist payload and end-effector interface
EtherCAT, CANopen, RS485 or other communication context
Required input context
EMI cross-talk isolation mapping in hollow-shaft joint spaces
Motor, reducer, encoder, brake and bearing concept
Camera, depth, force, hand and host compute stack
Required joint drawings, link CAD, STEP/STP or interface files
Not the right path if
This page does not imply full humanoid system delivery, locomotion control validation, balance algorithm validation or certified safety performance.
EmbodyStack does not guarantee humanoid safety certification; balance, locomotion, fall safety and final system validation remain customer responsibilities.
After submission
Separate catalog-ready joint components from geometry-dependent custom builds.
Identify missing motor, reducer, harness, sensor, host and CAD interfaces.
Define the engineering package and controlled files needed for the next prototype review.
Application RFQ
Start with the information already available.
Route this request here when humanoid joint packaging, hollow-shaft cable routing, lightweight frame constraints, sensor stack, hands or host compute must be reviewed together before RFQ.