SENTINEL
GoComply Sentinel

Detect compliance
pipeline failures
before regulators do.

Sentinel is a signal-detection engine for regulated banks. It finds the gaps in your compliance pipelines that cause A$700M–A$1.3B penalties — the same gaps that AUSTRAC found at CBA and Westpac, years too late.

Back-Test #1

CBA × AUSTRAC 2018

One transaction code not in the allowlist. 34 months of silence. 53,506 missing threshold transaction reports. A$700M penalty. Five signals that would have fired.

A$700M 53,506 TTRs 34 months

See the full back-test →

Back-Test #2

Westpac × AUSTRAC 2020

19.5 million IFTIs unreported through 4 correspondent banking relationships. 12 customers making payments for child exploitation material. A$1.3B penalty — the largest in Australian corporate history.

A$1.3B 19.5M IFTIs 72 months

See the full back-test →

Live Detector

Codebook-Drift Scanner

Paste your regulated data dictionary and pipeline allowlist. Sentinel computes the set difference and flags every code your compliance pipeline will silently drop. The exact failure mode behind the CBA 2018 penalty.

On-device No API keys Deterministic

Run it now →

How Sentinel works

Signal detection, not hand-waving.

01

Define the signal

Each signal is a pure, deterministic rule: codebook drift, coverage-ratio anomaly, NULL-rate spike, alert-rate divergence, SOP-to-regulation drift. No heuristics. Auditable by a regulator in two lines of pseudo-code.

02

Feed your data

Paste your data dictionaries, pipeline configurations, SOP text. Your data stays on-device — no API keys, no cloud AI dependency, no third-party model calls. Privacy-preserving by design.

03

Read the verdict

Sentinel fires or it doesn't. Every finding includes the exact codes, the exact threshold, the exact evidence. Board-pack-ready. Regulator-defensible.