Robot Proof · by 861 Research & Technology

Prove what your robot did, and which software it ran.

A signed, append-only log of software versions, configuration changes, interventions and autonomous decisions. One HTTP call from your robot or gateway. Anyone can verify it without trusting us.

Start a 60-day pilot Try the live log ↓

Why now

20 January 2027

The EU Machinery Regulation (EU) 2023/1230 applies. Software counts as a safety component. Evidence of software versions and interventions must be kept for 5 years, and decision data of autonomous systems for 1 year.

Insurers ask for data

AI and robotics liability cover is new, and underwriters lack loss data. A clean, signed record of what happened is the cheapest way to a better quote.

Incidents end up in disputes

After a collision, a stop or a wrong pick, the question is always: which version, which setting, who changed it, what did the robot decide. A log you can edit proves nothing.

How it works

Your robot or fleet gateway sends an event: software version, config change, intervention, decision, safety stop.
We chain it to the previous entry (SHA-256) and sign it (Ed25519). You get a receipt back in milliseconds.
Export the log at any time. The file verifies offline with our public key. Changing one byte breaks the chain.

Live log — try it

This is the public demo fleet. Press a button, the event is signed on our server, then your browser checks the signature itself.

#	time (UTC)	robot	type	hash	signature

Download export (JSON)

API

One endpoint. Works from ROS 2, PLC gateways, Python, Node or curl.

curl -X POST https://sapir861.com/api/robot-proof/v1/events \ -H "Authorization: Bearer $RP_KEY" -H "content-type: application/json" \ -d '{"robot_id":"AMR-07","type":"software_version","data":{"nav":"4.2.1","safety_fw":"1.9.0"}}'

import os, requests def rp(robot, kind, data): r = requests.post("https://sapir861.com/api/robot-proof/v1/events", headers={"Authorization": "Bearer " + os.environ["RP_KEY"]}, json={"robot_id": robot, "type": kind, "data": data}, timeout=5) return r.json()["receipts"][0] # {n, hash, sig, ts} # ROS 2: call rp() from a node that listens to /diagnostics, # parameter events and your safety controller topics.

GET /api/robot-proof/v1/log · /v1/verify · /v1/export · /api/robot-proof/public-key · types: software_version, config_change, intervention, decision, safety_stop, incident, maintenance, note

Who uses it

Robot system integratorsAMR and cobot makers selling into the EURobot-as-a-Service operatorsHospitals, hotels and warehouses running service robotsInsurers and safety auditors

Pricing

Pilot

$2,900 · 60 days

Up to 20 robots, setup call, ROS 2 / gateway integration help, compliance evidence pack at the end.

Fleet

$39 per robot / month

Minimum 10 robots. Unlimited events, exports, verification API, 5-year retention.

Enterprise / self-hosted

from $1,500 / month

Your own keys and storage, on-prem or private cloud, SSO, custom retention, support SLA.

Questions

Is this a certification?

No. Robot Proof is an evidence tool. It helps you show what happened and supports your conformity work. It does not replace a notified body or your risk assessment.

Where is the data?

Hosted on Cloudflare's global network by default. Enterprise can run it on their own infrastructure with their own signing keys.

What if you disappear?

Every export is self-verifying with the public key. You do not need us to prove your log is intact.

How fast?

Event in, signed receipt out, usually well under a second. Batch up to 50 events per call.

Talk to us

Robot Proof supports evidence and record-keeping. It is not legal advice and not a conformity assessment.

Robot Proof — signed audit log for robots