Segment
Mobile robotics: moving the machine, not the part
A fixed arm waits for work to arrive. A mobile robot goes and gets it, which turns a machine problem into a building problem: where the robot is, what changed on the floor since yesterday, and what the other three hundred vehicles are doing in the same aisles.
In one sentence
Mobile robotics covers vehicles that move themselves around a facility rather than moving a part within a cell — autonomous mobile robots and driverless industrial trucks, the fleet software that coordinates them, and the enclosed storage systems built around captive robot fleets.
Almost every argument for automating a factory or a warehouse founders on the same thing: the machine that does the work is not the machine that moves the work. A robotic cell that runs unattended still stops when nobody brings it parts, and in order fulfilment the largest single cost is a person walking. Mobile robots address that half of the problem, and they are now a larger unit market than industrial arms.
The technical break with the previous generation is that the route is no longer built into the floor. An automated guided vehicle follows wire, magnetic tape or surveyed reflectors, so changing where it goes is a construction job. An autonomous mobile robot carries a map and works out where it is by matching what it senses against that map, so a route change is a software edit. That is the whole commercial argument for the category, and it is why the interesting engineering moved from the vehicle to the software.
It moved twice, in fact. Getting one robot across a building reliably is a solved problem in a static facility and a hard one in a busy warehouse where pallets move daily. Getting four hundred robots across the same building without two of them waiting for each other in a single-width aisle is a different discipline again, and it is where large deployments actually fail. The storage systems in the last segment sidestep both by giving the robots a structure of their own to live in, at the cost of committing a building to a layout for a decade.
How this breaks down
Split by what one supplier delivers: the navigation stack on a single vehicle, the traffic layer that coordinates a fleet of them, the enclosed storage systems built around captive fleets, and the drive and power hardware every base rides on.
- Mobile roboticsthis page
- Autonomous navigationMapping, localisation and dynamic obstacle handling — the stack that replaced tape on the floor.Definition page
- Fleet orchestrationTraffic control, mission assignment, charging schedules and the interface to the system that knows what needs moving.Definition pageChokepoint
- Goods-to-person systemsCube storage, shuttles and mobile racking — captive robot fleets inside a structure built for them.Definition page
- Drive and powerWheel-drive units, lithium packs and opportunity charging — the running gear underneath every mobile robot.Definition pageChokepoint
What this depends on
1 of these is marked as a chokepoint: a handful of qualified suppliers, a multi-year lead time, or a single geography.
- Technology
Three-dimensional perception
A scan at ankle height misses overhanging forks and low pallets; without depth sensing the vehicle drives into the things a two-dimensional safety scanner cannot see.
3D sensing - Technology
Onboard inference hardware
Localisation, obstacle classification and route planning run on the vehicle within its reaction time, on embedded hardware that also has to fit the power budget.
Inference silicon - Supply chain
Lithium cells and chargers
A fleet is sized by how much of a shift each robot spends working rather than charging, which is a cell chemistry decision before it is a scheduling one.
LFP cathodes - StandardChokepoint
Safety standards for driverless industrial vehicles
Speed near people, protective field sizes and stopping distances are set by machinery safety standards written for vehicles rather than for cells; the assessment covers the whole route, not a fenced footprint.
Safety and collaboration
Companies across Mobile robotics
Every company named on a step below this page, ordered by how many of those steps it appears at. Compiled from the pages themselves rather than written separately, so the two cannot disagree. Not a ranking and not a recommendation.
- AutoStoreOslo1 step
- BalyoParis1 step
- BlueBoticsPrivate1 step
- Delta-Q TechnologiesPrivate1 step
- DematicFrankfurt1 step
20 more companies appear at a single step each; they are named on the pages for those steps.
How these pages are written
Each page explains one technology in plain language, states what it depends on, and names companies by what they supply at that step. Company roles are described qualitatively and deliberately carry no market shares, revenue figures or rankings — those change faster than an explainer can, and a stale number is worse than none. Ticker links point at company pages on this site and are provided for reference only.
Nothing here is investment advice, a recommendation, or a forecast. A company named on a page about a technology is not thereby a good investment, and the chokepoints described are structural facts about supply chains rather than predictions about prices. Technology moves; where a page describes something as unresolved or in development, that was true when it was written.
Plutux no es un asesor de inversiones. Los datos de mercado y el análisis generado por IA son solo informativos y educativos, no asesoramiento de inversión. Aviso legal