EventSourcingDB Auditing Services
EventSourcingDB chains every event to the one before it. Auditing Services checks that chain continuously and hands its fingerprints to an external custodian, so that a change to stored events no longer goes unnoticed – not even one made by whoever runs the database. The events themselves never leave your infrastructure.
Early access – available on request, ahead of the general release.
- License
- Proprietary
- Runs on
- Container, Linux, macOS, Windows
- Speaks
- HTTP
Tamper-evident only counts if someone else keeps the evidence.
A single changed event breaks the hash chain of EventSourcingDB. But whoever controls the database can rewrite the chain from that event onward, and it looks intact again. Proof that holds up in an audit needs a witness outside your own reach.
- Only fingerprints leave your infrastructure. A client next to your database sends the ID and the hash of the latest event, never the events themselves.
- Every fingerprint gets a receipt. The custodian answers with a signed receipt, chained to the one before, and you keep every one of them.
- Every hour gets a qualified time stamp. An hourly anchor over all receipts is time stamped under eIDAS, and the chain of anchors is public.
$ eventsourcingdb-auditing-services-client grant-audit-access \
--api-token <api-token> \
--until 2026-12-31
An auditor gets read access of their own, limited in time and revocable at any moment, and checks the history with the open-source verifier instead of trusting an export.
Planning something bigger?
Whether you need a quote, support, or a second opinion on your architecture – we are happy to help.