ZipLoom
Home
PricingSign InGet Your Live URL

own

Tamper-Evident Audit Log + Evidence Ledger

Every Gate Decision On A Hash Chain Your Auditor Can Verify.

Updated

At a glance

Every create, update, delete and deploy-gate decision goes into a hash-chained audit log. Export a signed evidence ledger of which deploys were fully gated.

  • Chained By The Database
  • Never A False Pass
  • An Evidence Ledger For Auditors
Sample. Every sensitive action and gate decision writes an audit row linked by hash to the one before. Verification replays the whole chain and reports any gap or edit.

Why it matters

An audit log that an admin can quietly edit proves nothing. When an incident review or an auditor asks what was checked before a release shipped, the answer has to hold up against someone who wishes it said something else.

Every sensitive action and every gate decision writes an audit row, and a database trigger links each row to the one before it by hash. An edit, a deletion or a gap breaks the chain, and verification replays the whole chain in the database to show where. Gate verdicts are recorded as passed, blocked, advisory or error, so a check that could not run is never stored as a pass. On Business plans, Owners and Admins export the evidence ledger as signed JSON or PDF.

Each Row Carries The Hash Of The One BeforeIllustration · sample data
row 1row 2row 3row 4prev #fb5prev #fdaprev #1024editedverification shows the breakpassed · blocked · advisory · error

What you get

Chained By The Database

Each audit row carries the hash of the one before it, computed inside Postgres. An edited or deleted row shows up as a broken chain — the log is tamper-evident, not just append-only by convention.

Never A False Pass

Every deploy gate — dependency, code, license, compliance and live posture — records passed, blocked, advisory or error. A gate that could not run is recorded as an error, never as a pass.

An Evidence Ledger For Auditors

Business plans export a signed ledger of every deploy: which gates ran, what they decided, and which deploys shipped fully gated — the question a SOC 2 auditor actually asks.

How It Works

  1. 1

    Every sensitive action and every gate decision writes an audit row.

  2. 2

    A database trigger links each row to the previous one by hash.

  3. 3

    Verification replays the whole chain in the database and reports any gap or edit.

  4. 4

    Owners and Admins on Business plans export the evidence ledger as signed JSON or PDF.

What this check inspects

  • Project, key, member and setting changes — field names recorded, secret values never.

  • Each deploy's gate verdicts, with scope: full, partial or failed-open.

  • Breaks in the chain: edits, deletions or gaps.

What it means when this fails

An audit log that an admin can quietly edit proves nothing. When an incident or an audit asks what was checked before a release shipped, the answer has to survive someone who wishes it said something else.

What it does not do

  • It is tamper-evident, not tamper-proof. A change cannot be hidden, because the chain breaks.

  • Viewing the chain in the console starts at LoomWorks, and the exportable ledger is Business and above.

Questions

Is it tamper-proof?
Tamper-evident: a change cannot be hidden, because the chain breaks. That is the property auditors rely on.
Which plans include it?
Every organization's sensitive actions are written to the tamper-evident chain. Viewing it in the console starts at LoomWorks; the exportable evidence ledger is Business and above.

Related features