Solution Brief
Every alert investigated. Inside your controls.

Investigateevery alert.

A financial crimes agent on AMD Instinct™ MI350P.Triage, evidence, narrative and QA for every alert on one LIQID UltraStack server, with SAR data inside your walls.

10
GPUs
MI350P on one host, room for 30
1.44
TB
HBM3E on one server
9.5
×
triage scaling, 1 to 10 GPUs
0
hops
network hops between GPUs

The Alert Backlog Dilemma

Route alerts into a growing queue, or investigate every one on infrastructure you control.

Volume Pressure

Alerts outpace hiring

Alert volumes grow faster than investigator teams can hire.

Evidence eats the day

Investigators spend most of their time gathering evidence across systems.

Cost Pressure

$35–40B a year on AML

What U.S. financial institutions spend on AML operations.

Agents multiply tokens

Agentic workflows use 10–100× more tokens per task than one AI call.

Data Pressure

SAR data can’t leave

Customer and SAR data can’t go to a hosted model.

Models must be validated

Pinned, self-hosted models are easier to take through model risk review.

Triage It. Draft It. Sign It.

One 10-GPU LIQID UltraStack server runs every step after an alert lands. A small model routes it, a 70B model drafts the cited narrative, and a reasoning model checks it against known typologies.

  • Investigators review, edit and sign off every narrative
  • Owned capacity replaces per-token fees
  • Grow from 10 to 20 to 30 GPUs on the same host
GPU allocation for the investigation agent: pinned, self-hosted models in one investigation agent. 4 GPUs for alert triage, 4 for evidence and narrative, 2 for typology and QA, on a LIQID GPU chassis with 10 AMD Instinct MI350P and 1.44 TB HBM3E, connected over PCIe Gen 5 to one dual-socket AMD EPYC 9005 host with one OS image.

Alert Triage · 4 GPUs

Llama 3.1 8B replicas score and route every alert.

9.5×
scaling, 1 to 10 GPUs
44,383
tok/s, 7B-class, 10 GPUs

Evidence + Narrative · 4 GPUs

Llama 3.3 70B, one model per GPU, gathers evidence and drafts the SAR narrative.

1,256
tok/s, 72B-class, 8 GPUs
1 GPU
per 70B model at FP8

Typology Check + QA · 2 GPUs

gpt-oss-120b tests each draft against known typologies.

144 GB
HBM3E per MI350P
1 card
holds gpt-oss-120b
Measured results: LIQID Phase-3 testing on 1 to 20 MI350P GPUs on one host. Test conditions and notes on page 2.
LIQID UltraStack with AMD MI350P for Financial Services

Proof: Measured on MI350P

No cluster: three models, ten GPUs, one server, and the next job lands on the same host.

Result
What was measured
Why it matters here
9.5× scaling
1 to 10 GPUs, 7B-class
4,653 tok/s on 1 GPU to 44,383 tok/s on 10, one replica per GPU
Triage capacity grows with every GPU, with headroom to clear the backlog overnight
1,256 tok/s
on 8 GPUs
72B-class model, FP8, under interactive limits: P99 TTFT ≤ 2 s, ≥ 30 tok/s per user
Narrative drafting at interactive speed for investigators on live cases
1 GPU
per 70B model
Llama 3.3 70B is ~70 GB at FP8 and fits on one 144 GB MI350P with room for cache
Each step of the agent runs on its own GPUs, with no model split across cards
What it means
Every alert gets a first pass
Investigators verify cited narratives instead of retyping them
7B-class: FP4, one replica per GPU, concurrency 128. 72B-class: FP8, one replica per GPU, P99 time-to-first-token ≤ 2 s, ≥ 30 tok/s per user. Different test conditions; don't compare them. Source: LIQID Phase-3 testing. Llama 3.1 8B, Llama 3.3 70B and gpt-oss-120b performance for this layout is projected from these results.

Grow on the Same Server: 10, 20 and 30 GPUs

Add GPUs and a new job, not a new cluster.

Start here
10
GPUs
1.44 TB HBM3E

Financial crimes investigation agent

Triage, evidence, narrative and QA for every alert.

Model layout

4 × Llama 3.1 8B triage · 4 × Llama 3.3 70B evidence and narrative · 2 × gpt-oss-120b typology and QA

Who buys, why now

Head of Financial Crimes / BSA Officer. Alert backlog, exam findings, investigator attrition.

20
GPUs
2.88 TB HBM3E

Operations and compliance suite

A department’s jobs on one server: triage, loan and KYC extraction, complaints, credit memos and QA.

Model layout

4 × Llama 3.1 8B triage · 6 × Llama 3.3 70B extraction · 2 × Mistral Small 3.2 complaints · 4 × Llama 3.3 70B credit memos · 4 × gpt-oss-120b review and QA

Who buys, why now

COO / Head of Operations. Several pilots competing for GPUs; API bills growing.

30
GPUs
4.32 TB HBM3E

Bank-wide private model hub

Every line of business on one host, one model per GPU.

Model layout

10 × financial crimes · 8 × lending and KYC · 6 × customer service and complaints · 6 × gpt-oss-120b research and developer assistant

Who buys, why now

CIO / Head of AI Platform. Consolidating departmental AI onto one platform.

Model risk teams can run a production model and challenger copies on separate GPUs against identical inputs. Starting with one job? See the 4-GPU Classification and Triage brief.

What UltraStack Adds

  • One model per GPU: 144 GB HBM3E holds a full 70B model at FP8, or gpt-oss-120b.
  • No network between GPUs: peer-to-peer over PCIe Gen 5 to one EPYC host.
  • Air-cooled: about 22 kW for the full 30-GPU system.

Start Fixed, Grow on One Host

  • One host: one OS image, one license footprint, one thing to patch.
  • Room to grow: 10 to 20 to 30 GPUs on the same host.

What Is Proven Today

  • P2P bandwidth saturates the link; RCCL collectives pass, 1 to 10 GPUs.
  • ROCm integration complete, developed jointly with AMD.
  • 200+ production deployments, 85+ patents.
The Efficiency Case · Targets, not measurements*
75%
Up to 75% fewer servers
2.1×
Up to 2.1× more tokens per dollar
1.8×
Up to 1.8× better tokens per watt
50%
Up to 50% lower power

Bring Us Three Numbers

Two questions settle the size of the opportunity: how many alerts sit untouched today, and how long does each one take to close?

1
Alert volume:

alerts per month and the open backlog.

2
Case size:

documents and transactions per case.

3
Concurrency:

investigations working at peak.

Built for

Financial crimes · AML / BSA · Fraud investigations · Model risk management

Proven on

AMD Instinct™ MI350P · AMD EPYC™ 9005 · ROCm™ · 200+ LIQID deployments

*Efficiency targets compare against multi-server deployments of the same GPUs; they are LIQID internal projections using AMD published specifications, and results vary by configuration and workload.

Performance figures for the AMD Instinct MI350P are based on AMD published specifications and LIQID Phase-3 testing from 1 to 20 GPUs, and are subject to change. 30-GPU figures are projected from measured 20-GPU scaling. Every layout runs one model per GPU; 20- and 30-GPU layouts are sizing arithmetic on published model sizes, not benchmark results. Models shown are US and EU open-weight models. Outputs support, and do not replace, investigator decisions and SAR filing. AML spend: FIS, May 2026. Token data: Futurum Research, Sep 2026.

Speak With An Expert