Inside your bank. Out of the transaction path.

Three single-tenant deployment models: on-premise (recommended for production), your own private cloud or VPC tenant, or a hybrid of the two. All use your own keys, and customer data never touches a shared multi-tenant cloud.

SITR connects through read-only adapters — Temenos T24, Oracle FLEXCUBE, or ISO 20022 feeds — or from a nightly extract or read replica. All data flows inbound; the system makes no writes to your core, so there is no contention with production transaction processing.

All data resides inside your environment and jurisdiction — nothing is replicated to an external region or vendor cloud. Transaction and contract data is processed transiently, in memory; only the compliance output (flags, determinations, rule registry, audit trail) is retained. No second copy of your core banking data is kept.

SITR sits beside the transaction flow, not within it, and screens asynchronously from the feed or extract. It adds no latency to the core and places no blocking load on transaction processing. If SITR is interrupted, no transaction is blocked — the core remains the system of record.

The reasoning model is open-weight and self-hosted in your tenant, so screening never depends on an external model provider and there is no egress to a public API. Deterministic checks run across the full population; the heavier model is invoked only on the smaller set of flagged transactions.

Every screening, flag, determination, escalation and configuration change is written to an append-only, tamper-evident trail. Rulings are effective-dated, so each transaction is assessed against the ruling that was in force when it was booked, not a later version.

Each flag carries a complete chain of evidence — from the transaction, to the check it failed, to the rule, to the AAOIFI clause, to the source document the rule was drawn from. A read-only auditor role can traverse and export the full lineage of any flag.

Distinct roles for the SCO, SSB, Auditor, Administrator and a read-only integration account, with least privilege and separation of duties — whoever configures a rule does not approve it. Authentication runs through your identity provider via SSO, SAML or OIDC. Personal data is minimised by a redaction layer before the model sees anything, with a tokenised reference so auditors can still trace back.