AUDIT & COMPLIANCE
Audit, compliance & internal ledgers
Prove what happened, when, and who saw it — with primitives for evidence, not just storage.
THE STATUS QUO
Auditors ask "what did this account look like on March 3rd?" and the answer is a week of log archaeology — because the database only knows the present.
HOW EzraDB DOES IT
Query any table as it stood at any past moment (row engine) — point-in-time answers become a WHERE clause, not a restore drill.
Every audited action is BLAKE3-chained to the previous one — tampering breaks the chain, and the break is detectable.
Ledger-grade correctness: concurrent transactions behave as if they ran one at a time — no write-skew surprises in balances.
CREATE POLICY scopes every query to what the requester may see; sensitive columns are granted, not exposed.
Hand auditors a frozen, isolated copy of the database in under a second — they explore freely, production never notices.
Designed-for SOC 2 / HIPAA / PCI postures as the enterprise surface matures.
*In development — not yet production-ready.
IN PRACTICE
Compliance is a query surface. EzraDB treats it like one.
SELECT price FROM tt_prices AS OF SYSTEM TIME '-9m'
WHERE sym = 'AAPL' ORDER BY ts LIMIT 1;
-- column/hybrid tables raise 0A000 until v0.2
MORE WAYS TEAMS USE EzraDB