Request a pilot
One event stream, sealed end to end
Deliberately small. You choose one stream worth proving, subscribe, and run it end to end — sealed, exported, and verified by someone outside your team.
Where to startNo. 000001
- scope
- one event stream
- runs on
- a box, in your environment or ours
- proves
- seal · verify · tamper-fail
- leaves with
- receipts you can hand to a third party
Receipts are checked against the public log and Bitcoin, never against the box.
Tell us what you need to prove
One stream, described in a sentence or two, is enough to start. We reply with what it would take to run it, and you subscribe and test it.
What we ask
What you build, who audits you, the stream you would start with, and whose environment it runs in.
What you do
Send your own events, watch them sealed, then change one byte and watch verification fail.
What you keep
Receipts. Checking one asks the published key, the public log and Bitcoin — never the box that issued it, which may be gone or in dispute.
Want to look around first? The beta console is open to register and explore, and hard questions are welcome on their own — start with the trust model and tell us what it misses.