01
Transaction monitoring
Ingest batches or score through an API. Deterministic rules retain thresholds, contributions, source rows, and run provenance.
Kestrel for banks
A bank AML operating surface built around evidence.
Transaction monitoring, investigations, and reporting packs in one traceable workflow—configured around your institution, controls, and reporting obligations.
Operating capability
The control record travels with the signal.
02
Investigation workspace
Turn alerts into assigned cases with entity context, evidence, notes, timelines, and a durable record of each disposition.
03
Reporting packs
Prepare a human-reviewed narrative and export the report with its supporting facts, decisions, and evidence chain.
04
Institution controls
Apply role-based access, team seats, audit events, retention, idempotent ingestion, and scoped operational limits.
Deployment and security
Scope the boundary before moving bank data.
Managed, customer-cloud, and on-premises patterns are assessed against integration and assurance requirements; the agreed model is written into the programme scope.
D-01
Data boundary
Hosting model, storage location, encryption, backup, and deletion are agreed in the implementation scope.
D-02
Integration
File formats, batch schedule, scoring API, identity provider, and downstream reporting interfaces are mapped before rollout.
D-03
Control design
Rules, thresholds, approval roles, retention, and evidence requirements are validated with compliance and security owners.
Jurisdiction packs are commissioned against local rules, data fields, report definitions, and supervisory expectations. A country pack is not represented as ready until that work is complete.
View the live Bangladesh edition →Scoped commercial path
Bring the data shape, control requirements, and operating volume.
Bank pricing is quoted after deployment, integration, jurisdiction work, support, and volume are bounded in writing.