Capability

An audit trail your
examiner will accept.

From prompt to examiner, one audit chain. Each response the proxy delivers, and each request it blocks, is sealed into a tamper-evident, hash-linked record built to hand to a regulator, an examiner, or a board.

Request the sample examination package See a demo

Tamper-evident

Each response and each block, sealed and hash-linked.

Each event is hashed and chained to the one before it. Change a single record after the fact and the chain breaks, which is what lets an examiner verify it.

Even blocked requests are recorded; the denial is evidence too.
The integrity claim is computed by the proxy in your environment, never delegated.
"Audit logs" become examination-ready evidence: control-mapped and immutable.

Tamper-evident audit chain

each delivered response sealed & hash-linked, blocked requests too

allowedprev ⌀ → 9f3a1c
redactedprev 9f3a1c → 4b07e2
blockedprev 4b07e2 → 7e02b4

SHA-256 chain · examiner-verifiable

The examination package

What you hand to an examiner.

The audit trail renders into a package built around the artifacts a financial-services examiner actually asks for.

Model inventory

An inventory of every model in use, auto-populated from live traffic.

Control coverage

Which governance controls were active, in shadow or enforce, across the period.

Policy snapshot

The exact policy-as-code in force, versioned and attributable.

Integrity hash

A SHA-256 hash over the chain so an examiner can verify nothing was altered.

Where it lives

A WORM record, inside your environment.

The hash-chained record writes to a write-once, read-many store inside your environment: retention-locked object storage with a per-customer encryption key.

A local write-ahead buffer keeps capturing through downstream outages.
A 6-year retention floor on Fully Managed production, per FINRA 24-09.
Capture is proxy-side; no raw payload crosses the wire to a SaaS aggregator.

Examiner-verifiable

An Integrity Pack lets an examiner verify the chain independently: recompute the hashes, confirm the sequence, and check the record against the policy that produced it. The integrity primitive is the chain itself, so it holds across storage backends.

Independent verification

Your reviewer checks the record on their own machine.

The verifier that checks a Meilynx audit chain is published under an open-source license. Given an exported record set, it runs offline, with no Meilynx system in the loop.

01 · Export

Take the record with you

Export the records for the period under review. The reviewer holds a copy that no longer depends on our systems.

02 · Verify

Recompute the chain offline

The open-source verifier recomputes every hash and confirms the sequence. An edited, reordered or inserted record breaks the chain.

03 · Check the time

Independent timestamps

The proxy anchors the chain with RFC 3161 timestamp tokens from two independent timestamp authorities. A token shows that the anchored records existed by the time it states and have not changed since.

The verifier on GitHub

By the numbers

Designed for the long record.

Retention floor

6yr

Fully Managed production · FINRA 24-09

Chain integrity

SHA-256

Examiner-verifiable hash over the record

Storage

WORM

Retention-locked · per-customer encryption key

Outcomes recorded

100%

Allowed and blocked alike

The record, in context.

Inline policy enforcementEach enforcement decision is what the audit chain records.FINRA 24-09How the audit trail maps to AI supervision and recordkeeping.Sample examination packageSee the rendered artifact an examiner receives.

Examination package

See exactly what an examiner receives

Model inventory, control coverage, a governance policy snapshot, and a SHA-256 integrity hash, delivered by email.

Get the sample package See a demo

An audit trail yourexaminer will accept.