The independent black box for robots.
When a robot stops, collides or nearly hits someone, the robot, the facility and the people each keep a different record. Kinwit merges them onto one verified timeline, so you can see what happened, in what order, and prove the record wasn't changed.
The facility's stop broadcast came 11.8–18.0 ms before the robot received its stop input.
- E-003Zone B2 safety input opens00:11.000 · ±2.56 ms
- E-004Facility broadcasts stop00:11.003 · ±0.56 ms
- E-005Robot receives stop input00:11.018 · ±2.55 ms
- E-008Robot commands zero velocity00:11.050 · ±0.00 ms
- E-009Robot reports stationary00:11.930 · ±10.05 ms
Every robot incident has more than one clock. They disagree.
Robots and facility systems log what they saw, each on its own clock. Read side by side, the logs contradict each other, and the order of events is exactly what an investigation has to get right.
Capture. Align. Prove.
Three steps that turn scattered logs into evidence two parties can both check.
Every source keeps its own identity
Robot and facility records are preserved separately, each with its own clock, then sealed into one signed package.
Clock offset is measured, not assumed
Kinwit bounds the drift between clocks from 56 sync messages both systems already log. An order is only claimed when the time windows don't overlap.
Every finding traces back to bytes
Each finding cites the exact records it came from. Change any byte afterwards and verification fails at that chunk.
Change one bit. Watch the proof fail.
This runs Kinwit's actual verifier in your browser, on the sealed evidence package behind the demo case. It checks an Ed25519 signature and re-hashes all 21 chunks of the robot recording. Then it alters one bit in a copy and runs the same check again.
Downloads about 1.5 MB. Nothing is uploaded, and the sealed original is never modified. More experiments
For the people who have to answer “what happened?”
“What happened, in what order, and what should I inspect next?”
“Which recorded message supports this finding, exactly?”
“Is the record intact, and what does it not show?”
More robots, more vendors, more scrutiny.
Industrial robots were operating in factories worldwide in 2023, a record high.
The EU Machinery Regulation applies, adding safety requirements for machinery with autonomous behaviour.
In a mixed fleet, every record is held by a party to the incident. Nobody owns the shared, checkable version.
Real software today. Real fleets next.
Built and running
- Signed, multi-source evidence packages (Ed25519, SHA-256, Merkle trees)
- Clock alignment bounded from the sources' own sync messages
- Deterministic findings and reports, every value linked to recorded bytes
- Two independent verifiers that agree, in TypeScript and Python
- Hosted, with authenticated, audited, re-verifying ingest
Next
- Gazebo and ROS 2 Nav2 recordings in place of the kinematic simulator
- Pallet-obstruction and near-miss scenarios
- A read-only connector for a first design-partner fleet
- Third-party timestamps on sealed packages (RFC 3161)
Today's cases come from a deterministic warehouse simulation and are labelled as simulated throughout. Kinwit orders and measures events. It does not assign fault.
See the evidence, not the pitch.
Open a real casefile, scrub the timeline, and try to break the proof.