Medkit
Every node behind one REST diagnostic API
Triaging a ROS 2 robot still means SSH, ros2 topic echo, and a folder of one-off scripts - and none of it survives the next robot.
A REST diagnostic API for your ROS 2 graph: discover nodes, read live data, trigger operations, manage configuration and faults. Apache 2.0, with a web UI and an MCP adapter.
Free, Apache 2.0 - shipped in the official ROS 2 distribution for Jazzy and Humble

What changes for you
Key capabilities
Where it fits
Medkit sits in front of your ROS 2 graph - and your PLCs over OPC-UA - as a standard SOVD (ISO 17978-3) diagnostic API. Open core, no lock-in.
Free vs Pro
Medkit (open core)
- REST diagnostic API for ROS 2
- OPC-UA bridge for PLCs
- Discovery, faults, operations, configuration
- Web UI + MCP adapter
- Apache 2.0
Medkit Pro
- More protocol bridges - UDS for ECUs and custom protocols built to order
- Runtimes beyond ROS 2 - classic ECUs (UDS/DoIP), AUTOSAR, custom RTOS
- Signature-verified, health-gated OTA with automatic rollback
- Fleet view and guided triage
- Commercial support
See it in action
How to get it
Install from GitHub and point it at your ROS 2 graph - no license key, no registration, a working diagnostic plane the same day. Talk to us when you want protocol bridges, OTA, or guided triage on top.
Medkit on GitHubRelated products & services
See and fix your whole fleet - every robot and PLC, one view
Learn morePLC diagnostics today. Robot-ready tomorrow.
Learn moreThe observability you build while prototyping should not disappear at deployment.
Learn moreFull system visibility with SOVD: robots, PLCs, and ECUs behind one diagnostic API.
Learn moreSee selfpatch on your fleet
Tell us about your stack. We'll show you how the diagnostic layer fits - and which of your recurring faults it could already resolve.