Rank #1 of 5 in Robotics Software Platforms
Install
sudo apt install ros-jazzy-desktop
vs Formant
vs Gazebo
vs NVIDIA Isaac
vs ViamVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Bring up hardware — stories about bring up hardware in this arenaBring up hardwareevidence →
Stories about bring up hardware in this arena
Data pipelines — stories about data pipelines in this arenaData pipelinesevidence →
Stories about data pipelines in this arena
Deployment ota — stories about deployment ota in this arenaDeployment otaevidence →
Stories about deployment ota in this arena
Fleet management — keys at organization scale — bulk provisioning, delivery services, IdP policiesFleet managementevidence →
Keys at organization scale — bulk provisioning, delivery services, IdP policies
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Safety reliability — stories about safety reliability in this arenaSafety reliabilityevidence →
Stories about safety reliability in this arena
Sdk ecosystem — stories about sdk ecosystem in this arenaSdk ecosystemevidence →
Stories about sdk ecosystem in this arena
Simulation — stories about simulation in this arenaSimulationevidence →
Stories about simulation in this arena
Teleoperation monitoring — stories about teleoperation monitoring in this arenaTeleoperation monitoringevidence →
Stories about teleoperation monitoring in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 4 free · 0 paid · 0 enterprise · 24 not stated in evidence
Follow the green: where the map greys out is where ROS 2 stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓7/10
unlocks → MCP server · Machine-readable spec · Versioning policy · Integrate vision-language-action or robotics foundation models into my robot's autonomy stack through supported tooling
Subscribe to events via webhooks
n/an/a
Build against official SDKs
✓7/10
Issue scoped/least-privilege API credentials for an agent
~4/10
Connect an agent via an official MCP server
—–
Download a machine-readable API spec (OpenAPI or equivalent)
—–
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
~5/10
Explore an interactive API reference with runnable examples
—–
Docs for agents
Point an agent at llms.txt or agent-oriented docs
—–
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
—–
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
n/an/a
Set up automations that run autonomously in the background
~6/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Bring up hardware — stories about bring up hardware in this arenaBring up hardware
Stories about bring up hardware in this arena
Data pipelines — stories about data pipelines in this arenaData pipelines
Stories about data pipelines in this arena
Deployment ota — stories about deployment ota in this arenaDeployment ota
Stories about deployment ota in this arena
Fleet management — keys at organization scale — bulk provisioning, delivery services, IdP policiesFleet management
Keys at organization scale — bulk provisioning, delivery services, IdP policies
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Safety reliability — stories about safety reliability in this arenaSafety reliability
Stories about safety reliability in this arena
Safety
Sdk ecosystem — stories about sdk ecosystem in this arenaSdk ecosystem
Stories about sdk ecosystem in this arena
Simulation — stories about simulation in this arenaSimulation
Stories about simulation in this arena
Teleoperation monitoring — stories about teleoperation monitoring in this arenaTeleoperation monitoring
Stories about teleoperation monitoring in this arena
Sorted by importance (agentic first) (high → low) · 54/54 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 7/10 | Xcommunity | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none± | untested | none yet | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 5/10 | Cclaimed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | fullfree | 8/10 | Xcommunity | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 6/10 | Cclaimed | |
Swap sensors and actuators behind stable hardware-abstraction interfaces without rewriting application code C Bring up | robotics engineer | Bring up hardware — stories about bring up hardware in this arenaBring up hardware | 3 | partial | 6/10 | Cclaimed | |
Bring up a new robot — drivers, configuration, first motion — in hours rather than weeks C Bring up | robotics engineer | Bring up hardware — stories about bring up hardware in this arenaBring up hardware | 3 | disputed | 5/10 | Dcontradicted | |
Build against official, typed SDKs in multiple languages (Python, TypeScript, Go, C++) that cover the platform's full surface G Sdks | developer | Sdk ecosystem — stories about sdk ecosystem in this arenaSdk ecosystem | 3 | partial | 5/10 | Cclaimed | |
Have an AI agent authenticate with scoped credentials and command a real robot end-to-end through the platform's API or SDK G Sdk agentic | ai-native user | Sdk ecosystem — stories about sdk ecosystem in this arenaSdk ecosystem | 3 | partial | 5/10 | Cclaimed | |
Implement emergency-stop and safety-interlock patterns the platform documents and supports C Safety | robotics engineer | Safety reliability — stories about safety reliability in this arenaSafety reliability | 3 | partial | 5/10 | Cclaimed | |
Teleoperate a remote robot with live video and responsive control over real-world networks C Teleop | ops lead | Teleoperation monitoring — stories about teleoperation monitoring in this arenaTeleoperation monitoring | 3 | partialfree | 5/10 | Xcommunity | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 4/10 | Cclaimed | |
Capture sensor and telemetry data on-robot and sync it to the cloud with bandwidth-aware policies C Data | developer | Data pipelines — stories about data pipelines in this arenaData pipelines | 3 | partial | 3/10 | Cclaimed | |
Simulate my robot and its environment with realistic physics and sensor models before touching hardware C Sim | robotics engineer | Simulation — stories about simulation in this arenaSimulation | 3 | partial | 3/10 | Cclaimed | |
Monitor the health, location, and status of a whole robot fleet from one dashboard C Fleet | ops lead | Fleet management — keys at organization scale — bulk provisioning, delivery services, IdP policiesFleet management | 3 | none | 0/10 | ||
Deploy software updates over-the-air to robots with staged rollouts and rollback C Deploy | ops lead | Deployment ota — stories about deployment ota in this arenaDeployment ota | 3 | n/a | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | n/a | untested | none yet | |
Inspect live topics, logs, and state on a deployed robot remotely to debug issues C Teleop | robotics engineer | Teleoperation monitoring — stories about teleoperation monitoring in this arenaTeleoperation monitoring | 2 | full | 8/10 | Xcommunity | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | fullfree | 8/10 | Cclaimed | |
Run the same robot code against simulation and the real robot without a rewrite C Sim | robotics engineer | Simulation — stories about simulation in this arenaSimulation | 2 | fullfree | 7/10 | Xcommunity | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Cclaimed | |
Query and export collected robot data through an API or SQL for offline analysis G Data | developer | Data pipelines — stories about data pipelines in this arenaData pipelines | 2 | partial | 5/10 | Cclaimed | |
Integrate cameras, lidars, IMUs, and GPS with ready-made drivers and standard message types C Sensors | robotics engineer | Bring up hardware — stories about bring up hardware in this arenaBring up hardware | 2 | partial | 4/10 | Xcommunity | |
Feed collected robot data into model training and deploy the improved model back to the fleet C Data ml | developer | Data pipelines — stories about data pipelines in this arenaData pipelines | 2 | partial | 3/10 | Cclaimed | |
My robots keep operating and buffer data locally when cloud connectivity drops, then recover cleanly G Safety | ops lead | Safety reliability — stories about safety reliability in this arenaSafety reliability | 2 | partial | 3/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 3/10 | Cclaimed | |
Generate synthetic training data and run reinforcement learning at scale in simulation C Sim training | developer | Simulation — stories about simulation in this arenaSimulation | 2 | none | 0/10 | ||
Push configuration changes across many robots at once with per-group targeting C Fleet | ops lead | Fleet management — keys at organization scale — bulk provisioning, delivery services, IdP policiesFleet management | 2 | none | 0/10 | ||
Run automated tests of robot software in CI, including simulation-based regression tests C Deploy | developer | Deployment ota — stories about deployment ota in this arenaDeployment ota | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Express a robot task in natural language and have the platform plan and execute it G Sdk agentic | ai-native user | Sdk ecosystem — stories about sdk ecosystem in this arenaSdk ecosystem | 2 | n/a | untested | none yet | |
Get alerts on robot faults, battery, and connectivity so issues are caught before customers notice C Fleet | ops lead | Fleet management — keys at organization scale — bulk provisioning, delivery services, IdP policiesFleet management | 2 | none | untested | none yet | |
Integrate vision-language-action or robotics foundation models into my robot's autonomy stack through supported tooling G Sdk agentic | ai-native user | Sdk ecosystem — stories about sdk ecosystem in this arenaSdk ecosystem | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | n/a | untested | none yet | |
Control with roles and permissions who is allowed to command, configure, or view each robot G Safety | ops lead | Safety reliability — stories about safety reliability in this arenaSafety reliability | 1 | partial | 4/10 | Cclaimed | |
Pull reusable packages or modules from a registry or ecosystem for common hardware and behaviors C Ecosystem modules | developer | Bring up hardware — stories about bring up hardware in this arenaBring up hardware | 1 | partial | 4/10 | Xcommunity | |
Route autonomy failures to a human intervention queue where an operator resolves and hands back control C Teleop | ops lead | Teleoperation monitoring — stories about teleoperation monitoring in this arenaTeleoperation monitoring | 1 | none | 0/10 | ||
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 35 stories with headroom
What would move ROS 2’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productConnect an agent via an official MCP server
nonemoves agent-readyimpact 45
Missing: any mention of an official MCP server, MCP protocol support, or agent-facing API for ROS 2.
Fleet management — keys at organization scale — bulk provisioning, delivery services, IdP policiesMonitor the health, location, and status of a whole robot fleet from one dashboard
nonemoves PA Scoreimpact 30
ROS 2 evidence covers single-robot/graph introspection (CLI tools, RViz via desktop install, topic/service introspection) but nothing about a unified dashboard aggregating health, location, and status across a whole fleet of robots — fleet-level monitoring is typically built by third-party layers on top of ROS 2, not documented here.
Agenticness — how well agents can access and operate the productPoint an agent at llms.txt or agent-oriented docs
nonemoves agent-readyimpact 30
No evidence of an llms.txt file, agent-oriented documentation format, or any mention of AI agent-targeted docs; the evidence pack only covers standard human-oriented ROS 2 documentation and community discussion.
Agenticness — how well agents can access and operate the productOperate the product with natural-language commands
nonemoves Built-in AIimpact 30
ROS 2's interfaces are CLI-based (ros2 command with sub-commands) and programmatic client libraries, not natural-language control; no evidence of NL command parsing, LLM integration, or agentic natural-language interface is present in the evidence pack.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
The evidence pack shows standard reStructuredText documentation, tutorials, and CLI examples, but nothing describing an interactive API reference (e.g., a searchable/browsable API explorer with runnable/executable code examples in-browser).
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
Missing: any OpenAPI/JSON-schema export, machine-readable spec endpoint, or documented spec-generation tool.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
Missing: documented API versioning scheme, formal deprecation policy/timeline, compatibility guarantees across releases.
Data pipelines — stories about data pipelines in this arenaCapture sensor and telemetry data on-robot and sync it to the cloud with bandwidth-aware policies
partialq3/10moves PA Scoreimpact 21
Missing: cloud upload/sync capability, bandwidth-aware transfer policies, any first-party cloud integration or partner tooling for telemetry sync.
Showing the top 8 of 35 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map2 surfaces · 29 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
GitHub README29 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Build against official SDKs
- Set up automations that run autonomously in the background
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Swap sensors and actuators behind stable hardware-abstraction interfaces without rewriting application code
- Bring up a new robot — drivers, configuration, first motion — in hours rather than weeks
- Pull reusable packages or modules from a registry or ecosystem for common hardware and behaviors
- Integrate cameras, lidars, IMUs, and GPS with ready-made drivers and standard message types
- Capture sensor and telemetry data on-robot and sync it to the cloud with bandwidth-aware policies
- Query and export collected robot data through an API or SQL for offline analysis
- Feed collected robot data into model training and deploy the improved model back to the fleet
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Read the product's source under an open license
- Self-host the core product
- Control with roles and permissions who is allowed to command, configure, or view each robot
- Implement emergency-stop and safety-interlock patterns the platform documents and supports
- My robots keep operating and buffer data locally when cloud connectivity drops, then recover cleanly
- Have an AI agent authenticate with scoped credentials and command a real robot end-to-end through the platform's API or SDK
- Build against official, typed SDKs in multiple languages (Python, TypeScript, Go, C++) that cover the platform's full surface
- Simulate my robot and its environment with realistic physics and sensor models before touching hardware
- Run the same robot code against simulation and the real robot without a rewrite
- Inspect live topics, logs, and state on a deployed robot remotely to debug issues
- Teleoperate a remote robot with live video and responsive control over real-world networks
Hacker News8 stories
- Drive the product through a documented public API
- Bring up a new robot — drivers, configuration, first motion — in hours rather than weeks
- Pull reusable packages or modules from a registry or ecosystem for common hardware and behaviors
- Integrate cameras, lidars, IMUs, and GPS with ready-made drivers and standard message types
- Self-host the core product
- Run the same robot code against simulation and the real robot without a rewrite
- Inspect live topics, logs, and state on a deployed robot remotely to debug issues
- Teleoperate a remote robot with live video and responsive control over real-world networks
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
1 of 7 testable claims verified · 0 contradicted → integrity 14/100
23 distinct capability claims found in ROS 2’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
1
Verified
6
Unverified
0
Contradicted
21
Undersold
Verified (1)
“Provides service introspection to inspect service call traffic for debugging”
Inspect live topics, logs, and state on a deployed robot remotely to debug issuesfullproof ↗
Unverified (6)
“Offers tunable Quality-of-Service policies (reliability, best-effort, etc.) for handling unreliable networks”
My robots keep operating and buffer data locally when cloud connectivity drops, then recover cleanlypartialproof ↗
“Client libraries available in multiple programming languages (C++, Python, etc.) for building ROS 2 applications”
Build against official, typed SDKs in multiple languages (Python, TypeScript, Go, C++) that cover the platform's full surfacepartialproof ↗
“Ships a command-line tool suite (ros2 CLI) for introspecting nodes, topics, services and more”
“Secures inter-node communication with encryption and participant authentication via DDS-Security/sros2 tooling”
Control with roles and permissions who is allowed to command, configure, or view each robotpartialproof ↗
“Can launch a full physics simulation of a robot in Gazebo integrated with ROS 2”
Simulate my robot and its environment with realistic physics and sensor models before touching hardwarepartialproof ↗
“Supports recording and replaying robot data via rosbag, including a Python API for reading/writing bags from code”
Capture sensor and telemetry data on-robot and sync it to the cloud with bandwidth-aware policiespartialproof ↗
Undersold (21)
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Issue scoped/least-privilege API credentials for an agentpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Swap sensors and actuators behind stable hardware-abstraction interfaces without rewriting application codepartialproof ↗
Pull reusable packages or modules from a registry or ecosystem for common hardware and behaviorspartialproof ↗
Integrate cameras, lidars, IMUs, and GPS with ready-made drivers and standard message typespartialproof ↗
Query and export collected robot data through an API or SQL for offline analysispartialproof ↗
Feed collected robot data into model training and deploy the improved model back to the fleetpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
Implement emergency-stop and safety-interlock patterns the platform documents and supportspartialproof ↗
Have an AI agent authenticate with scoped credentials and command a real robot end-to-end through the platform's API or SDKpartialproof ↗
Run the same robot code against simulation and the real robot without a rewritefullproof ↗
Teleoperate a remote robot with live video and responsive control over real-world networkspartialproof ↗
Claims outside our story set (16)
Real capability claims found in ROS 2’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Supports multiple DDS middleware implementations, selectable at runtime”
source ↗“Provides a bridge for communication between ROS 1 and ROS 2 systems”
source ↗“Allows composing node components at compile, link, load, or run time”
source ↗“Supports nodes with managed lifecycles (state machine for startup/shutdown)”
source ↗“Includes a launch system to coordinate startup of multiple nodes”
source ↗“Core communication patterns: publish/subscribe topics, request/response services, and long-running actions with feedback”
source ↗“Provides built-in topic statistics to monitor message behavior on subscriptions”
source ↗“Default middleware (Fast DDS) can be swapped for another RMW implementation at runtime”
source ↗“Provides parameter get/set functionality for node configuration”
source ↗“Uses the same API for both inter-process and intra-process communication”
source ↗“Supports multiple executors at the callback-group level within a single node”
source ↗“Supports static remapping of ROS names”
source ↗“Has preliminary support for real-time code execution”
source ↗“Supports content-filtering subscriptions to reduce unwanted message delivery”
source ↗“Offers a ROS-Base install option with just communication libraries, message packages, and CLI tools (no GUI)”
source ↗“ROS is a set of software libraries and tools for building robot applications, from drivers to advanced algorithms”
source ↗
Business model
Free, Apache-2.0 open source robotics middleware governed by the Open Source Robotics Foundation; no paid tiers, sustained by OSRF membership and community contributions.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents