I have had four versions of this conversation in the last six months, and they all open the same way: someone's plant has committed to a humanoid, the demo video looked friendly, and now the safety lead is quietly working out what the auditor will ask. The good news is that the answer is less exotic than the robot. You are not buying a new category of safety device. You are building a robot cell, and a robot cell has a well-worn safeguarding recipe.
What makes the humanoid case interesting is the one residual risk that a bolted-down arm does not have, and the fact that the standard written for exactly that risk is not finished. So let us start with what is real on the floor right now, then go device by device.
Are humanoids actually doing this work, or is it all demo footage?
Both, which is why the safeguarding question is live rather than hypothetical. A handful of deployments are genuinely industrial, and they are useful reference points — treated here strictly as public news, not as performance claims about anyone's hardware.
- Figure 02 at BMW Spartanburg. Figure AI reports a roughly eleven-month deployment on an active assembly line at BMW Manufacturing in Spartanburg, South Carolina, contributing to production of more than 30,000 X3 vehicles — per Figure, the robots loaded over 90,000 sheet-metal parts across about 1,250 operational hours on weekday shifts (figure.ai).
- Agility Digit at GXO. Agility Robotics' Digit went live at a GXO Logistics facility near Atlanta on 5 June 2024 under the industry's first humanoid Robots-as-a-Service agreement, and in November 2025 Agility announced Digit had moved over 100,000 totes in that live commercial deployment — picking totes on and off AMRs, loading conveyors, stacking containers (agilityrobotics.com).
- BMW Plant Leipzig. BMW Group announced in November 2025 it would deploy humanoid robots in production in Germany for the first time, using the AEON robot from Hexagon, with an initial test in December 2025, further testing from April 2026 and a pilot phase starting in summer 2026 for high-voltage battery assembly (press.bmwgroup.com).
- Tesla Optimus. Tesla has deployed Optimus units inside its own Gigafactory Texas and Fremont plants and, as of early 2026, was scaling production, with a stated long-term ambition of up to roughly 10 million robots a year. A verified count of units actually on production lines was not officially disclosed — treat the large figures circulating on secondary blogs as unverified.
Notice the common thread: every one of these runs inside a defined, safeguarded work zone. None of them is a humanoid wandering loose among untrained staff. That is not timidity — it is the only configuration today's published standards can support.
What is ISO 25785-1, and why can't I lean on it yet?
ISO 25785-1 is the first ISO standard aimed squarely at the kind of robot you just bought. Its full title is “Robotics — Safety requirements for dynamically stable industrial mobile robots (legged, wheeled, or other forms of locomotion) — Part 1: Robots.” It is being developed by ISO/TC 299 (Robotics), and it is the first standard written specifically for legged and dynamically-balancing robots — humanoids. It even gives the central concept a name: actively controlled stability, meaning a robot that needs active control to stay balanced and could become unstable if it loses power.
That definition is the whole point of the standard, and the whole reason your cell is different from a normal robot cell. But you cannot certify to it. As of mid-2026, ISO 25785-1 (project 91469) is still a draft — at the Working Draft / Committee Draft stage, with a CD ballot reached during 2026. It is also tightly scoped: it explicitly excludes operator-controlled robots, mechanically guided systems, ride-on devices, exoskeletons, road vehicles, airborne and waterborne systems, floor-cleaning robots, wall-climbing robots, underground use, and non-industrial applications. So it is the right standard for an industrial humanoid, and it is not ready. Track it; do not design your 2026 cell against a draft you cannot buy.
So which published standards do I actually design to?
The same stack as any robot cell with a moving element — you just carry three documents at once instead of one. ISO 10218-1:2025 and ISO 10218-2:2025, published in 2025 as revisions of the 2011 editions, cover the robot and the integrated cell. Those revisions added cybersecurity requirements, robot classification, laser-equipment rules and safety parameterization, and they pulled the former ISO/TS 15066 collaborative-application content directly into the standard, so the biomechanical contact rules now live inside ISO 10218 itself rather than beside it.
For the locomotion — the part that walks — you reach for ISO 3691-4, the driverless-industrial-truck standard, in the same way you would for a wheeled AMR. And for the physical placement of every protective device, ISO 13855. The integrator owns the join between these scopes: ISO 10218 for the arm and the cell, ISO 3691-4 for the moving platform, ISO 13855 for where the scanners and curtains physically sit. There is, in 2026, no single product standard that covers a biped end to end. Anyone who tells you there is has not read the project record.
Layer one: what does a perimeter laser scanner do here?
A perimeter safety laser scanner is the device that earns its keep on a walking robot. It sweeps a horizontal plane low to the floor and lets you define zones: a larger warning field that slows the cell or raises an alert when someone approaches, and a tighter protective field that commands a safety stop on intrusion. Because a humanoid's working footprint is an area, not a single doorway, this area-based detection is what a flat light-curtain plane cannot give you.
For a wide perimeter — obstacle-avoidance and intrusion detection around a sizeable cell — a long-range unit such as the DAIDISIKE DLD30T-5N perimeter LiDAR gives you the range to wrap a configurable boundary around the zone the robot moves in. The architecture is exactly the one used to safeguard AGV and AMR fleets, which remains the closest practical precedent for a legged robot — the scanner does not care whether the moving thing rolls or walks, only where it and the people are. The walking is the new part; the safeguarding device is mature.
Layer two: where do the area light curtains go?
The scanner watches the open floor; the light curtains guard the fixed interfaces. Anywhere a person and the robot share a defined opening — a pick-and-place station, a part hand-off, the cell entry point — an access or area safety light curtain creates a detection plane that drops the safety outputs the instant it is broken.
For whole-body and access detection around the larger, less predictable envelope a humanoid cell needs, an area-type unit such as the DAIDISIKE DQSA area safety light curtain covers the walk-up interface where an operator loads or inspects. The choice between a light curtain at a fixed opening and a scanner over an open floor is not a matter of taste — it follows the access routes, and most humanoid cells end up using both. We laid out that plane-versus-area decision in detail in our light curtain vs scanner guide.
How do I set the mounting distance with ISO 13855?
Every protective device has to sit far enough from the hazard that the machine stops before a person reaches it. ISO 13855 gives the formula: S = (K × T) + C.
- S is the minimum safety distance from the detection plane or zone to the hazard.
- K is the approach-speed constant — 2000 mm/s for a hand/arm approach.
- T is the total stop time of the whole system: device response, controller, and the robot actually coming to rest.
- C is the added distance for detection capability: C = 8 × (d − 14) mm, where d is the curtain's resolution in millimetres, and C is never taken below zero.
Two rules catch people out. If S works out above 500 mm using K = 2000 mm/s, you are allowed to recompute with a reduced K of 1600 mm/s. And if S comes out below 500 mm, you still have to apply a 500 mm minimum separation — the formula does not let you mount a curtain right on the hazard. The humanoid-specific wrinkle is hiding in T. A bolted arm has a stop time you can measure and trust. A walking robot's stopping behaviour — and the geometry of where it ends up — is harder to bound, so get a conservative, verified stop-time figure from the robot vendor before you commit the distance. If T is fuzzy, S is fiction.
Why isn't a fence enough when the robot can fall over?
Here is the part that makes a legged humanoid genuinely different from a fixed arm or even a wheeled AMR, and it is the reason the area sensors exist. A humanoid can fall or tip if power or balance control is lost, and its centre of mass and reach envelope change as it walks. A bolted arm sweeps a known, repeatable volume. A wheeled AMR stays upright when you cut its power. A biped does neither.
That dynamic, potentially-toppling envelope is exactly the new hazard class ISO 25785-1 was created to address, and it is precisely what a static fence does not fully cover. So the fence handles the gross boundary, the interlocked and guard-locked access door handles entry, and then the perimeter scanner and area curtains handle the part the fence cannot: a person in the floor zone the robot might step or fall into, and the interfaces where people and the machine meet on purpose. Layered, not single-device — because no one layer covers every way a person can reach this particular hazard.
And no, the robot's own LiDAR is not your safety device
The humanoid arrives bristling with cameras and LiDAR. They are navigation and perception sensors. They help the robot walk and dodge obstacles, and they are genuinely useful — but they are not certified safety devices under IEC 61496, they have no self-monitored dual safety outputs, and they are not type-tested to stop a machine before someone is hurt. A certified perimeter safety laser scanner is all three. Use the robot's perception to make it behave well; rely on external certified scanners and curtains to keep people safe. This is the identical category error that catches AGV and AMR integrators, and the answer is identical too. We cover the mobile-robot precedent in our ANSI/RIA R15.08 explainer.
What does the finished shopping list look like?
Pulling it together, the safeguarding bill of materials for a typical 2026 humanoid workcell reads almost exactly like a conventional robot cell — which is the reassuring part:
- A physical fence with one or two access points, each with a coded, guard-locking interlock so the door cannot open while the robot moves and the cell cannot run while the door is open.
- One or more perimeter safety laser scanners covering the swept floor zone, with warning and protective fields, and field sets switched by the cell's operating mode.
- Area / access safety light curtains at every fixed human interface and the cell entry, resolution chosen by what they must detect, and each mounted at its ISO 13855 distance.
- The robot's own perception layered on top as behaviour, never counted in the safety function's PL or SIL.
For the wider picture on where the standards genuinely sit versus where the marketing runs ahead of them, our companion piece on humanoid robot safety standards in 2026 factories goes deeper on what is still unsolved.
References & standards cited
- ISO 25785-1 (under development) — safety requirements for dynamically stable industrial mobile robots (legged); ISO/TC 299, project 91469, still a draft.
- ISO 10218-1:2025 — industrial robots; 2025 revision, ISO/TS 15066 content absorbed.
- ISO 13855 — positioning of safeguards; S = (K × T) + C.
- Figure AI — production at BMW — public reference for the Spartanburg deployment.
- Agility Robotics — Digit moves over 100k totes — public reference for the GXO deployment.

