How it works
Send events. Get evidence.
Chain of custody for your logs, time-stamped end to end.
Capture
Post to the API, use the SDK, or point an existing OpenTelemetry pipeline at it. Answered in milliseconds, already on disk.
Attest & seal
Your exact bytes are hashed, chained, signed with Ed25519 and committed to a Merkle tree. Nothing is reformatted first.
Verify
Signed tree heads go to a public log your box cannot reach, then into Bitcoin. Inclusion and consistency proofs on request.
Export
Open-format files with proofs attached. Erasure destroys the payload without breaking the chain.
Integration
Speaks OpenTelemetry
Same field names as the rest of your stack, including the generative AI conventions. OTLP maps with no translation, so you are probably already collecting what we need.
- TransportsOTLP collectors, REST API, SDK. No instrumentation rewrite.
- ValidationEvery field publishes its regex. Validate before you send.
- RejectsListed with the exact reason. Never billed, never in your chain.
- VersionsField definitions update like antivirus definitions. You choose when to switch.
- CryptoSHA-256 · Ed25519 · RFC 8785 · RFC 6962 · OpenTimestamps.
What we claim, and what we do not.
The short version is on the trust model page.