How the pieces fit

Each system has one job

The customer channel does not own the ledger. The identity check does not replace the core. Sign-in and permissions sit in front of changes to money or customer records. You can modernize one journey without swapping everything at once.

Who owns what

Who owns what, in six groups: Customer channels, Sign-in and checks, Accounts and money, Risk and records, Operations, and Relationships.
A visual summary of the table. The table is the text version.
Area Platforms What they do
Customer channels Nova · Summit · Mercury The apps and branch screens people use. They start a journey. They do not keep the official customer file or the ledger.
Sign-in, customer checks, and permissions Aegis · Atlas · Kenning · Gazette · Argus Who may sign in, what they are allowed to do, the know-your-customer decision, and checks on data quality. These systems do not hold account balances.
Accounts and money Titan · Pulse · Ceres · Quill · Vulcan · Wayfarer · Attest The official customer file and ledger, plus payments, loans, checks, cards, and remittances. Where money is recorded, Titan is that record.
Risk and records Sentinel · Scribe · Ledgerhall Risk cases, the document store, and the packages prepared for regulators.
Operations Relay · Helios · Orion The service desk, people operations, and AI-assisted workflows. These are not the bank’s books.
Relationships Beacon · Prism · Aurum Relationship management, customer insight, and wealth processes. They refer to Titan’s customer numbers. They do not replace the official customer file.
Card ecosystem Janus · Vantage · Talos · Plutus · Terminus · Sigil · Laurel The card switch and what sits around it: fraud rules, ATMs, POS terminals, online card checks, loyalty, and the switch console. Money still posts to Titan.
Reconciliation and reporting Libra · Almanac Bank-wide reconciliation and management reporting. Ledgerhall stays the only regulatory filer.

The full family

Every platform, grouped by the job it does. Opening a retail account runs from Nova to Kenning to Titan, with Aegis and Atlas checking identity and permission. Payments, lending, risk, records, operations, and relationships attach beside that path.

All 33 platforms.

Hover or tab to a platform to see its connections. Select it to open its page.

How the Trudi banking platforms integrateBackbone of the main flows between platform groups. Hover or focus a platform to see all of its connections.TRUDI · PLATFORM INTEGRATION MAPHow the banking platforms integrateMain flows between groups. Hover or tab to a platform to see all of its connections.Main flow between groupsDirect API call (on hover)Event or batch feed (on hover)01CHANNELSWhere customers and staff start02CUSTOMER CHECKWho is this customer?03ACCOUNTS AND MONEYTitan is the system of record; Pulse runs the rails04CARD ECOSYSTEMSwitch, fraud, ATM, POS, 3-DS, loyalty05RISK AND REGULATORYDecisions, cases and filings06RECONCILIATION AND MISBank-wide feeds07OPERATIONSRuns the business, not the books08RELATIONSHIPSReference Titan customer numbers09CONTROL PLANE · UNDER EVERY PLATFORMEvery platform: identity → Aegis, entitlements → Atlas, documents → Scribe, risk → Sentinel.onboardingchannels: payments, accountscustomer refproducts post to Titanrailscard authorization, switch, fraudrisk checksextractsrecon and MIS feedsreconevery platform binds the control planeOrion gateway readsMercury → Titan: customer file, postingscustomer file, postingsMercury → Scribe: documentsdocumentsMercury → Sentinel: risk checkrisk checkMercury → Attest: specimensspecimensCeres → Titan: postingspostingsCeres → Pulse: loan payoutsloan payoutsCeres → Aegis: step-upstep-upCeres → Scribe: document connectordocument connectorCeres → Sentinel: risk connectorrisk connectorCeres → Ledgerhall: regulatory connectorregulatory connectorQuill → Titan: postingspostingsQuill → Sentinel: risk checkrisk checkQuill → Attest: signature checksignature checkSummit → Attest: signatures, mandatessignatures, mandatesSummit → Titan: customer filecustomer fileSummit → Pulse: payment intentspayment intentsTitan → Attest: opening specimensopening specimensPulse → Attest: mandate checkmandate checkAttest → Scribe: documentsdocumentsAttest → Atlas: entitlementsentitlementsVulcan → Titan: postingspostingsVulcan → Talos: fraud checkfraud checkVulcan → Sigil: 3-D Secure3-D SecureNova → Titan: customer filecustomer fileNova → Pulse: payment intentspayment intentsNova → Wayfarer: remit intentsremit intentsNova → Kenning: onboarding CDDonboarding CDDPulse → Titan: postingspostingsPulse → Foreign CBS: postingspostingsPulse → Sentinel: risk checkrisk checkWayfarer → Pulse: remittance moneyremittance moneyWayfarer → Sentinel: risk checkrisk checkHelios → Pulse: payrollpayrollHelios → Titan: payrollpayrollHelios → Scribe: documentsdocumentsSentinel → Titan: account holdsaccount holdsRelay → Aegis: access ticketsaccess ticketsAegis → Atlas: entitlementsentitlementsAtlas → Aegis: operator identityoperator identityScribe → Aegis: identityidentityScribe → Atlas: entitlementsentitlementsKenning → Aegis: JWKSJWKSKenning → Titan: customer refcustomer refPlutus → Janus: ATM messagesATM messagesPOS terminals → Janus: acquiringacquiringJanus → Vulcan: on-us authorizationon-us authorizationJanus → Talos: fraud checkfraud checkJanus → Card networks: BancNet, Visa, MCBancNet, Visa, MCJanus → Titan: merchant settlementmerchant settlementVantage → Janus: ops consoleops consoleVantage → Plutus: ops consoleops consoleTerminus → POS terminals: terminal settingsterminal settingsPulse → InstaPay: TInstapayTInstapayPulse → PESONet: TPesonetTPesonetPulse → PDDTS: TPDDTSTPDDTSPulse → TBills: TBillsTBillsCeres → Vulcan: card collectionscard collectionsVulcan → Sentinel: card alertscard alertsAttest → Sentinel: forgery alertsforgery alertsTalos → Sentinel: fraud alertsfraud alertsVulcan → Laurel: card eventscard eventsTitan → Laurel: account eventsaccount eventsGazette → Sentinel: name-list snapshotsname-list snapshotsTitan → Ledgerhall: read extractsread extractsPulse → Libra: reconciliationreconciliationJanus → Libra: reconciliation feedreconciliation feedVulcan → Libra: reconciliation feedreconciliation feedTitan → Libra: reconciliation feedreconciliation feedPlutus → Libra: reconciliation feedreconciliation feedTitan → Almanac: read extractsread extractsLibra → Almanac: read extractsread extractsBeacon → Titan: customer refcustomer refBeacon → Prism: customer refcustomer refPrism → Titan: customer refcustomer refOrion → Relay: gateway readgateway readOrion → Scribe: gateway readgateway readOrion → Ceres: gateway readgateway readOrion → Titan: gateway readgateway readOrion → Sentinel: gateway readgateway readOrion → Pulse: gateway readgateway readOrion → Ledgerhall: gateway readgateway readOrion → Argus: refused readrefused readOrion → Aegis: token exchangetoken exchangeOrion → Atlas: entitlement checkentitlement checkSummitCorporate bankingNovaRetail digitalMercuryBranch and tellerKenningeKYC and CDDGazetteName screeninglistsPulsePayments hubCeresLoansQuillChequesVulcanCardsWayfarerRemittancesAttestSignaturesTitanCustomer file and ledgerJanusCard switchTalosCard fraudrulesSigil3-D Secure ACSLaurelLoyaltyPlutusATM handlingTerminusPOS terminalsVantageSwitch opsconsoleSentinelRisk decisions and casesLedgerhallRegulatory filingsLibraReconciliationAlmanacMIS reportingRelayService deskHeliosPeople and HROrionAI workflows · banking gateway (read-only)BeaconRelationshipsPrismCustomerinsightAurumWealthand trustAegisIdentity, tokens, step-upAtlasEntitlements, flagsScribeDocuments, recordsArgusData quality probesInstaPayPESONetPDDTSTBillsForeign CBSPOS terminalsCard networksDashed pills are outside parties, not Trudi platforms. Platform names link to each product page.
How the 33 platforms connect, in nine groups. The bold lines are the main flows: products post to Titan, Pulse runs the payment rails, and Sentinel takes the risk checks. Every platform sits on the control plane: Aegis and Atlas check identity and permission before money or a customer record changes.
Open the diagram full size
Text alternative: groups and handoffs
The same nine groups as the map, with their main handoffs.
GroupPlatformsHandoff
01 ChannelsNova, Summit, MercuryNova starts retail account opening and hands the work to Kenning. Nova and Summit send payments to Pulse. Mercury posts branch transactions to Titan.
02 Customer checkKenning, GazetteKenning decides on the customer check and passes an accepted customer reference to Titan. Gazette only sends public-record name-list snapshots to Sentinel; Sentinel makes the screening decision.
03 Accounts and moneyTitan, Pulse, Ceres, Quill, Vulcan, Wayfarer, AttestTitan is the customer file and the ledger. Pulse, Ceres, Quill and Vulcan post to Titan. Pulse runs the payment rails, and Wayfarer pays remittances out through Pulse. Attest verifies signatures for Quill, Mercury and Summit.
04 Card ecosystemJanus, Talos, Sigil, Laurel, Plutus, Terminus, VantageJanus is the card switch for card authorization, ATMs and POS terminals. Talos runs the card fraud rules in the approval path and sends alerts to Sentinel. Sigil checks the cardholder on online card payments. Laurel runs loyalty. Vantage is the switch operations console.
05 Risk and regulatorySentinel, LedgerhallPlatforms ask Sentinel for a risk decision where a risk check applies. Sentinel can ask Titan to place a hold. Ledgerhall reads extracts from Titan for regulatory reports.
06 Reconciliation and reportingLibra, AlmanacLibra reconciles switch, card, ATM, payment and ledger records. Almanac builds management reports. Ledgerhall stays the only regulatory filer.
07 OperationsRelay, Helios, OrionService desk, people operations including payroll, and AI-assisted workflows. Orion reads banking data only through a read-only gateway. These are not the bank’s books.
08 RelationshipsBeacon, Prism, AurumBeacon, Prism and Aurum refer to Titan customer numbers. They do not replace the official customer file.
09 Control planeAegis, Atlas, Scribe, ArgusUnder every platform: Aegis for sign-in, identity and step-up, Atlas for permission and safety switches, Scribe for documents, Argus for data quality. If a required check cannot be made, the change does not go through.

You can start with a few

Each platform keeps its own job. Adopt the ones you need. The family is not one system you have to take whole.

Request a demo Explore platforms Security in brief