Skip to content

Open core

The diagnostic layer for robots and PLCs

Cut downtime from hours to minutes: see which node broke, approve a fix that worked before, and ship it back over the air.

Three vendors fail one after another - Allen-Bradley, Beckhoff, Siemens - and one box on the DIN rail sees the whole cascade. The AI traces the root cause and a technician verdict teaches it. The repeat fault is answered from memory in 3 ms. Every screen is the real product.

Conference

ROSCon 2026

Toronto · September 22-24

Our talk

Production diagnostics for ROS 2: fault lifecycle, freeze-frame ring buffer, SOVD REST surface

Talk details
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

01 /Workflow

From fault to fix - with you in control

Three steps. A human signs off on every change.

01

See it

A fault anywhere in the fleet lands in one SOVD view, with a freeze-frame of every value at that moment.

02

Understand it

A deterministic matcher ranks causes against every incident your fleet has seen - about 40% faster to root cause.

03

Fix it - your call

Your operator picks from fixes proven on your fleet - one click to approve, and the signed OTA update ships.

02 /Approach

Observability says it broke. Diagnostics gets it fixed.

Observability was built for cloud software, not mass production. You cannot stream terabytes a day from every robot, and a dashboard fixes nothing. Diagnostics captures structured faults at the moment of failure, on top of whatever you already run.

1.5 TB

Continuous recording

per robot per day - the fault buried somewhere in those 24 hours

414 MB

Fault-scoped capture

per fault record - full context from the moment of failure

~360x

Less data per day

measured on a ROS 2 robot, ten faults a day

See the math on a real robot

Now watch it happen:

ROS 2 fault forensics with ros2_medkit - a real fault on a Yahboomcar M3 Pro

03 /Products

One diagnostic layer for robots and PLCs

Different vendors, one plant, one fault tree - from the open-source Medkit core to guided triage and a plant-floor appliance.

04 /Trust

Your infrastructure. Your data. Your control.

Built to run in regulated environments - diagnostic data never has to leave your network.

Runs where your robots run

Deploy on-prem, in your VPC, or fully air-gapped. The diagnostic gateway needs no outbound connection.

Access under control

JWT authentication with viewer, operator, configurator, and admin roles. All API traffic is TLS-encrypted and follows the SOVD authentication model.

Signed, reversible OTA

Updates are signature-verified and health-gated, with automatic rollback driven by the diagnostic gateway.

AI that answers to you

The diagnostic core is deterministic - no embeddings, nothing hidden. Run AI fully on-prem or connect your assistant under consent. Every suggestion is logged.

Full security model

05 /Vision

Where this is going

The goal: fleets that detect, diagnose, and repair themselves. Once a fix has proven itself enough times, you let it run without asking.

Built by diagnostics engineers

selfpatch is a product company founded by engineers from automotive diagnostics and software-defined vehicles. We build one diagnostic layer for robots and PLCs from different vendors in the same plant.

About the company

See selfpatch on your fleet

Tell us your stack - we'll show which of your recurring faults it could already resolve.