AURIUM captures every AML transaction monitoring decision with the data, rules and model behind it, so your team can replay it exactly and hand regulators evidence they can verify.
When a regulator asks why an alert fired, the answer depends on four things that change after the decision is made.
Follow one AML transaction monitoring alert from the original decision to its evidence record. The replay below runs a real deterministic engine in your browser, and the hashes are computed live.
Synthetic demonstration data. This is not a live bank integration.
Choose how the decision is rebuilt, then run it. The engine recomputes the outcome and compares it field by field with what was recorded.
Choose a mode and run the replay to see the comparison.
A structured record of the inputs, versions, execution context, replay comparison and integrity checks. It reflects the last replay you ran.
Generating…
Synthetic demonstration record. In production, evidence packs are also signed with AURIUM's Ed25519 key and verified with aurium verify-evidence.
AURIUM sits beside your monitoring system. It records each decision as it is made, and turns any one of them into evidence on request.
01 Encode
Rules, thresholds, models and policies become versioned artifacts, each named by its content hash.
POST /v1/artifacts
{ "kind": "ruleset", "name": "TM-RULES",
"version": "14.2.0", "rules": [ … ] }
→ 201 sha256:5f85…392d02 Capture
One call at each decision point stores the inputs, versions, external responses and output.
03 Replay
Replay uses the sealed record in an isolated process and compares every field with the original.
04 Verify
A signed evidence pack that anyone can check.
$ aurium verify-evidence pack.json PASS 11 of 11 checks VERIFIED
Logs tell you a decision happened. A replay shows how it was made, and proves that nothing has changed since.
A regulator's question becomes a lookup instead of a project. These are the outcomes a pilot is designed to measure.
Reduce the effort needed to reconstruct a historical decision. Analysts open one record instead of requesting data from several systems and teams.
Measured in a pilot by the time and number of hand-offs needed to assemble the full context of a sampled historical alert, before and with AURIUM.
Give compliance teams a structured record of the data, rules and execution context behind each decision, with integrity checks a third party can run.
Measured in a pilot by the share of sampled decisions whose inputs, rule versions and external responses can be produced in full.
Make it clear what happened, why it happened and which decision state produced the outcome, even after rules and models have changed.
Measured in a pilot by the share of sampled decisions that replay to an exact match, and how quickly any difference is explained.
We don't publish savings we haven't measured. A pilot sets your baseline first, then measures the change.
AURIUM's first application is AML transaction monitoring for UK banks and challenger banks: high-volume decisions, driven by rules and models, that a regulator can ask about years later.
Future expansion. Not available today.
A working session with your financial crime and technology leads. No production data is needed to start.
Prefer email? Write to mouaadliaa@gmail.com
Not yet. The replay engine, decision record and evidence verification are built and tested on synthetic AML data. We are looking for UK banks to take part in a first technical evaluation.
No. Your monitoring system keeps making the decisions. AURIUM sits beside it, records each decision with the state behind it, and makes that decision replayable and verifiable later.
Nothing confidential. We demonstrate on a representative synthetic sample. If we move to an evaluation, we agree data handling with your security team first.
Each decision records the exact rule, model and policy versions by content hash, and the engine itself is versioned. Later changes never alter how a past decision replays. You can also replay a past decision under a newer version to see exactly what would change.
The deployment is designed for AWS London (eu-west-2), single-tenant in an AWS account your bank controls, with encryption under your own keys. This infrastructure is written and validated, and not yet deployed.
Not yet, and we don't claim otherwise. An independent penetration test is planned before any production deployment, followed by SOC 2 and ISO 27001 readiness. We share architecture documents and test results during a technical evaluation.
Yes. Evidence packs are signed and include everything needed to re-run the decision. The verifier works offline with only the pack and AURIUM's public key.