Skip to content

Services

Engineering services for ROS 2 production, diagnostics, and OTA

From prototype to production fleet: we harden ROS 2 systems, give them a standards-based diagnostic layer, and make updates safe to ship - whether we build it for you, integrate it into your stack, or advise your team. Built on the open-source Medkit core where it fits.

Not sure where to start?

Begin with a pilot - a paid, clearly bounded engagement that proves value on part of the fleet before a wider rollout.

Start a pilot

How an engagement runs

01A technical intro call - your stack, your failure modes, where the product fits.
02A scoped, paid pilot on a slice of your fleet with agreed success criteria.
03Fleet-wide rollout - licenses, integration, and a team that already knows your system.

Three ways to work with us

Project development

We build your project in these domains: protocol bridges, plugins, dashboards, complete diagnostic and OTA subsystems - delivered as tested code you own and keep.

Integration

We bring the diagnostic and update layer into your existing fleet: deployment on your infrastructure, bridges to your protocols, validation against your live system.

Consulting & training

Architecture reviews, SOVD / ISO 17978-3 alignment, fleet-rollout strategy, and triage programs - with the training your team needs to run it without us.

All three, in every domain below - and only for ROS 2 production, diagnostics, and OTA. We do not do generic robotics consulting.

01

ROS 2 to production

The observability you build while prototyping should not disappear at deployment. We develop and consult on exactly this transition: taking your ROS 2 project from research observability to mass-production diagnostics, on your codebase or on the Medkit core.

Engineer driving a screwdriver into a robot chassis on a steel workbench, warning labels on the frame

When you need this

Observability built during prototyping disappears at deployment
R&D and production run different stacks with different tooling
Fault history resets every time you ship

What we deliver

One diagnostic API across your R&D and production stacks
Migration support without losing observability
Fault history and knowledge carried across the transition
Production-readiness review of your ROS 2 graph

02

Diagnostics

Full system visibility with SOVD: robots, PLCs, and ECUs behind one diagnostic API. We build it into your project, integrate it with your fleet, or consult on the architecture - bridges, dashboards, fault correlation, and a triage program your team runs without us.

Technician keying a handheld machine-control pendant at an industrial machine in a dark workshop

When you need this

Every robot type has its own diagnostic scripts and dashboards
A protocol or system you rely on has no off-the-shelf bridge
MTTR keeps creeping up as the fleet grows

What we deliver

Protocol bridges and gateway deployment on your infrastructure
Custom plugins, operator dashboards, and Foxglove panels
Fault-correlation rules and remediation runbooks
SOVD / ISO 17978-3 architecture review and team training

03

OTA

Safe OTA is a discipline, not a feature. We develop update pipelines for your project and consult on rollout strategy: staged campaigns, health gates driven by diagnostics, automatic rollback, and updates that wait for proof the device is healthy.

Microwave relay tower with red aviation lights against a dark night sky

When you need this

Updating the fleet means driving to every site with a laptop
A bad update can take a whole shift of robots down
Update campaigns are hard to gate on actual device health

What we deliver

Signature-verified, health-gated update pipelines with automatic rollback
Staged fleet campaigns gated on diagnostic state
Integration with your existing update tooling
Rollback and recovery runbooks

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.