Every institution that onboards clients across more than one jurisdiction has lived the same problem. Every new regime means a new rulebook, a new risk matrix, a new form library, a new set of local requirements. By the time you’re in 3 or 4 jurisdictions, your compliance function is not one function — it is several functions wearing the same T-shirt, each quietly running its own variant of the same work.
That is the status quo we built Tarth to answer. One platform. One workflow. Configurable by you, end to end, to every regulatory context your institution operates in — with no custom development, no engineering tickets, and no waiting on a vendor to catch up to your jurisdiction.
Configured by you, not by us
Tarth is not a platform we pre-configure for each jurisdiction. It is a platform that you configure — because configurability is the point.
For each jurisdiction, you shape:
- The rulebook — load the clauses and logic that apply
- The risk matrix — weightings, tiers, thresholds
- The client classification logic — including things like minimum-net-wealth thresholds, investor categorisation, and any jurisdiction-specific classification rules
- The screening configuration — lists, PEP rules, adverse media scope, disposition workflows
- The document requirements — what needs to be collected, in what form, for which client type
- The forms — the ones sent to the client, the ones kept on file
- The recommendation logic — how a risk rating maps to a recommended action
Every configuration can be saved as a group — a full jurisdiction profile — and tagged to the clients it applies to. An institution running in ADGM and DIFC has 2 groups. Add Cayman, and there are 3. Add BVI and the UK, and there are 5. One tool. Five saved groups. Every client tagged to the right one.
What this looks like per jurisdiction
The examples below are illustrative. They describe the kinds of configurations an institution might build on Tarth, not a regulatory recommendation. Configurations should always reflect your own compliance team’s interpretation of the rulebook in force.
ADGM (UAE)
Configure Tarth to the FSRA framework — client classification under the FSRA Conduct of Business rules, including a configurable proof-of-net-wealth threshold for professional client eligibility. CDD and EDD thresholds set to the FSRA AML module. Sanctions screening aligned to the UAE consolidated list alongside the UN and OFAC lists FSRA expects. Proof-of-address and UBO requirements per FSRA guidance. Save it as the ADGM group. Tag every ADGM client to it.
DIFC (UAE)
Configure Tarth to the DFSA framework — the DFSA Conduct of Business module, the DFSA AML rulebook, the specific client categorisation logic DFSA runs, and the screening scope DFSA expects. The workflow the DIFC team sees is identical to the ADGM team’s. The saved group underneath is different.
Cayman (CIMA)
Configure Tarth to the CIMA AML Regulations: know-your-investor requirements for mutual funds and private funds, beneficial ownership under the Beneficial Ownership Transparency Act, the specific PEP treatment CIMA expects, and the sanctions scope CIMA-supervised entities are expected to run. Save it as the Cayman group. Tag every Cayman fund to it.
BVI (FSC)
Configure Tarth to the BVI FSC AML framework, VIRRGIN beneficial ownership filing alignment, and the economic substance considerations BVI clients carry. Same workflow, BVI group underneath.
The UK (FCA)
Configure Tarth to FCA expectations — the Money Laundering Regulations 2017, JMLSG guidance, the FCA’s financial crime rulebook, the CDD and EDD thresholds UK firms are expected to apply, and the sanctions scope including the UK OFSI consolidated list. Save it as the UK group. Tag every UK client to it.
Without rebuilding. Without custom development.
This is the part that matters most. When your institution adds a new jurisdiction — a new fund in Cayman, a new entity in BVI, a UK arm — nothing gets rebuilt. No engineering ticket. No vendor escalation. No waiting. You configure a new group on the platform you already have, save it, tag the relevant clients to it, and the AI KYC agent executes against it from the next onboarding forward.
Configuration is self-serve. It sits in the compliance function, not in a vendor contract.
Why this matters
Institutions scale. New jurisdictions come with new funds, new entities, new markets. If every new jurisdiction means a new tool, a new implementation, a new team variant, scaling is slow and painful — and the compliance team pays the cost in rework.
A self-serve, configurable platform removes that tax. You scale across jurisdictions on your own terms. You own the configuration. You own the rulebook. You own the speed at which new jurisdictions get stood up.
Tarth is jurisdiction-agnostic by design, configurable per jurisdiction by your team, scalable across as many regulatory contexts as your institution operates in. Five jurisdictions today. Ten tomorrow. The workflow stays constant. The team stays intact. The onboarding file at the end of each one is built to the standard of the regulator that will read it.
That is what we built. That is what is running today.