This is a familiar pattern in technology, and it's one open source has solved before. Linux gave servers a common foundation. ROS gave robot developers a shared framework. Robot operations deserves the same.

Today, we're thrilled to announce OpenRobOps 1.0 — the first stable release of an open-source, vendor-agnostic platform for robot fleet management and operations. Fully self-hostable, Apache 2.0 licensed, and ready for production fleets.

Why 1.0 matters​

A 1.0 release is a promise. It says the core is stable, the APIs are ones we'll stand behind, and the platform is ready to run real robots doing real work. OpenRobOps is rooted in production-proven technology from InOrbit.AI — the same foundation used to manage thousands of robots in real-world deployments — now available to everyone, in the open.

It marks something bigger, too: for the first time, there is a production-ready, fully open-source foundation for robot fleet operations. No license fees, no lock-in, no black boxes. Your robots, your servers, your data.

What's in 1.0​

Your entire fleet in one place. Real-time telemetry, customizable dashboards, live camera feeds, historical time-series charts, ROS diagnostics, and incident tracking across your robots — regardless of who manufactured them. One platform, one view, any vendor.

Maps and navigation, fleet-wide. Live maps show every robot in your fleet at once — poses, paths, planned trajectories, and footprints. Send a robot to a waypoint with a click, watch its global plan and local trajectory in real time, and switch between robot-reported and shared facility maps.

Connect robots your way. ROS and ROS 2 robots are first-class citizens: install the InOrbit agent and they join your fleet with essentially zero effort — telemetry, maps, and actions just work. An Open-RMF connector is built in as well, so RMF-managed fleets plug straight into the same operational view.

Native ISO 21423 support. OpenRobOps also speaks the new ISO 21423 interoperability standard for industrial mobile robots. Any ISO-native robot can join your fleet — no agent, no vendor SDK required. It gets the same dashboards, incidents, actions, and audit trail as every other robot. We believe standards are how this industry scales, and we're proud to ship one of the first open implementations.

Incidents, alerts, and automation. Define incidents as code, trigger notifications, and wire up automatic actions when things go wrong — so your team responds to problems, not dashboards.

Operations you can trust. Role-based access control, per-robot view permissions, robot locks for safe exclusive control, self-service API keys, and a full audit log of every action taken on every robot.

Extend and customize freely. Pluggable ingest modules process any telemetry. Custom widgets build the exact operational view your team needs. A declarative configuration API defines dashboards, attributes, and incidents as code. And a complete theming system lets you brand the entire UI — because the platform running your operation should feel like yours.

Ready to deploy. Versioned container images on GHCR, a documented release process, Kubernetes deployment guidance, and Terraform-based configuration management — on a stack you already know: Node.js, React, MongoDB, and MQTT with Protocol Buffers.

Try it — you're 10 minutes away​

This is the part we're most excited about. You don't need a sales call, a license, or even a robot to see OpenRobOps in action:

1. Follow the quick start guide — a full fleet management platform running locally in about 10 minutes.
2. Connect your first robot, or spin up the simulator and watch a fleet come alive on the map.
3. Make it yours — build a custom widget, add a data source, or theme the UI.

Join us​

OpenRobOps is built in the open, and 1.0 is just the beginning. Whether you're running a fleet of warehouse robots, developing the next generation of AMRs, or just believe that robot operations infrastructure should be transparent and community-driven — there's a place for you here:

• Star the repo on GitHub — it genuinely helps the project grow
• Join the community on Discussions
• Contribute — the contributing guide has good first issues waiting

Robot operations is open now. Let's put it to work.

— The OpenRobOps team

Today, every robot vendor ships its own proprietary operations dashboard. If you run robots from two manufacturers, you get two disconnected views. If you want to customize how you monitor your fleet, you're limited to what the vendor exposes. And if you ever want to switch platforms, you're starting from scratch.

This is a familiar pattern in technology — and one that open source has solved before. Linux gave servers a common foundation. ROS gave robot developers a shared framework. Robot operations deserves the same.

So we're building it. Today we're announcing OpenRobOps, a new open-source project for robot fleet management and operations — and we're building it in the open, from day one.

What we're setting out to build​

OpenRobOps won't be just another dashboard. Our goal is a foundation the robotics industry can build on together: an open-source, vendor-agnostic platform for operating fleets of autonomous mobile robots — fully self-hostable, under the Apache 2.0 license.

We're not starting from a blank page. OpenRobOps is rooted in production-proven technology from InOrbit.AI, which has been used to manage thousands of robots in real-world deployments. Our work now is bringing that experience into an open, transparent codebase that anyone can run, inspect, and extend.

Here's what we're aiming for:

One view for any fleet. Real-time telemetry, customizable dashboards, and incident tracking across your robots — regardless of who manufactured them. One platform, one view, any vendor.

Ownership, not rental. Not a SaaS product you rent access to. OpenRobOps will run on your servers, under your control. Your robot data stays where you decide it stays.

Open to every robot. Native support for ROS and ROS 2, integration with Open-RMF, and — as the standard matures — ISO 21423, the emerging interoperability standard for industrial mobile robots. We want joining a fleet to be easy no matter what your robot speaks.

Extensible by design. Pluggable ingest modules for any telemetry, custom widgets for the exact operational view your team needs, and a declarative configuration API so dashboards, attributes, and incidents can be defined as code.

Boring, familiar technology. MQTT with Protocol Buffers on the wire; Node.js, React, and MongoDB behind it. If you've worked in robotics or web development, you'll feel at home.

Where we are today​

Early. The core architecture is taking shape, and telemetry is flowing from robots to dashboards. There are rough edges, missing pieces, and open questions — and that's exactly why we're announcing now rather than later.

We believe the best infrastructure is built in the open, with the people who will actually use it. The decisions we make in the coming months — how robots connect, how data is modeled, how the platform is extended — will shape the project for years. We'd rather make them with you.

Follow along, or better: join in​

If you're running a fleet of warehouse robots, developing the next generation of AMRs, or just believe that robot operations infrastructure should be transparent and community-driven — there's a place for you here, from the very beginning:

• Star the repo on GitHub — the code is landing there as it opens up
• Join the community on Discussions — tell us about your fleet and what you'd need from a platform like this
• Contribute — the contributing guide explains how to get involved

Robot operations should be open. Let's build it together.

— Hernan & Florian