Sealed by designWORM · hash-chained · Merkle

Evidence a regulator can verify.
Not a report they have to trust.

Most audit logs are a table you are asked to believe. Amzaa's trail is sealed the moment each write happens and chained to the one before it, so altering any row breaks verification from that row onward. Publishing that root outside our database, into your hands, is the design, and the schema carries it. It is not yet delivered, and until it is, we say so. Once it is, rewriting history would mean changing a copy you already hold.

Try it

Tamper with a sealed record. Watch the chain break.

Change a value in a sealed row below, then re-verify. The tampered row and every row after it fail, because each hash depends on the one before. Shown here as an illustration of the behaviour.

Findings · sealed audit trail company 4 · WORM · hash-chained
chain verified · 5 of 5 rows intact · chain intact from first row to last

This is an illustration, not a live console. In the product the maths is real and the table is write-once. Publishing the signed root into your custody is designed and scheduled rather than shipped.

How the seal works

Four properties, and each one closes a way to cheat.

Chained

Every write includes a hash of the write before it. Change any record and its hash no longer matches, and neither does every record that followed. There is no quiet single edit.

Write-once

The trail is a WORM table. The database itself refuses updates and deletes on a sealed row. It is not a convention someone can turn off in settings.

Merkle-sealed

A Merkle root summarises every entry into one value. Verifying the root proves the whole trail at once, without re-reading every row, so it stays fast at millions of records.

Published outside

Signing that root and handing it to you, so it is held outside our database, is the design, and the schema carries it. It is not yet delivered to a customer, and we will not describe it as shipped until you can hold one. A trail whose both ends we control is arithmetic. A trail whose root you hold is evidence. Today the first half is real and the second is coming.

What it lets a regulator do

Hand them a replay. Let them check it without us in the room.

Because the trail is sealed, an examiner can be given a read-only replay of exactly what happened and when, and verify the chain themselves. External custody of the root, so they verify against a copy they hold, is designed and scheduled. Time-travel to any prior state. Place a legal hold. Prove completeness.

The difference between "trust our report" and "verify it yourself" is the whole point.

Verifyre-check the root, pass or fail
Replayread-only, any point in time
Holdfreeze records under legal hold
Provecompleteness, not just contents
Design partner programme

Bring us a record and try to change it without us knowing.

A small cohort of regulated banks, NBFCs and the firms that own them. Early access, real influence, pricing that holds.

We are pre-launch and we will not dress it up. There are no logos on this page because there are none to show. Come and try to break the chain.