Skip to content
Commercial

Medkit Pro

See and fix your whole fleet - every robot and PLC, one view

A production fleet is not all ROS 2, and a fault rarely stays on one machine. Every vendor has its own tool, an update can brick a robot, and the same fault gets re-diagnosed from scratch every time.

The commercial layer on the open-source core: every robot, PLC, and ECU behind one diagnostic API, with safe OTA and guided triage on top.

Commercial license - talk to us

Apache 2.0 coreSOVD · ISO 17978-3On-prem & air-gapped

Why Pro pays off

Time to root cause~40% faster

Manual triage

Medkit Pro guided triage

Signed, health-gated OTA with automatic rollback
One fleet view across every vendor
Every fix compounds into reusable knowledge

On-prem · your model · no external model calls

The self-healing loop

01Open core

Observe

Capture around the fault, not the firehose.

02Pro

Diagnose

Classify the real root cause - measured ~40% faster with fault correlation.

03Pro

Fix

Agent on rails: bounded, your model, human-approved.

04Pro

Verify

The fix is checked and the loop closes.

05Pro

Learn

Every fix becomes a reusable knowledge unit.

Knowledge compounds. Every fix makes the next robot, line, and customer cheaper to heal.

What changes for you

One cross-vendor incident in one place: the PLC fault and the robot it stranded, side by side.
Update campaigns gated on live device health, with automatic rollback.
Recurring faults get a ranked, proven fix, not another from-scratch hunt.

What's included

More protocols & runtimes

UDS in development

ROS 2 and PLCs (OPC-UA) ship in the open core. Pro adds UDS for ECUs, custom protocol bridges, and runtimes beyond ROS 2, with J1939 and ISOBUS on the roadmap.

Safety-critical runtimes

Live on RTMaps 5 + eMCOS RTOS

rtmaps_medkit serves the same SOVD diagnostics from inside RTMaps 5, the ISO 26262 ASIL-B real-time runtime, already running on the eSOL eMCOS safety RTOS. Because the contract is SOVD and not the runtime, the same bridge fits other safety middleware too.

Secure OTA

Available

Updates are signed, gated on live device health, and rolled back automatically if the gate fails. Stage campaigns across the fleet instead of driving to every site.

Fleet

Gateway live · UI rolling out

One endpoint fans out to every Medkit gateway across robots and PLCs, so the whole site reads as one faults view, across vendors.

Guided triage

Available

A deterministic matcher ranks likely causes against past incidents, about 40% faster to root cause, and proposes fixes that have worked before. Your operator approves, and each resolved fault becomes a reusable unit so the next one is cheaper. No external model calls.

Key capabilities

UDS, custom bridges, and runtimes beyond ROS 2
Safety side: SOVD inside RTMaps 5 (ISO 26262 ASIL-B), on the eMCOS RTOS
Signed, health-gated OTA with automatic rollback
One fleet view across every gateway and vendor
Guided triage: ranked, proven fixes
On-prem or air-gapped, no external model calls

Where it fits

ROS 2 robotsMedkitPLCsMedkit + OPC-UAECUsMedkit + UDSfan-outMedkit Profleet · OTA · triageone viewOne fleet viewacross vendors

One diagnostic layer for the whole stack, not one tool per vendor.

How to get it

Licensed on top of Medkit. Most teams start with a pilot on one mixed cell, then license fleet-wide.

Apache 2.0An open core you can inspect and trustISO 17978-3Built on the international SOVD standardOn the deviceOn-prem and air-gapped - no cloud requiredAny stackROS 2 today; PLCs and ECUs through Pro bridges

See 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.