OpenRobOps 1.0

[herchu]

🎉 OpenRobOps 1.0 is out — open-source robot fleet operations, ready for production

Today we're tagging v1.0.0 of OpenRobOps (ORO): a self-hostable, vendor-agnostic platform for monitoring and operating fleets of autonomous mobile robots. Apache 2.0, no license fees, no lock-in. Your robots, your servers, your data.

ORO started as production code that has run thousands of robots at InOrbit.AI and is now developed fully in the open under the OpenRobOps org. From here on, this is a community project and this is where it gets built.

Why this matters

Every AMR vendor ships its own dashboard. Mixed fleets mean disconnected views. Teams building robots end up rebuilding the same backend, UI and integrations over and over — the "build trap." Open source fixed this before robot software (ROS). Robot operations deserved the same shared foundation. That's what 1.0 is.

What's in 1.0

• One view of your whole fleet. Real-time telemetry, dashboards, camera feeds, time-series history, ROS diagnostics, incident tracking — across robots from any vendor.
• Fleet-wide maps and navigation. Every robot's pose, path, plan and footprint on a live map. Send a robot to a waypoint with a click.
• Connect robots your way. ROS / ROS 2 robots join with the agent installed and essentially nothing else. Open-RMF fleets plug in through the built-in connector.
• Native ISO 21423. ORO acts as a fleet manager (IMRFM) for the new ISO 21423 industrial mobile robots: communications and interoperability standard. Any ISO-native robot joins the fleet with no agent and no vendor SDK, and gets the same dashboards, incidents, actions, locks and audit log as every other robot. This is the first open implementation of the standard.
• Incidents, alerts, automation. Status-rule-driven incidents with severities, in-app notifications, webhook channels, and automatic actions.
• Operations you can trust. Role-based access control, per-robot permissions, robot locks for exclusive control, self-service API keys, full audit log.
• Extend everything. Pluggable ingest modules, custom widgets, a declarative configuration API so dashboards/attributes/incidents live in Git, and a full theming system (eight themes ship in the box).
• Deployable. Versioned images on GHCR, Kubernetes guidance, Terraform-managed settings. Stack: Node.js, React, MongoDB, Mosquitto MQTT + Protocol Buffers.

Try it in ~10 minutes, no robot required

1. Quick start — full platform running locally.
2. Connect your first robot, or run the Flatland simulator and watch an ISO 21423 fleet appear on the map.
3. Make it yours: custom widgets, data sources, themes.

Related repos

• OpenRobOps/oro — the platform (this repo)
• OpenRobOps/iso21423 — @openrobops/iso21423, a TypeScript SDK for the standard: topics, JSON Schema validation, MQTT session with Last Will semantics, request state machine. Usable by anyone building an ISO robot or fleet manager in Node.js.
• OpenRobOps/sim-flatland — Nav2 simulated robot with a reference ISO 21423 agent sidecar.

What's next

The roadmap lists what's shipped and what's in the codebase but not yet enabled (more ingest modules, more widget types, ISO upstream mode). Priorities live in issues and milestones. If you want to shape them, this is the moment.

How to get involved

• ⭐ Star the repo — it genuinely helps people find the project.
• 💬 Tell us what you're running. Reply below: what robots, what vendors, what's missing for your fleet.
• 🐛 File issues for bugs and feature requests.
• 🔧 Contribute. The contributing guide covers dev setup and the PR process, and there are good first issues waiting.
• 📖 Full release blog post: https://openrobops.org/blog/openrobops-v1

Thanks to everyone who tested, filed issues and pushed on the standard along the way. Robot operations is open now. Let's put it to work.

— The OpenRobOps team