Transaction monitoring
Your team and your AI agents work TM alerts on Forest. Pre-process false positives, build cases, route to investigation, all from one workspace above your detection engines.
Forest is where your team and your AI agents work transaction monitoring. Detection engines feed alerts in. Triage cuts the noise. Cases promote to investigation. The audit trail follows the work.
Alerts from every engine, one queue
Sardine, Hawk AI, Featurespace, Unit21, and your in-house models feed alerts into one inbox on Forest. Your analysts work one screen, not five.
AI pre-processing cuts the noise
Your AI agents resolve repeated false-positive patterns, propose verdicts, and draft analyst notes. Reviewer time goes to real risk, not noise.
Case promotion to investigation
When an alert needs deeper work, your analyst promotes it to a case with one click. Linked transactions, customer record, and prior history attach automatically.
Cross-rail visibility
Card, account, SEPA, FX, and on-chain transactions live as datasources on Forest. One customer view spans every rail, no matter which engine flagged it.
AI agents under your governance
Your AI agents act on alerts under human-in-the-loop approval where regulation requires. Every reasoning step logs to the case. RBAC and audit trail are the same as your humans.
Full alert-to-decision audit
Every alert, every analyst action, every AI verdict, every override logs with the full causal chain. Filtered exports for ACPR or any supervisor run in one click.

Built for regulated fintechs at scale
A 360-view of each alert
Transaction, customer, prior cases, AI agent reasoning, and analyst notes on the same record. The decision lives in one place.
Governance for humans and AI agents
Approvals, RBAC, and audit apply to your analysts and your AI agents the same way. One trail, one set of rules.
Detection engines, fully connected
Sardine, Hawk AI, Featurespace, Unit21, Hummingbird, and your in-house models ready to tap from your workflows. Add an engine or run two in parallel without re-platforming.
Vendor agnostic
Frequently asked questions
You still have question ?
Book a conversation with a forest expert
Does Forest detect, or just orchestrate?
Forest does not detect, your TM engines do. Forest is the operational layer above them: alert aggregation, AI triage, case promotion, investigation handoff, audit trail. Detection logic stays where it belongs (your engine), the work stays where your team needs it (Forest).
Can I run Forest above multiple TM engines?
Yes. Forest aggregates alerts across engines into one queue with the source tagged on each case. You can run Sardine for card alerts, Hawk AI for account alerts, an in-house model for FX, and Chainalysis for on-chain, with one analyst view.
How do AI agents help with TM triage?
Your AI agents resolve repeated false-positive patterns, propose verdicts on low-complexity alerts, and draft analyst notes for review. On Forest, every AI agent action runs with human-in-the-loop approval where regulation requires.
How does Forest handle cross-rail monitoring?
Card, account, SEPA, FX, and on-chain transactions connect as datasources on Forest. One customer record spans every rail, so analysts see the full picture even when the alert came from a single-rail engine.
How fast can my team deploy a new TM workflow?
Forest ships TM triage templates that your team configures without engineering. New workflows go live in days, not months. The Forest team helps you map your engine outputs into the case schema during onboarding.
How do I include sanctions screening in a TM workflow?
When a TM alert involves a counterparty, your workflow can call sanctions screening as a configured step (see [[sanctions-screening]]). The hit attaches to the case and routes the right way per your rules.
How does Forest log every TM decision?
Every alert, every analyst action, every AI verdict, every promotion to investigation logs with the full causal chain inside your own infrastructure. The 5-year retention AMLR requires runs by default.

