InOrbit.AI Launches OpenRobOps as First ISO 21423 Reference Implementation

InOrbit.AI has released OpenRobOps (ORO), an open-source fleet management software that provides the first reference implementation of the ISO 21423 standard. The move aims to standardize how industrial mobile robots from different manufacturers communicate and coordinate in shared workspaces.

Distributed under the Apache 2.0 license, ORO is designed to help robotics developers avoid the "build trap" of creating proprietary back-end infrastructure from scratch. The software provides a production-grade foundation to bridge the interoperability gap. The technical suite includes an edge-to-cloud hybrid architecture, high-throughput telemetry ingest, real-time spatial tracking, and automated incident remediation. It also supports configuration as code (CaC) and native Open-RMF interoperability.

The Push for Interoperability

For years, the robotics industry has been plagued by fragmentation. In many warehouses and factories, robots from different vendors operate in silos, unable to communicate or negotiate right-of-way, which often creates operational bottlenecks. To solve this, ISO 21423 was developed as an international standard specifying communication protocols to enable interoperability among industrial autonomous mobile robot (AMR) systems from different vendors.

This standard draws on existing regional frameworks, such as Europe's VDA 5050 and the MassRobotics Interoperability Standard in North America, to create a shared global language. The practical application of this standard was first showcased at Automate 2026. During the public demonstration, 10 different companies utilized InOrbit Space Intelligence to prove that heterogeneous fleets could operate under a unified communication protocol.

Industry Implications

By open-sourcing a reference implementation of ISO 21423, InOrbit.AI is attempting to lower the barrier for original equipment manufacturers (OEMs) to build compatible systems. This creates a shift for robot operations and fleet management similar to the impact ROS (Robot Operating System) had on low-level robotics development.

For end-users, this shift is critical to preventing vendor lock-in. When fleet managers can integrate robots from multiple vendors into a single orchestration layer, they can scale automation based on specific hardware needs rather than being tied to a single ecosystem. This interoperability allows for more flexible deployment and reduces the risk associated with relying on a single supplier for critical infrastructure.

What's Next

As the ISO 21423 standard moves toward full adoption, the industry will be watching to see how many OEMs integrate the OpenRobOps reference implementation into their own stacks. While the Automate 2026 demonstration proved the concept with a small group of companies, the broader success of the standard depends on widespread industry adherence to these communication protocols to ensure seamless cross-vendor coordination.