About Merus
From rosbag to diagnostic evidence. Diagnostics surface measured signals; AI reports explain likely causes without hiding the underlying metrics.
It starts with a rosbag: each diagnostic applies the modules that match the recording, ranks real failures, and turns robot logs into an engineering review a team can act on.
The diagnostic catalog contains 37 modules across timing, transport, transforms, sensors, navigation, control, and signal analysis. Expert AI agents use those metrics to explain likely causes, recommendations, and fixes instead of guessing from raw text.
Merus is built for production robotics teams that need repeatable checks, clear failure evidence, and data isolation for uploaded robot logs. The same diagnostic layer is designed to move from bag analysis toward runtime telemetry.
The name comes from the Latin merus: pure, unmixed, distilled. That is the product standard: keep the raw evidence inspectable, separate measured facts from model interpretation, and make every recommendation trace back to the bag.
For product access, commercial questions, or security contact support at merus.dev.