The problem
Why it matters.
Robots, drones and devices make decisions far from people. Their commands and records need to be provable after the fact.
With Roost
How Roost handles it.
01
CommandA command is issued to a machine.
02
PolicyRoost checks who may issue it.
03
SignThe command is signed by the quorum.
SIGNED
RecordMachine and command are on record.
What you get
In the console.
- Signed commands and firmware for fleets
- Runs on site with no outbound dependency
- Air-gapped sites are supported with files instead of a link
- Records survive the machine
AxowlacmeRoostM
Devices
2boxes
1pair
0alerts
| Serial | Site | Voters | Tamper | Firmware | Status |
|---|---|---|---|---|---|
| ROOST-26-0001 | Seoul HQ, vault floor | 3/3 | Armed | 1.1.0 (B) | Green |
| ROOST-26-0002 | Busan DR site | 3/3 | Armed | 1.1.0 (B) | Green |
Chip temp46–50 °C
Mesh100.1 %
TimeNTS · 8 ms
AttestationMatch
See Roost refuse an unapproved signature.
A 30-minute live demo with our engineers.