Every command on the record.
Every machine on your sites is locked to your sites: it will not run software you did not authorise, it will not leave the boundary you drew, and every command it was ever given is on the record with a name against it. Where your data lives follows the contract, not the hardware it was captured on.
What it does
A machine on your site will not run software you did not authorise, and will not arm to a ground station it does not recognise. Everything it sends and everything it is told travels encrypted. None of that is a setting anybody has to remember to switch on.
The rest is bookkeeping you can hand straight to an owner: a boundary per site the machine holds itself to rather than a line in a plan, an audit entry for every command with a name and a time against it, retention set by your contract, and data held in the region that contract names. Every line of it reviewable by your security team.
In practice
- 01
The machine arrives locked to you
Every aircraft and robot is tied to your account before it ships to site, and will not run software you did not authorise. Nobody on site has to configure that, and nobody on site can undo it.
- 02
The boundary is the machine's, not the plan's
Boundary, ceiling and no-fly volumes are held by the machine itself. It will not cross the line you drew, even if somebody tells it to.
- 03
Log every command
Arm, take-off, waypoint change, override, download — each entry carries an operator ID and a timestamp, retained for the term of the contract and exportable for an owner's audit.
Spec
- SOFTWARE
- YOURS TO AUTHORISE
- LINKS
- ENCRYPTED END TO END
- BOUNDARY
- HELD BY THE MACHINE
- AUDIT
- 100% OF COMMANDS · LOGGED
100%
Commands written to the audit log