OhhO Proof
Prove the robot is safe before it ships.
Prove the robot is safe before it ships. OhhO Proof runs your robot through thousands of simulated scenarios, tracks regression and coverage, and assembles the evidence into a safety case.
- Scenario-based simulation testing
- Regression vs known-good builds
- Coverage map of tested conditions
- Failure / fault injection
- Versioned safety-case report
What you get
You wouldn't ship software without tests; a robot deserves more. OhhO Proof is the testing and validation product — it puts your robot through scenario-based trials in simulation and on hardware, and tells you, with evidence, whether it's ready.
Proof runs large batches of randomized scenarios — navigation, manipulation, edge cases and failure injection — across Gazebo and Isaac Sim, scoring each run against safety and task criteria. A coverage map shows what you've actually tested, not what you hope you have.
Every release is checked for regressions against the last known-good build, and the results roll up into a versioned safety case you can hand to QA, to OhhO Comply for certification, or to a customer who needs assurance.
Built to do the hard parts for you
Thousands of randomized navigation and manipulation scenarios across Gazebo and Isaac Sim.
Score each run against task success, collisions, safety-zone and timing criteria.
Every build is compared to the last known-good; regressions are flagged before release.
See which conditions — speeds, payloads, lighting, layouts — you've actually exercised.
Inject sensor dropouts, latency and actuator faults to test failure handling.
Results assemble into a versioned report that feeds OhhO Comply and your QA sign-off.
How it works
Pick suites or describe the conditions your robot must handle.
Proof executes batches across simulators in parallel.
See pass rates, regressions and the coverage map.
Generate a safety-case report for QA and Comply.
Specifications
- Simulators
- Gazebo Harmonic + Isaac Sim
- Scenarios
- Navigation, manipulation, edge cases, faults
- Scoring
- Task success, collisions, safety zones, timing
- Regression
- Versus last known-good build
- Coverage
- Condition-space coverage map
- Output
- Versioned safety-case report
Which plan do I need for OhhO Proof?
We recommend the Fleet plan. Hobby projects can validate single scenarios on Spark. Teams shipping to real users want Fleet for large-batch testing, coverage and fault injection; safety-critical programs choose Forge for custom scenarios and formal sign-off.
Common questions
No. Proof runs primarily in simulation, with optional hardware-in-the-loop runs for final validation.
Proof produces the test evidence; Comply files it as part of the certification record.
Works better together
Ready to build with OhhO Proof?
Start free and simulate first — no hardware required. Upgrade when you're ready to deploy.