Skip to the content

Trust

For IT, legal and safety teams checking a robot service before it reaches their site.

Models are approved and signed before they run

Every new model is tested before it reaches a robot. Every approved model carries a digital signature, and a robot refuses any model whose signature doesn't check.

How our robots stop

Four separate safety layers sit between a fault and the wheels. If one fails, the next still stops the robot.

  • The software checks every command and every sensor.
  • The drive stops when commands stop arriving.
  • Each motor stops itself when it hears nothing.
  • A hardwired emergency stop cuts power, with no software in the way.

A learned model can make a robot more careful. It can never override a stop.

Built the way a Mars rover is built

A Mars rover can't be repaired once it lands. So NASA's Jet Propulsion Laboratory writes its software to strict rules, and it publishes them.

Our robots work beside people, on sidewalks and in buildings. A mistake there can hurt someone. So we hold our safety software to the same rules. This is how.

  • Rehearse first. JPL checked its first AI-planned drive in a digital twin of the rover before sending it. Every change to how our robots drive is rehearsed in simulation and scored before it reaches a robot.
  • Keep a person in the loop. The rover's team approves what the rover isn't trusted to decide. A person approves the steps our robots aren't trusted to take alone.
  • Fail safe. When something goes wrong, a spacecraft drops into a safe mode. When a part fails, our robots stop safely and report what is missing.
  • Check the worst case. Perseverance checks its best paths against the worst case before it drives. Our robots check curbs and drops the same way.
  • Keep safety code simple enough to prove. JPL's Power of Ten rules do that. Our safety code follows them, checked on every change.
  • Test every condition. NASA tests its critical software until every condition is shown to change the result. Our safety-critical code is tested the same way.

These are practices NASA publishes. NASA hasn't reviewed or endorsed our work.

What this site collects

This site doesn't track you from site to site and sets no tracking cookies. A message sent through the contact form holds your name, your email address, your organisation if you give one, and what you wrote. Only our team can read it, and it is deleted a year after it arrives, or sooner if you ask.

Questions

Questions about your data or a robot's safety are welcome on the contact page.