MissionDebug Cloud

MissionDebug Cloud

A black box for your ROS 2 fleet, like the flight recorder on an aircraft, with the review dashboard built right into the Transitive portal. No separate hub to install.

MissionDebug always keeps the last window (60 seconds by default) of the topics you care about on each robot, and saves an MCAP snapshot the moment something goes wrong, or whenever you ask. MissionDebug Cloud then brings those captures into the portal: see every robot in your fleet, browse incidents across all of them, and replay a capture in the browser, all rendered from the cloud so it works even when a robot is offline.

• Runs and supervises the MissionDebug agent on each robot, restarting it automatically if it crashes. The agent is fetched on first start, so there is nothing to install by hand.
• Keeps a rolling in-memory buffer of the topics you choose, and writes an MCAP snapshot of the window leading up to an incident.
• Captures automatically when a detector fires (a stall: commanded to move but not moving; path deviation; low battery; a topic that stops publishing; or your own value-threshold triggers), or on demand from the portal. External systems, such as an anomaly detector, can also request a labeled capture.
• Scans the robot for live topics so you pick what to capture from a checklist, with honest badges for topics that have no publisher. No typing topic names by hand.
• Brings the whole fleet into the Transitive portal: a live status card per robot, a fleet-wide incident feed, and in-browser replay with a timeline scrubber, signal plots, camera frames, and a plain-language account of what triggered the capture. Every capture is also downloadable as a standard MCAP file.
• Lets you configure what to capture and what counts as an incident, per robot, from the portal. No SSH, no config files. Custom message types (for example px4_msgs) work by pointing the agent at your workspace setup file.

The MissionDebug agent and its self-hosted hub still run standalone via the .deb for air-gapped sites with no internet (warehouses, factories, defense). MissionDebug Cloud is the connected-fleet path: the same capture engine on the robot, but the review hub is the Transitive portal itself, with no separate machine to set up. The two are complementary; pick the one that fits where your robots run.

• ROS 2 (Humble or newer) on the robot.
• Ubuntu 22.04 or newer (the MissionDebug agent needs it).
• Outbound network from the robot (the capability fetches its agent and uploads captures to the cloud).

Working end to end: anomaly-triggered capture on the robot, verified upload to the cloud, a persistent fleet-wide incident feed, and in-browser replay in the portal. Free during early access. We are working closely with early users to decide what to build next; if you run robots and want the flight-recorder workflow, we would like to hear from you.