--- title: "The last mile of robotics: the pilot was flawless, the deployment stalled at 10 robots" date: 2026-09-18T09:30:00+10:00 author: Sam Bottrell canonical_url: "https://celona.io/resources/the-last-mile-of-robotics-the-pilot-was-flawless-the-deployment-stalled-at-10-robots" section: Resources --- # Robot makers build robots. Connectivity shouldn't be their problem Your robot works everywhere except the one place that matters: the customer's site. The autonomy was the hard part, and you solved it. Now a flaky network is quietly capping your rollout, one stalled robot at a time. By **Jyotin Basrur** · September 18, 2026 / From the robot maker's chair ## **The last mile of robotics: the pilot was flawless, the deployment stalled at 10 robots** ##### A field note for anyone shipping robots into the real world Your robot works. You've watched it run a thousand times without a hitch — in your lab, in the pilot, in the demo that closed the deal. So why are you sitting in a customer review three months later, staring at a reliability chart gone red, with nothing to offer but "we're looking into it"? This deployment was meant for 200 robots. You're stuck at 10. It's 11 p.m. and the message arrives: *"Unit 7 faulted again at the Memphis site."* Your sharpest engineer spent a day in the logs and came back with the worst possible answer — *"nothing's wrong on our side."* You are sitting across the table from your customer's IT lead, and you are both politely certain it's the other's fault, and everyone walks out with nothing fixed. The hard part was supposed to be the autonomy — perception, planning, control. You solved that. What's quietly stalling your deployments is the one thing you never signed up to own: the network your robot has to live on. / The setup ## It worked in the lab The pilot was beautiful. One robot, one controlled space, an afternoon of everyone watching. It worked, everyone clapped, and you got the PO for twenty more. Then you shipped into the real building — concrete, metal racking, forklifts, and a Wi-Fi network you've never seen and don't control. And the robot that was flawless in the lab starts to hesitate. It stalls for a few seconds in one aisle. A video feed drops on the far side of the warehouse. A control command lands late, once, and the robot faults out. This causes 5 other robots to stall. Not always. Not everywhere. Just often enough to erode trust. The tickets start. "Your robot froze again." You fly an engineer out and can't reproduce it. Everything on your side looks fine, so you suggest it might be their network; they're certain it's your robot. Nobody can prove anything, nothing gets fixed, and the deployment stalls at a fraction of the fleet you sold. ![fhfhfh](https://celona.io/volumes/images/Resources/Blog/The-Robot-Makers-Dilemma/_width1000px/On-the-custoemer-wifi.jpg?transformId=13659)It worked in the lab. In the customer's warehouse, the same robot stalls in one aisle — and no one can say why. / The uncomfortable truth ## You are a robotics company, not a wireless company Here's what no one warned you about: shipping robots into the world makes you responsible for connectivity you can't see and were never equipped to manage. Suddenly your engineers — the ones who are brilliant at motion planning — are being asked which wireless technology to standardize on. Wi-Fi 6? Wi-Fi 7? Private 5G? Should the control channel travel a different path than video? How do you keep the safety-critical link alive when the RF gets ugly? These are real, hard questions — and not the ones you started a robotics company to answer. And even when you guess right on the technology, you're still blind. When a robot underperforms, you can't see the one thing that would let you fix it: what actually happened on the link, at that moment, for that flow. / The real last mile ## It was never the robot You pour everything into the last mile of autonomy — the smarter algorithm, the tighter model. But the last mile of a *deployment* isn't a smarter robot. It's the wireless link between the robot and the world, and today nobody owns visibility into it. Connectivity sits between you and every customer as a black box, turning every incident into a standoff instead of a fix. / The turn ## What if the robot could see its own network? That's the question that changes everything. What if the robot could see and explain its own connectivity — in its own words, with evidence? That's what AerConnect does. It's an open-source connectivity layer that runs on the robot's own host — or a gateway beside it — over whatever network is there: Wi-Fi, cellular, Ethernet. It gives you the three things you never had: - **It sees every flow.** It knows control from video from telemetry, and measures how each one is really performing. - **It explains failures with evidence.** When the robot hesitates, AerConnect shows whether it was the network or the robot, with a timestamp — so "your robot is broken" becomes "here's exactly what happened, let's fix it." - **It uses the right path for the right traffic, automatically.** Critical traffic stays on the most reliable link, and you can add 5G where Wi-Fi isn't enough — without re-architecting the robot. The connectivity decisions you were never equipped to make? You stop making them. The layer handles it. ![https://celona.io/volumes/images/Resources/Blog/The-Robot-Makers-Dilemma/unifying-industrial-connectivity-with-AerConnect.jpg](https://celona.io/volumes/images/Resources/Blog/The-Robot-Makers-Dilemma/_width1000px/unifying-industrial-connectivity-with-AerConnect.jpg?transformId=13660)AerConnect: one open layer across Wi-Fi, cellular, and private 5G — so connectivity stops being the robot maker's problem. / The new world ## What the next rollout feels like Picture it. The pilot still goes beautifully — but this time it translates. When a robot hesitates at site 14, you don't scramble a flight; you open a shared, live view with the customer's team and see, together, that an access point handed off badly in that one aisle. It's fixed by lunch. No blame, no standoff, no stalled deployment. Your engineers go back to building robots, because connectivity is finally something they don't have to think about. You right-size each site with data instead of guesswork — Wi-Fi where it's enough, 5G where it isn't. And the fleet you sold actually gets deployed, because the thing that used to erode trust now builds it. That's the difference between a robot that demos and a robot that scales. The last mile of robotics was never really about the robot. It was about everything the robot couldn't see. AerConnect is how it finally sees. ## Run it on one of your robots [AerConnect](https://celona.io/aerconnect) is a free, open-source connectivity layer from celona — neutral by design, no lock-in, and it works on the network you already have. If you build robots, let's run a proof of concept on one of yours. In a couple of weeks we'll show you, with evidence, exactly where connectivity is costing you — and where AerConnect wins it back. / Related resources ## Go deeper More resources on private wireless for the enterprise. [Page ### Pricing estimator Estimate the 3-year cost of a Celona Orion deployment (private 5G + Wi-Fi) against big-brand Wi-Fi and competitor private cellular. ](https://celona.io/pricing-estimator) [Blogs ### More network for your dollar How Celona Orion gives you a better network for the same or lower price than the leading enterprise Wi-Fi vendor. Aug 2026 ](https://celona.io/resources/more-network-for-you-dollar) [Videos NEW ### How Orion brings enterprise wireless together No more choosing between Wi-Fi and private 5G, Orion brings them together in one subscription. Aug 2026 ](https://celona.io/resources/how-orion-brings-enterprise-wireless-together) [Access all Resources ](https://celona.io/resources)