How commands are protected

1. 1

   You send a command

   Play, blank, identify or snapshot, from the dashboard or a phone.

2. 2

   It is signed

   Signed with your organization’s own key, never shared with another organization.

3. 3

   The screen verifies

   The screen checks the signature and ignores anything that does not match.

4. 4

   It is on record

   The result goes into a hash-chained audit log, checked every night.

• Its own signing keys

  Every organization has its own signing keys.

• Signed commands only

  Screens only obey signed commands.

• A chained audit log

  The audit log is hash-chained, so tampering shows.

• Organizations kept apart

  Organizations are isolated from each other, with rate limits on every route.

Your data stays yours: you can export your organization's data and close your account.