Company directory
Humanoid Robot Companies: A Tracked Directory (2026)
The humanoid robot companies directory is a source-checked list of businesses developing physical humanoid robots. Humanoid robot companies differ in their robot embodiments, deployment claims and published tactile hardware. This directory records five companies with official product or company sources; inclusion is not a ranking, investment assessment or confirmation of general autonomy.
Last updated:
Published | Updated by RoboSkin.ai Editorial Team
November 4, 2026: rechecked the five company rows, corrected the 1X location to the current official About page and added configuration-specific procurement questions. Documentation review only; no hardware trial.
- 3
- sections
- 2
- questions
- 3
- next routes
5 companies tracked
One row per company with an official humanoid model source. Last verified records the source check, not independent hardware validation. Review is manual after a relevant release or correction.
| Company | Founded | Location | Model | Tactile approach | Official site / sources | Last verified |
|---|---|---|---|---|---|---|
| Agility Robotics | 2015 | Salem, Oregon, United States | Digit; Digit 5 announced, early access expected in 2027 | Detailed tactile sensor architecture: Not published in the reviewed company and Digit 5 announcement | Agility Robotics official site Company history and locations Digit 5 announcement and availability scope | |
| Apptronik | 2016 | Austin, Texas, United States | Apollo | Tactile array specifications: Not published in the reviewed Apollo announcement | Apptronik official site Apollo announcement and company origin | |
| Figure | 2022 | Sunnyvale, California (2023 company announcement; current headquarters not verified) | Figure 03 | Internally developed fingertip tactile sensors; compliant fingertips and separate palm cameras | Figure official site Figure company-issued founding announcement Figure 03 hand and tactile design | |
| 1X | 2014 (originally Halodi Robotics) | San Carlos, California, United States | NEO | Soft lattice covering and tendon-driven actuation described; detailed tactile array specifications: Not published on the reviewed page | 1X official site 1X history and location NEO product and body design | |
| Unitree | 2016 | Hangzhou, China | G1 (selected model) | Dex3-1 hand can optionally include tactile sensor arrays; not standard on every G1 configuration | Unitree official site Unitree registered company information G1 and optional Dex3-1 tactile arrays |
Short answer
What you need to know
- 1
Five companies are currently tracked. Count each company once, even when it lists several robot models.
- 2
Each row links company or product sources and carries a Last verified date. Verification means an editorial source check, not a factory visit or hardware test.
- 3
Review is manual and event-driven when a company, model or sensor release changes. No automatic monitoring or daily revalidation is claimed.
Topic 01
Compare the deliverable configuration, not the company headline
Use the company row to locate a product, then make a separate record for the configuration you would evaluate. Figure’s Figure 03 announcement describes fingertip tactile sensors and separate palm cameras. Unitree’s G1 specification says Dex3-1 tactile arrays are optional. A company-level “has touch” checkbox would hide that difference and would not tell you which signals a customer can access.
Availability also needs a date and a named model. Agility’s September 15, 2026 Digit 5 announcement describes expected early access in the first half of 2027; that is different from the earlier Digit deployments described by the company. Do not carry deployment evidence from one generation into a claim that another is already generally available.
| Decision | Ask for | Keep separate |
|---|---|---|
| Choose a hand configuration | Included and optional sensors, exact hand revision and exposed channels | Dexterity, actuator force control and measured contact arrays |
| Plan software integration | Documented data access, timestamps, commands and supported version | An internal demonstration versus a customer-accessible interface |
| Evaluate autonomy | Task protocol, interventions and remote-assistance conditions | Shown completion versus unassisted repeated operation |
| Plan delivery and maintenance | Current offer, region, configuration, replacement and recalibration process | A future availability statement or factory-capacity target |
Record assistance and contact evidence explicitly
For example, the current NEO page describes scheduled Expert Mode for tasks the robot does not know, in addition to its autonomy claims. Record the operating mode alongside a demonstrated task. A soft lattice cover and tendon actuation describe construction; they do not, on their own, specify a calibrated tactile array.
For a proposed procurement comparison, retain the official source date, configuration identifier, unanswered integration questions and a task-specific acceptance plan. Ask for contact calibration, replaceable surface behavior and synchronized data where those matter to the application. These are buyer questions, not verified performance, a safety approval or an endorsement of any company.
Topic 02
How companies enter the directory
Include a company when an official source identifies a physical humanoid model and the organisation responsible for it. Exclude software-only providers and speculative projects without an identifiable official product source.
Founding year and location are separate claims from product capability. The location field uses the cited company location; it is not an inference about where every robot is manufactured. Not published means the linked source did not establish the requested field.
| Field | Verification rule | Important limit |
|---|---|---|
| Company and model | Official company or product page | An announcement is not proof of customer deployment |
| Founded and location | Company history, contact page or company-issued announcement | A historical office address may not be the present headquarters |
| Tactile approach | Explicitly documented sensors or contact feedback | A soft cover or dexterous hand alone does not prove tactile arrays |
| Last verified | Date the cited page was checked | Does not imply independent testing or automatic monitoring |
Topic 03
Read tactile claims at the model level
A company can sell multiple hand configurations. Optional tactile arrays must stay labelled optional; they cannot be applied to every robot from that vendor. Force control also differs from measuring a spatial contact map.
For integration, request the sensor interface, calibrated range, bandwidth, replacement procedure and controller access for the exact configuration. Compare the published embodiment with the task and dataset before treating a demonstration as transferable evidence.
Common questions
FAQ for this topic
Is this a complete list of humanoid robot companies?
No. It is a five-company tracked directory with explicit inclusion rules and dated sources. It does not claim market coverage or a sales ranking.
Does a published tactile approach prove autonomous manipulation?
No. A sensor specification, a demonstration and a repeatable autonomous task evaluation are different evidence levels.