One Qualified Timestamp. Ten Thousand Documents. Full Legal Standing for Each.
TrustBeat batches your hashes into a Merkle tree every 10 minutes and anchors the root with a single eIDAS-qualified timestamp. Every document gets its own inclusion proof — legally binding under eIDAS Art. 41, at a fraction of the per-stamp cost.
Thousands of hashes · 1 qualified timestamp · every 10 min
Try it now — no account needed
Hash Your File in 3 Seconds
Drop any file below. SHA-256 is computed entirely in your browser — your file never leaves this tab.
Drop a file here
or click to browse — any file type, any size
Use cases
Built for teams who can't afford proof gaps
Qualified integrity records at scale — for every workflow that carries legal, regulatory, or operational weight.
Development & DevOps
Your CI pipeline ships dozens of release artifacts a week. Paying per-document TSA rates doesn't scale — so most teams skip qualified timestamps entirely and hope nothing is ever challenged.
Anchor every artifact in one API call. Under €0.001 per proof via Merkle batching.
NIS2-obligated organisations
Banks, telecoms, healthcare, and critical infrastructure operators under NIS2 Art. 21 must keep tamper-evident incident logs. If an auditor questions a record's integrity, the burden of proof is on you — unless you have a qualified timestamp.
Anchor log batches automatically. eIDAS Art. 41 reverses the burden of proof.
High-risk AI systems
EU AI Act Annex III requires immutable records of every decision your model makes. If a decision is challenged, you need to prove what the model decided, on what input, and when — not just what it does today.
Anchor input, output, and metadata at decision time. Article 12 compliant.
Finance & accounting
Tax authorities can challenge when a document was created. A backdated invoice, a retroactively adjusted contract, a tax return with a disputed filing date — without a trusted timestamp, the document's date is metadata anyone can edit.
Anchor invoices and tax documents at creation. A qualified timestamp is legally presumed to prove the date under eIDAS Art. 41 — in every EU member state.
Four Ways to Trust
Choose the product that fits your workflow — or combine them.
Document Anchoring
One eIDAS timestamp anchors thousands of documents per batch.
- Thousands of hashes per 10-minute cycle
- Cryptographic inclusion proof per document
- Files never leave your system — hashes only
- 30-year recursive archive stamping included
- From < €0.001 per proof
Tamper-Evident Logs
Bind log content, source identity, and time window to a single eIDAS-qualified proof. NIS2 Art. 21 and ZoKB 2026 ready.
- Combined hash seals log content + metadata — source, tenant, time window
- Metadata canonicalised with RFC 8785 JCS — tamper-evident, deterministic
- Batched eIDAS-qualified timestamp — same 30-year archive chain as Document Anchoring
- Audit-ready verification: VERIFIED / FAILED with CryptoAgilityReport per submission
- Hash-agnostic — anchor logs from any source: filesystem, S3, Kafka, database, or application events
AI Decision Anchoring
Qualified tamper-proof records of every AI decision. Prove your model was compliant at the moment it decided — not just today. Privacy-safe: only hashes, never raw data.
- Anchors input hash + output hash + model metadata in a single eIDAS-qualified proof
- Article 12 record keeping — immutable evidence for high-risk AI systems (Annex III)
- Article 14 human oversight flag — recorded and cryptographically bound per decision
- Privacy-safe by design — raw inputs and outputs never leave your system
- Same Merkle + LTV archive chain — proof valid for 30+ years under eIDAS
Audit Trail
Structured, queryable, tamper-evident event ledger anchored with eIDAS-qualified timestamps. Every event becomes a court-admissible entry that no one can silently alter.
- Submit events via SDK or REST API — 202 response, never blocks
- Merkle-batched anchoring every 10 min — per-event inclusion proof
- Filter and browse your trail by actor, action, resource, date range
- Export court-admissible ZIP: events.jsonl + proofs + VERIFY.md
- Offline verification — auditors need no TrustBeat account
EU Digital Identity
Accept EUDI Wallet credentials in your application. Verify PID, eID, and mobile driving licences from any conformant European wallet via a simple QR scan.
- OID4VP (HAIP) session flow — QR code generated in one API call
- SD-JWT VC, JWT-VC, and ISO 18013-5 mDL — all three ARF credential formats
- Trust anchors synced daily from the EU Trusted List (ETSI TS 119 612)
- Selective disclosure — request only the claims your application needs
- Token Status List revocation check included per verification
Anchor a file in five lines
Five zero-dependency SDKs. One call. A legally-presumed eIDAS timestamp in your next batch.
$ pip install trustbeatfrom trustbeat import TrustBeat
tb = TrustBeat(api_key="YOUR_API_KEY")
job = tb.anchor_file("contract.pdf")
print(job.id) # → 01JQ...How One Timestamp Covers Thousands of Documents
Every 10 minutes, a single eIDAS-qualified timestamp mathematically anchors every hash submitted in that window.
Collect
Documents are hashed locally in your browser or application. Only the 64-character SHA-256 fingerprint is ever transmitted — your file never leaves your system.
Anchor
TrustBeat assembles all submitted hashes into a Merkle tree and sends the single root hash to an eIDAS-qualified Trust Service Provider. One timestamp. Thousands of documents.
Prove
Each document receives a cryptographic inclusion proof — a Merkle path that mathematically proves it was in the batch, valid under eIDAS Regulation Art. 41 for 30 years.
Qualified
For auditors, regulators, and recipients
You received a TrustBeat certificate. Now what?
Anyone can verify a document independently — no account, no software, no trust in TrustBeat required.
Open the verify page
Go to trustbeat.eu/verify. No login, no download, no plugin. Works in any browser.
Drop the document
Drop the original file. Its SHA-256 hash is computed locally in your browser — the file never leaves your machine.
Proof verified
The Merkle path is re-derived and checked against the eIDAS-qualified timestamp. You see the exact time and QTSP — independently, with zero trust in us.
No account needed · Works in any browser · eIDAS legally binding
Recursive Integrity Timeline
Your data doesn't exist in just one moment — TrustBeat carries it forward, automatically, decade after decade.
Origin — eIDAS-Qualified Anchor
Your document hash is sealed with an eIDAS-qualified timestamp from an eIDAS-qualified QTSP on the EU Trusted List. The timestamp carries full legal presumption of integrity.
Archive Seal #1 — LTV Extension
Before the original QTSA certificate expires, TrustBeat automatically wraps the proof in a new qualified timestamp — covering the original token, its certificate chain, and OCSP revocation evidence. The trust chain remains unbroken.
Quantum-Resistant Layer — Planned
As post-quantum cryptography standards mature, TrustBeat plans automated re-stamping using next-generation algorithms. Your proofs remain valid long after today's cryptographic assumptions are superseded.
Technical FAQ
The questions a CTO asks. Answered with EU law and hard cryptography.
Ready to anchor your first document?
Start free. No credit card required. Your first 100 hashes are on us.
eIDAS Regulation (EU) No 910/2014 · Art. 41 legal presumption · EU Trusted List QTSP