How to Choose a Humanoid Robot: The 2026 Buyer's Guide

Buying a humanoid robot in 2026 is a different act from buying almost any other machine on this site, because most of what you are shown is a demonstration and most of what you can actually deploy is a pilot. The videos are real, the folding of laundry and the sorting of totes happen, and then you read the fine print: teleoperated, staged, one unit, best take of many. A buyer who mistakes a demo for a product ships a purchase order for a workforce and receives a research platform with a support contract. The gap between what a humanoid can do on a stage and what it can do unattended on your floor for a full shift is the single most important thing to understand before you spend anything.

The order that keeps buyers out of trouble starts with the job and the honesty. First, name the task the robot must do, where it does it, and who stands next to it. Then decide whether you are buying a platform to do research on, a pilot to prove a business case, or a fleet to run production, because those are three different purchases with three different vendors, price models, and risk profiles. A humanoid is a bipedal or wheeled mobile base, two arms, one or two dexterous hands, a sensor head, an onboard compute stack, a battery, and an AI manipulation policy that is improving month to month. You are buying all of that plus a bet on how fast the software gets better, and the software is the part that decides whether the machine earns its keep.

This guide is the hub for the humanoid decision. It segments buyers by what they are actually doing (research labs, warehouse and logistics pilots, manufacturing cells, and consumer or companion use), lays out the specs that decide a purchase and how to trade them off with real ranges, sets honest expectations about pilot-stage maturity, walks the budget tiers and the buy-versus-lease reality that governs most of this market, names the real vendors by category, and covers integration, safety, and total cost of ownership. Throughout it points at the deeper humanoid robot hardware guide and at the live humanoid leaderboard, where you can sort shipping and announced platforms by height, payload, degrees of freedom, runtime, and availability instead of trusting a launch video.

The take: Decide what you are buying before you decide which one. A research platform, a warehouse pilot, a manufacturing cell, and a companion are four different purchases, and the biggest models are sold as a service to pilot partners rather than sold outright at all. Fix the task, the environment, and the person standing next to the robot first. Then be honest that in 2026 a humanoid is a supervised pilot doing a narrow set of tasks, a long way from a drop-in worker, and price the year of integration and babysitting rather than the sticker. The two questions that eliminate the most confusion fastest are "can I even buy this or only lease a pilot" and "does this task really need legs and two hands, or am I buying a form factor for its own sake." Answer those two and the shortlist shrinks to something you can actually deploy.

Companion reading: humanoid robot hardware, how to choose a robot dog / quadruped, how to choose a cobot, how to choose an industrial robot arm, robotics funding & the capital cycle, and reinforcement learning for robotics.

Table of contents

1. Key takeaways
2. Buy the job the robot must do
3. Segment yourself: lab, warehouse, factory, or home
4. The specs that decide a purchase
5. Hands, dexterity, and the manipulation stack
6. Legs vs wheels, runtime, and compute
7. Be honest about maturity: it is a pilot
8. Budget tiers and the buy-vs-lease / RaaS reality
9. The vendor landscape by category
10. Integration, safety, and total cost of ownership
11. A repeatable selection process
12. Frequently asked questions
13. Changelog

Buy the job the robot must do

The humanoid form is seductive, and that is the trap. A machine shaped like a person promises to slot into a world built for people without changing the world, and for some jobs that promise is real. For many others it is an expensive way to do something a simpler robot does better. The first decision is honest and unglamorous: does this task actually need a bipedal, two-armed, human-shaped machine, or are you buying the silhouette.

Legs earn their cost when the environment has stairs, ledges, uneven floors, or human-height reach that you cannot or will not re-engineer. Wheels are cheaper, more stable, more efficient, and fail less, so if your floor is flat, a wheeled base under a humanoid torso, or simply an AMR with an arm, usually wins. Two hands earn their cost when the task genuinely needs bimanual manipulation: holding a box while sealing it, mating two parts, handling flexible material. A great deal of "humanoid" work is one-handed pick and place that a fixed robot arm or a cobot does faster, cheaper, and with a decade of reliability data behind it.

Rule of thumb: If you can bolt the task to the floor, bolt it to the floor. A fixed arm beats a humanoid on cost, speed, uptime, and safety for any job that lives in one spot. Reach for a humanoid only when the job moves through a human-built space that you cannot redesign, and needs hands where a person's hands would go.

The honest use cases for a humanoid in 2026 are narrow: material handling and tote moving in facilities designed around people, machine tending across stations that are spaced for humans, and research into general-purpose manipulation. The aspirational cases (home chores, elder care, general labor) are being demonstrated and piloted, and they are real research, but they are not deployable products you should budget against this year. Match your expectation to the maturity and you will not be disappointed.

Segment yourself: lab, warehouse, factory, or home

Four buyer segments cover almost every humanoid purchase, and each one wants a different machine, buys it a different way, and tolerates a different amount of babysitting. Find yours, then let it set your priorities and your shortlist.

Segment	What dominates the choice	How you acquire it	Realistic 2026 spend	Autonomy expectation
Research / university lab	Open SDK, DOF, community, documentation	Outright purchase	$16k to $150k per unit	You write the policies
Warehouse / logistics pilot	Payload, runtime, uptime, teleop fallback	RaaS / lease / pilot partnership	$10 to $30 /hr or five-figure/yr lease	Supervised, narrow tasks
Manufacturing cell	Repeatability, safety certification, integration	Pilot partnership, later lease	Negotiated program	Fixed-station, supervised
Consumer / companion	Price, safety, voice, quiet, support	Preorder / early purchase	$20k to $30k (mostly unshipped)	Very limited, novelty-stage

Research and university labs want an open platform they can program against rather than a black box that runs a vendor's policy. The deciding factors are a real SDK and ROS 2 support, thorough documentation, high and well-documented degrees of freedom, a community publishing on the same hardware, and a price a grant can absorb. Unitree's G1 and H1 and Fourier's GR series dominate here because you can buy one, own it, and open it up. Repeatability and uptime matter less because a lab tolerates a robot that falls over during an experiment.

Warehouse and logistics pilots are the leading commercial beachhead, and they invert the lab's priorities. Here you want payload and reach for totes and boxes, runtime long enough to cover a shift with a battery plan, and above all reliability and a clean teleoperation fallback for when the autonomy hits a case it cannot handle. You are almost never buying hardware outright; you are signing a Robot-as-a-Service or pilot agreement with Figure, Agility (Digit), Apptronik (Apollo), or 1X, and the vendor keeps ownership and pushes software updates. Judge these on demonstrated uptime and on how the vendor handles the failure cases rather than on the headline demo.

Manufacturing cells want a humanoid that stands at a fixed station and tends a machine or moves parts between two spots, and they care about repeatability, safety certification, and how cleanly the robot integrates with existing line equipment and PLCs. This is the most demanding autonomy environment and the one where a fixed arm most often wins instead, so the humanoid has to justify its mobility. Apptronik, Figure, and Agility are the names running these pilots, usually alongside a manufacturer partner.

Consumer and companion is the most hyped and least shipped segment. 1X (Neo) and Tesla (Optimus) are the visible names, with prices floated in the $20k to $30k range, and the honest status in 2026 is preorders, early units, and heavy teleoperation behind the scenes. If you buy here, buy it as an early-adopter novelty and a bet on the roadmap rather than as an appliance that will fold your laundry unattended next month.

The specs that decide a purchase

Once you know your segment, a handful of numbers do the real work, and each trades against the others. Here is what each spec means and what raising it costs you.

Height and weight. Humanoids run roughly 1.2 to 1.8 meters tall and 30 to 90 kg. Taller and heavier buys reach, payload, and human-scale presence, and it costs you safety margin (a 70 kg machine that falls is dangerous), energy (more mass to move means shorter runtime), and floor risk. For confined or consumer spaces, smaller and lighter is safer and calmer around people. For warehouse lifting, you need the mass to move the mass.

Degrees of freedom (DOF). Total DOF ranges from the mid-20s to well over 40 once you count the hands, and it is a rough proxy for how human-like the motion can be. More DOF buys dexterity and natural motion, and it costs money, weight, wiring complexity, and reliability, because every actuated joint is a thing that can fail and a thing to control. Do not chase DOF for its own sake; a high joint count with a weak manipulation policy is a puppet with many strings and no puppeteer.

Payload. The number that decides whether the robot can do warehouse and logistics work. Whole-body payload runs roughly 5 to 25 kg for current platforms, and per-hand payload is the more honest figure for manipulation, typically 1 to 5 kg per hand while keeping a stable posture. As with any robot, the momentary maximum lift is much higher than the payload you can carry repeatedly through a full motion at speed, so ask for the sustained working payload rather than the hero number.

Runtime and battery. Working runtime in 2026 is short, roughly 2 to 5 hours per charge depending on how hard the robot works, and standby is longer. For anything beyond a single short shift, the battery strategy is a hard spec: hot-swappable packs let a robot keep working while a charged pack goes in, and a fast charge cycle lets you run a charge-and-swap rotation. A humanoid with a bolted-in battery and a long charge is a half-shift machine no matter what the datasheet says.

Onboard compute and the AI stack. This is the spec that actually separates useful from useless, and it is covered in its own section below and in the hardware guide. Briefly: you want to know what onboard compute the robot carries (an NVIDIA Jetson-class module is common for real-time control, sometimes with a heavier module for the learned policies), how much of the intelligence runs on-robot versus in the cloud, and how the manipulation policies are trained and updated.

You want more	You give up	When it is worth it
Payload	Runtime, safety margin, cost	Warehouse, logistics, lifting
Runtime	Payload, weight, cost	Multi-shift, remote sites
DOF / dexterity	Reliability, cost, complexity	Fine assembly, general manipulation
Height / reach	Safety, energy, floor footprint	Human-height shelves, tall machines
Legs (vs wheels)	Reliability, runtime, cost, stability	Stairs, uneven floors, human terrain
Open SDK / hackability	Turnkey autonomy, vendor support	Research, custom tasks
Turnkey vendor policy	Control, lock-in, per-hour cost	Warehouse pilots, fast deployment

War story: A logistics team ran a bake-off between two humanoid pilots and picked the one that lifted 20 kg over the one that lifted 12 kg, reasoning that more payload meant more capable. On the floor the heavier-lifting robot cleared 40 minutes of real work per charge because the lifting drained it, needed two people watching it, and stopped dead on any tote it had not seen in training. The 12 kg robot ran a longer stretch on its battery, handled the messy edge cases through a clean teleop handoff, and moved more totes per shift despite the lower number. Sustained throughput with supervision, rather than peak payload, is what a pilot is measuring.

Hands, dexterity, and the manipulation stack

The hands are where a humanoid's promise lives and where its cost and fragility concentrate. A robot that walks beautifully and cannot reliably grasp a soft bag or a loose part is a very expensive way to move nothing. Weight this subsystem heavily, because it is the least mature part of the whole machine.

Finger count and hand DOF. End effectors range from simple two-finger or three-finger grippers, through under-actuated multi-finger hands, up to full five-finger hands with 15 to 25 degrees of freedom. Simpler hands are far more reliable and cheaper and handle a surprising amount of pick-and-place work; full anthropomorphic hands unlock tool use and fine manipulation and are correspondingly expensive, delicate, and slow to teach. Match the hand to the task rather than buying the most human hand on offer. For the deeper treatment of grippers, see the sibling guide, how to choose a robotic gripper.

Tactile and force sensing. A hand that cannot feel is grasping blind and will crush a soft item or drop a heavy one. Tactile sensors in the fingertips and force sensing at the wrist let the robot modulate grip and detect slip, which is the difference between handling a rigid box and handling a bag of groceries. Tactile sensing is early technology across the industry in 2026, so ask concretely what the hand senses and how the policy uses it rather than accepting "tactile hands" as a checkbox.

The manipulation policy. The software that turns camera and touch input into hand and arm motion is the real product, and it is where vendors genuinely differ. The current approaches lean on learned policies (imitation learning from teleoperated demonstrations and reinforcement learning, covered in the RL for robotics guide) plus a teleoperation fallback for cases the policy cannot handle. The questions that matter: how is a new task taught and how long does it take, how does the robot behave when it is uncertain, and how clean is the human handoff. A vendor who can teach a new task in days and hands off gracefully to a remote operator has a deployable pilot; one who needs a month of engineering per task has a demo.

Rule of thumb: Judge a humanoid by its worst grasp rather than its best. Anyone can film the good take. Ask to see the robot handle the item it fails on, watch how it recovers, and ask how long it took to teach the tasks in the demo. The recovery behavior and the teaching speed tell you whether you are buying a product or a science project.

Legs vs wheels, runtime, and compute

Three coupled decisions (how the robot moves, how long it lasts, and where it thinks) shape the machine more than the marketing does.

Legs vs wheels. Bipedal walking is the headline capability and the biggest source of cost, energy drain, and failure. A biped can climb stairs, step over obstacles, and go anywhere a person can, and it can also fall, which is dangerous and expensive. A wheeled base is cheaper, more stable, more energy-efficient (so runtime is longer), and far less likely to tip, at the price of being stuck on flat, connected floors. Many practical deployments favor a wheeled humanoid torso for exactly this reason, and Agility's Digit and several others deliberately optimize their legs for warehouse walking rather than acrobatics. Buy legs when your environment genuinely has terrain a wheel cannot cross; otherwise wheels do the job with less risk. The quadruped guide, how to choose a robot dog, covers the legged-locomotion tradeoffs in more depth for the four-legged case.

Runtime and the battery plan. Working runtime of 2 to 5 hours means the battery strategy is part of the machine rather than an accessory. For a single short task, a bolted-in battery and overnight charge is fine. For any shift work, you need hot-swappable packs and enough spares to keep one robot running continuously, or a fleet where robots rotate to a charger. Price the batteries and the charging infrastructure into the deployment, because a robot that stops for an hour every two hours has a duty cycle that quietly halves its economics.

Onboard compute. Real-time balance and control run on an onboard real-time computer, commonly an NVIDIA Jetson-class module, while the heavier learned-perception and policy work may run on a second, more powerful module or, in some designs, partly in the cloud. Cloud dependence is a real deployment question: a robot that needs a live connection to think will stall on a spotty warehouse network and raises data and latency concerns. Ask what runs on the robot and what runs off it, and what the robot does when the network drops.

Be honest about maturity: it is a pilot

This is the section that saves buyers the most money, so read it before you get attached to a demo. In 2026 the humanoid industry is in the pilot phase across the board, and the marketing runs several years ahead of the deployable reality. Setting your expectations correctly here is the difference between a successful trial and a written-off purchase order.

The demos are real actions and misleading framing at the same time. When a robot folds laundry or sorts a bin in a launch video, the action happened, and it was very often teleoperated by a human wearing a motion-capture rig, or it was the best of many takes, or it ran in a fixed cell that looks nothing like your floor. None of that is fraud; it is how research capability gets communicated. Your job as a buyer is to translate the demo back into deployment terms: how much of that was autonomous, how repeatable is it, and what happens on the thousandth item instead of the filmed one.

What a 2026 humanoid actually delivers in a good pilot is a narrow set of taught tasks, performed under human supervision, with a remote operator ready to take over on edge cases, on a duty cycle limited by battery and by how often the autonomy needs help. That is genuinely useful for the right task, and it is improving quickly as the manipulation policies get better. It is not a drop-in human worker, it will not learn your whole job by watching, and it needs babysitting for the foreseeable pilots. A buyer who expects the pilot and gets it is happy; one who expects the demo and gets the pilot feels cheated by a machine that is doing exactly what the technology can currently do.

The capital behind the field shapes what you should expect too. Enormous funding is flowing into humanoids in 2026, which is why hardware is improving fast and why some vendors will consolidate or pivot before your pilot pays back. The funding dynamics and what they mean for buyer risk are covered in robotics funding and the capital cycle. The practical takeaway: prefer vendors with a credible path to revenue and a real deployment record, and treat a pilot as a bet that could strand if the vendor does not survive the cycle.

Safety rule: Never let a 70 kg walking machine share space with untrained people on the strength of a demo. Full-size humanoids carry real kinetic energy and current safety standards for them are immature. Insist on a documented safety concept (fall behavior, e-stops, speed and force limits, keep-out zones, human supervision) and treat any vendor who waves this away as disqualified, whatever the robot can do.

Budget tiers and the buy-vs-lease / RaaS reality

Humanoid pricing does not slope smoothly, and a large part of the market is not for sale at all. Understanding how you acquire the robot matters as much as the price, because most flagship platforms are placed with pilot partners under a service model rather than sold outright.

Under $20k: research and consumer units you can buy. Unitree's G1 starts around $16k and its H1 higher, putting an ownable, hackable full-size or near-full-size humanoid in reach of a lab or a serious individual. This is the on-ramp if you want to own hardware and program it yourself. Consumer machines like 1X's Neo and Tesla's Optimus have been floated in the $20k to $30k range, though in 2026 these are largely preorders and early units rather than shipping appliances. Expect to do the integration and to accept early-adopter roughness.

$20k to $150k-plus: research and development platforms. Fourier's GR series and higher-end Unitree configurations, and various research humanoids, sit here, bought outright by universities and corporate R&D labs that want a capable, open platform and can absorb the price. What you get is hardware and an SDK; what you supply is the intelligence and the integration. Boston Dynamics' Atlas sits conceptually at the top of this range as a research and development platform rather than a catalog product.

Robot-as-a-Service and pilot partnerships: the flagship reality. Figure, Apptronik (Apollo), Agility (Digit), 1X, and Sanctuary largely do not sell you a robot to own. They place units with pilot partners under Robot-as-a-Service or partnership terms, keep ownership, push software updates, and charge for the capability delivered. RaaS pricing floated in the market runs roughly $10 to $30 per hour of operation, or a low-to-mid five-figure annual lease per unit, with the vendor handling maintenance and updates. The appeal is that you avoid a large capital outlay, you get continuous software improvement, and the vendor carries the hardware risk in a fast-moving field. The cost is per-hour economics that add up, real vendor lock-in, and less control over the platform.

Tier / model	What you get	What you supply	Best for
Buy < $20k (Unitree, consumer preorders)	Ownable hardware, SDK, roughness	Integration, policies, patience	Labs, early adopters, hobbyist-pro
Buy $20k to $150k+ (Fourier, high-end, Atlas-class)	Capable R&D platform, SDK, support	Intelligence, integration	University and corporate R&D
RaaS $10 to $30/hr or 5-figure/yr lease	Turnkey capability, updates, maintenance	The task, supervision, floor space	Warehouse and manufacturing pilots
Pilot partnership (negotiated)	Co-developed deployment, vendor engineers	Real-world use case, commitment	Flagship logistics / manufacturing

Rule of thumb: If you want to own and program a humanoid today, look at Unitree and Fourier and accept that you are buying a platform to build on. If you want a robot that does a job with the vendor on the hook for the software, you are signing a RaaS or pilot deal with Figure, Agility, Apptronik, or 1X, and you do not own the machine. Match the acquisition model to whether you are doing research or buying a capability.

Sort the humanoid leaderboard by availability, price, and payload to see which platforms you can actually acquire today versus which are demos and preorders, before you build a business case around one.

The vendor landscape by category

Names cluster by what they are building and how you can get one. Knowing the category a vendor sits in tells you more than the spec sheet does, because it tells you how you will acquire the robot and what maturity to expect.

Commercial warehouse and logistics (RaaS / pilot). Figure (Figure 02 and later, running pilots in logistics and pushing a proprietary manipulation stack), Agility Robotics (Digit, the most deployment-focused logistics humanoid, optimized for tote and package handling), Apptronik (Apollo, running manufacturing and logistics pilots with major partners), and 1X (moving from EVE toward Neo) are the core of the commercial push. You engage these through pilots and service agreements rather than a purchase order, and you judge them on deployment record and uptime.

General-purpose and consumer. Tesla (Optimus, ambitious roadmap, aiming at both its own factories and eventually consumers, timeline uncertain), 1X (Neo, aimed at the home), and Sanctuary AI (Phoenix, focused on general-purpose manipulation and the cognitive stack) are chasing the broad general-purpose dream. Treat their consumer timelines as aspirational and their current status as pilot and demonstration.

Research and ownable platforms. Unitree (G1 and H1, the low-cost ownable on-ramp that put humanoids in reach of labs and individuals), Fourier Intelligence (GR series, a popular research and development platform), and Boston Dynamics (Atlas, now electric, the benchmark for dynamic capability and used as a research and development platform rather than sold as product) are where you go to buy hardware you own and program. Unitree and Fourier are the realistic purchase; Atlas is a capability reference and partnership platform.

Manipulation and cognition specialists. Sanctuary and others emphasize the hands and the reasoning stack over locomotion, on the thesis that manipulation intelligence is the bottleneck. This matters if your task is dexterity-heavy rather than mobility-heavy.

Vendor	Platform	Category	How you get one
Figure	Figure 02+	Warehouse / general	Pilot / RaaS
Tesla	Optimus	General / consumer	Aspirational, internal first
1X	Neo / EVE	Consumer / home	Preorder / pilot
Apptronik	Apollo	Manufacturing / logistics	Pilot partnership
Agility	Digit	Warehouse / logistics	RaaS / pilot
Unitree	G1 / H1	Research / ownable	Outright purchase
Boston Dynamics	Atlas (electric)	Research / benchmark	Partnership / R&D
Sanctuary	Phoenix	General / manipulation	Pilot / R&D
Fourier	GR series	Research / R&D	Outright purchase

The landscape will shift as the capital cycle sorts winners from casualties, so weight a vendor's deployment record and funding runway alongside its specs. A slightly less capable robot from a vendor that will still exist and support it in three years beats a spectacular demo from one that will not.

Integration, safety, and total cost of ownership

The robot is the part of the purchase you think about and the smallest part of what it costs to run. What decides whether a humanoid pilot succeeds is the work around it.

Integration. A humanoid does not walk onto your floor and start working. It needs the task defined and taught, the environment assessed and often lightly adapted, the safety concept designed, the network and charging set up, and the teleoperation and monitoring plumbed in. For a warehouse pilot this is weeks to months of work with vendor engineers, and it is where most of the first-year cost and risk sits. Ask the vendor concretely how a new task is onboarded and how much of the integration they do versus you.

Human supervision and teleoperation. In 2026 a deployed humanoid needs people: a remote operator who can take over on edge cases, and on-site staff to reset, recharge, and handle the physical exceptions. The staffing to supervise the robot is a real recurring cost that can rival or exceed the hardware or RaaS line, and it is the cost buyers most often forget. A pilot that needs one supervisor per robot has very different economics from one where an operator oversees several.

Safety and standards. Full-size humanoids sharing space with people is a genuinely unsolved safety problem, and the standards are immature. There is no mature, humanoid-specific functional-safety regime comparable to what exists for cobots and industrial arms, so vendors and integrators are applying existing machinery and collaborative-robot safety thinking (speed and force limiting, e-stops, safety-rated monitored zones, and often simple physical separation from untrained people). Insist on a written safety concept covering fall behavior, emergency stops, force and speed limits, keep-out zones, and the supervision model, and involve your safety people from day one. This is a hard gate rather than a formality.

Total cost of ownership. Price the program over its life rather than the robot at the door. The real number is the hardware or RaaS fee, plus integration and task onboarding, plus batteries and charging infrastructure, plus the supervision and teleoperation staffing, plus the safety review, plus downtime while the robot learns your edge cases. For a pilot, the hardware or per-hour fee is frequently the smaller half of the total. A pilot budgeted only against the sticker or the hourly rate will overrun and look like a failure even when the robot performs as promised.

War story: A manufacturer approved a humanoid pilot against the RaaS hourly rate alone and reported it a failure at review. The robot did its taught task acceptably. The overrun came from everywhere else: two months of integration nobody had scheduled, a full-time person babysitting a single robot, a safety review that paused the line, and a charging setup bought late at a premium. The unbudgeted program around it was the problem, and the robot performed fine. Model the whole program before you sign, and a working pilot will read as a success instead of a surprise.

A repeatable selection process

Put it together into a checklist you can run for any humanoid purchase or pilot.

1. Name the task in one sentence, with the environment and the payload. "Move 10 kg totes between a conveyor and a shelf on a flat warehouse floor" is a spec filter. "A general-purpose worker" is a demo you will regret buying.
2. Test whether it needs a humanoid at all. Could a fixed arm, a cobot, an AMR, or a quadruped do it cheaper and more reliably? If yes, buy that instead.
3. Pick your segment: research platform to own, warehouse or manufacturing pilot to run, or consumer novelty. This sets your acquisition model and your shortlist.
4. Decide buy vs RaaS. Want to own and program: Unitree or Fourier. Want a capability with the vendor on the hook for software: a RaaS or pilot deal with Figure, Agility, Apptronik, or 1X.
5. Rank the two or three specs your task actually needs (payload and runtime for logistics, dexterity and tactile for assembly, open SDK for research) and accept the trades on the rest.
6. Interrogate the manipulation stack and the hands. How is a task taught, how long does it take, how does the robot recover from failure, what do the hands sense. This decides usefulness more than any single number.
7. Set the battery and duty-cycle plan. Confirm hot-swap or a charge rotation if you need more than a short shift, and price the batteries and chargers.
8. Demand a written safety concept and involve your safety team. Fall behavior, e-stops, force and speed limits, keep-out zones, supervision. No document, no deployment.
9. Build the real budget: hardware or RaaS, plus integration, plus supervision and teleop staffing, plus batteries and charging, plus safety review, plus learning-curve downtime. That is the program cost.
10. Shortlist on the leaderboard, filtering by what you can actually acquire today, and see the pilot in person on your own task before you commit, watching the failure cases and the recovery rather than the highlight reel.

Run this in order and you buy a pilot you can defend at review. Skip the "does it need a humanoid" and "is it a pilot or a product" steps and you buy a demo and inherit its gap.

Frequently asked questions

Can I actually buy a humanoid robot in 2026, or only lease one? Both, depending on the vendor. Research and lower-cost platforms from Unitree (from around $16k) and Fourier are sold outright, and consumer machines from 1X and Tesla are in preorder. The commercial flagships from Figure, Agility, Apptronik, and 1X are largely placed with pilot partners under Robot-as-a-Service or partnership terms rather than sold, so you lease the capability and the vendor keeps the hardware. Decide whether you want to own a platform or rent a capability before you shortlist.

How much does a humanoid robot cost? Ownable research units run roughly $16k for a Unitree G1 up through $150k-plus for higher-end research platforms. Commercial deployments are usually priced as a service, floated around $10 to $30 per hour of operation or a low-to-mid five-figure annual lease per unit, with the vendor handling maintenance and updates. Whichever model you pick, the hardware or hourly fee is often the smaller half of the total once you add integration, supervision, and safety costs.

Are humanoid robots actually useful yet, or is it all hype? They are genuinely useful for a narrow set of taught tasks under human supervision, and they are not the general-purpose workers the demos imply. In 2026 a good deployment does specific material-handling or machine-tending work with a remote operator ready to take over edge cases, on a duty cycle limited by battery and autonomy. The technology is improving fast, so expect the useful envelope to widen, but buy against what it does now rather than what the video suggests.

Are the demo videos real? The actions are real; the framing is often misleading. Many impressive clips are teleoperated by a human in a motion-capture rig, or the best of many takes, or staged in a fixed cell unlike a real floor. That is standard for communicating research capability. Translate any demo into deployment terms by asking how much was autonomous, how repeatable it is, and how the robot handles the item it was not trained on.

Do I need legs, or is a wheeled base enough? Wheels are cheaper, more stable, more energy-efficient, and less failure-prone, so if your floor is flat and connected, a wheeled base under a humanoid torso or an AMR with an arm usually wins. Legs earn their cost only when the environment has stairs, ledges, or terrain you cannot re-engineer. Many practical deployments deliberately favor wheeled or warehouse-optimized legged designs for exactly this reliability reason.

How long does a humanoid run on a charge? Working runtime is roughly 2 to 5 hours per charge in 2026, depending on how hard the robot is working, with longer standby. For anything beyond a short shift you need hot-swappable batteries or a fast charge-and-swap rotation, which makes the battery plan a hard spec rather than an accessory. A machine with a bolted-in battery and a long charge cycle is a half-shift robot regardless of the datasheet.

Is it safe to have a humanoid around people? Cautiously, and only with a real safety concept. Full-size humanoids carry significant kinetic energy and can fall, and the safety standards specific to them are immature, so vendors apply existing machinery and collaborative-robot safety practices: force and speed limiting, e-stops, monitored keep-out zones, and often physical separation from untrained people. Insist on a documented safety concept and involve your safety team before any deployment near humans.

Which humanoid is best for a university research lab? An ownable, open platform with a real SDK and community, which in 2026 points to Unitree (G1, H1) and Fourier (GR series) as the practical picks on price and openness. You want documentation, ROS 2 support, and a community publishing on the same hardware more than you want the highest payload or the flashiest demo. Buy the platform you can open up and program, and supply the intelligence yourself.

What separates a good humanoid from a bad one? The manipulation software and the hands, rather than the joint count or the walking demo. Hardware is converging across vendors, so the deciding factors are how well the robot grasps real objects, how it recovers when it fails, how quickly a new task can be taught, and how clean the teleoperation handoff is. Judge a humanoid by its worst grasp and its recovery behavior, and by the vendor's actual deployment record, rather than by its best filmed moment. Sort the leaderboard by the specs your task ranks to build the real shortlist.