AI & agents
What did the agent decide, and who approved it?
- Prompt, model version, stated reasoning, autonomy
- Recommendation and human approval in provable order
- Guardrails fired, elevated access, justification
- EU AI Act Article 14 · 21 CFR Part 11
AIEM · Application Information & Event Management
Logs show what happened.
enTrail proves it.
Application Information and Event Management: the record of what your application, your people and your agents did, sealed so nobody can rewrite it. Accountability and non-repudiation, provable by anyone.
enTrail does not replace your logs. It makes them trustworthy.
Evidence receiptNo. 000001
- event
- agent.decision.approve
- actor
- svc-triage (ai agent)
- sha256
- 9f2c4b71e0a8…e41a
- chain
- #48,219 ✓ continuous
- signed
- ed25519 ✓ valid
- anchor
- bitcoin block 968,349
✓ VERIFIED · by a stranger, from the receipt alone
Heart of the matter
Accountability you can name. Non-repudiation you can prove.
01
Every action has an owner
People, service accounts, machines and AI agents are all named actors. "The system did it" is not an answer.
02
The record cannot be denied
Sealed events cannot be altered, deleted, reordered or backdated. Not by your admins. Not by us.
03
Someone outside can check
Signed heads are published off your box and anchored in Bitcoin. Auditors verify without an account.
The pipeline
Capture. Seal. Verify. Export.
Capture
API, SDK, or the OpenTelemetry collectors you already run.
Attest & seal
Hash chain, Ed25519 signature, Merkle tree. Your exact bytes, never rewritten.
Verify
Signed tree heads published off the box, anchored in Bitcoin, checkable by anyone.
Export
Open formats anyone can check, for auditors, regulators and courts.
The 90-second demo
Change one byte. Watch it fail.
$ entrail verify 9f2c4b71e0a8…e41a
✓ payload hash matches the sealed bytes
✓ chain continuous · link 48,219 extends 48,218
✓ signature valid · ed25519
✓ anchored · bitcoin block 968,349, checked offline
$ entrail verify 9f2c4b71e0a8…e41a --payload tampered.json
✗ payload hash mismatch at byte 214
VERIFICATION FAILED
Built for
Two arguments worth winning
Regulated SaaS
Can you prove your audit trail was not edited?
- Evidence sealed outside the system that wrote it
- Service accounts and machines as first-class actors
- Right to erasure without breaking the chain
- SOC 2 · ISO 42001 evidence exports
Why it holds up
Never take our word for it
Open standards only
SHA-256, Ed25519, RFC 8785, RFC 6962. Published spec, golden test vectors, write your own verifier.
Anchored in Bitcoin
A time bound nobody controls, checkable offline without contacting us.
Append-only, provably
Consistency proofs show nothing was rewritten between any two points in your history.
Bring one event type you would hate to argue about.
That is the right pilot.