Overview
The parts, and how they fit
Three things to understand: the platform, which holds who you are and what you may reach; the box, which takes your events and seals them; and verification, which anyone can do without an account.
What each part is
| Part | Who runs it | What it holds |
|---|---|---|
| Your Evidence Box | You, or us on your behalf | Your events, your keys, your chain. One machine, not shared. |
| The platform console | Us | Organisations, users, two-factor, and who may reach which box. No event data. |
| The public log | Us | Signed tree heads and proofs. No payloads, ever. |
| Bitcoin | Nobody | A time bound we cannot move, reached through OpenTimestamps. |
| The verifier | Whoever is checking | Runs anywhere. Needs a receipt, not an account. |
End to end
- Your application sends an event to your box, authenticated with a project key. The box answers in milliseconds with a hash you keep. That hash is your receipt.
- Shortly after, the box seals a batch: it chains the events, signs the batch, and commits it to a Merkle tree.
- The head of that tree is published to a log your box cannot reach or change, and later anchored in Bitcoin.
- Anyone you hand a receipt to can check it against the log and the anchor, with no account and no call to us.
Try it
The console is live in beta at demoplatform.entrail.io. Registration is open, so you can create an organisation and sign in while reading these pages. It is a beta environment rather than production: use it to try the system, not to hold evidence you need later.
Where to go next
- Send events if you are integrating today.
- Verify a receipt if you are checking someone else's evidence.
- How the platform works if you are setting up people and access.
What is not here
How managed boxes are provisioned, updated, monitored or reached for support is ours to operate and is not documented here. If you run your own box, everything you need is in these pages.