InOrbit.AI ships OpenRobOps, first ISO 21423 reference implementation

OpenRobOps traces its roots to a February announcement by InOrbit, which has now followed through with a full release. The company frames the timing around a familiar problem: as fleets of autonomous mobile robots grow, customers expect OEMs to ship full-featured fleet managers, but many OEMs instead spend years maintaining custom back ends and interfaces rather than refining their robots. InOrbit calls this the "build trap" and positions OpenRobOps as an escape.

The release also carries a standards angle. ISO 21423 is still upcoming, yet OpenRobOps already includes a reference implementation, and InOrbit's CEO sits on the ISO working group as an ANSI representative. InOrbit points to a public demonstration of ISO 21423 at Automate 2026, where 10 companies showed multi-vendor orchestration based on the company's paid Space Intelligence product, as evidence the approach works in practice.

The stakes likely hinge on adoption. InOrbit compares OpenRobOps to ROS, which saved roboticists from rewriting low-level device drivers; whether OEMs treat ORO the same way, rather than continuing to build their own back ends, is the open question. For end users, the benefit may depend on how broadly ISO 21423 compliance spreads across vendors.