Your robot recorded everything.It still can't tell you what broke.
Point it at your ROS 2 recordings or the live graph. Back comes what broke, the line to change, and who fixes it.
Installs today · runs on your machine · you choose what leaves it
Reads the stack you already run
- ros2_control
Names and logos belong to their owners. They say what TrialONE reads, not who endorses it.
Five steps from “it broke” to “fixed”.
Where the timeline is on record, maintainers of the public incidents we test on needed two hours to 111 days to find the cause.
A frozen camera. A topic that stopped. Timestamp drift. A joint commanded to move that did not. The faults your own diagnostics stay green through.
Find the moment
- Today
- Scrub through the bag.
- With TrialONE
- The run, and the second it went wrong.
Find the cause
- Today
- Guess, replay, guess again.
- With TrialONE
- The cause, with the numbers behind it.
Find the line
- Today
- Grep the whole stack.
- With TrialONE
- The file and line, or a clear “not found”.
Hand it off
- Today
- Write the ticket, ping the channel.
- With TrialONE
- A GitHub issue, Slack, or your coding agent.
Check the fix
- Today
- Wait and hope.
- With TrialONE
- The next recording closes it, or reopens it.
Your robot provides the reference. We isolate what changed.
01 / Compare
- Your recorded cycles
Compare 21 repetitions.
Repeated work gives a reference for comparison.
02 / Diagnose
- Measured deviations
5 stand out for closer inspection.
Find the unusual moments before digging into the cause.
03 / Act
- Software change
- Physical check
Choose the right next step.
A source change when the evidence supports it, or a hands-on check.
Hand the fix to your coding agent.
Your agent gets the evidence and the source context. Your team applies the change, then checks it against the next recording.
- Claude Code
- Codex
- Cursor
From diagnosis to a checked change
Inspect the diagnosis
Your agent receives the evidence, the suspected cause and any source location.
get_issue
Review the proposed change
Your agent can draft a change. Your team reviews it like any other pull request.
Apply the approved change
Apply it through your normal process and record the change. The issue stays in repair.
claim_repair
Check the next recording
A measured check shows whether the fault is gone or still present.
The right person hears about it. Nobody else gets woken up.
Real faults go where your team already works. Hints stay on the page.
Your team chooses where the issue goes. Connect only the destinations you use.
your robot
a recording or the live graph
TrialONE
fault, routed
- Slackthe alert
- Discordthe alert
- Emailthe assignee, escalated
- GitHuban issue with the recipe
- Foxglovethe recording
It runs on the robot and watches while it works.
Install it next to your stack. It stays quiet while the robot is healthy, tells you the moment something goes wrong, and keeps every run and every test as history.
Install it on the robot
One command, then a service that starts with the robot.
Runs on
- Linux
- Windows
- NVIDIA Jetson
- Raspberry Pi
Watch it live
Quiet while nothing changes. A real fault reaches your team while the robot is still running.
Listens to
- ROS 2
- CAN bus
- Arduino
- ESP32
- micro-ROS
Keep every run
Every run and every test session, on one timeline per robot.
Keeps
- Every run
- Every test session
- Every channel
- Every change
Names and logos belong to their owners. They say where TrialONE runs and what it reads, not who endorses it. Arduino® is a trademark of Arduino S.r.l.
Measured on real data.
Real robot recordings, reproduced software failures and repeatable checks. See the evidence behind the diagnosis.
reproduced reference cases across 38 open source projects
real flight recordings checked for driver and sensor-data inconsistencies
repeated control runs on faulty and repaired source code
Pilot teams
We are looking for our first robotics teams.
We onboard a few teams at a time and set TrialONE up on your robots together with you.
Approved by hand
A founder reads every request.
Set up with you
On your robots, in your stack.
A direct line
Straight to the people building it.
Start a pilot on your robot.
Bring one robot and a problem your team wants to solve. We help you set up TrialONE and check the outcome together.
A founder reviews your request and agrees the first case and data setup with your team.
Or talk through a pilot with us before you get started.
Two founders, TUM and LMU. You will talk to one of us, not a sales funnel.