Demonstration · Synthetic data

Updated: 7 October 2026

One local pattern.
The bank's decision.

Follow a fictional account through local transaction monitoring, from incoming payments to the analyst queue and signed decision log.

TRL 6. Synthetic data only. No production deployments.

Synthetic data · Synthetic example

Follow the bank's work.

Several payers in, money out within a day, a local pattern score, an analyst queue with a daily limit, a signed decision line, and the bank's own decision.

The walkthrough uses fictional people, accounts and payments. No detection rates or alert counts are claimed.

Separate engine tests

The agreed figures, with their limits.

500K

Entities under 2 seconds

500K entities under 2 seconds on the fixed synthetic fixture, with about 55K transactions. This is a detection test, not the full product cycle.

Synthetic data

Under 10 ms

Alert lifecycle, per alert

Alert lifecycle under 10 ms per alert, from a detection result to a persisted, queryable alert. Batch results are amortised per alert.

Synthetic data

Under 10 seconds

Federation bilateral round

Federation bilateral round under 10 seconds on TCP loopback development transport. Semi-honest security. This does not measure a real inter-bank network.

Synthetic data

Under 1 GB

Measured detection-pass VRAM

VRAM under 1 GB in the measured detection-pass working set after warm-up. Resident ingestion and model inference are excluded. This is not total-system memory.

Synthetic data
Read the benchmark methods and exclusions →