Design partner · Since 2018

Banking platforms you can adopt one journey at a time.

Trudi I.T. Solutions builds software for Philippine banks and financial institutions: customer channels, the checks that approve a new customer, and the core that holds accounts.

Start with one journey. You do not have to replace the whole bank at once.

Platforms are modular. You can adopt them separately. Trudi I.T. Solutions does not claim to be a bank or to hold a BSP license.

A phone, a laptop, and a records screen with abstract banking layouts. No customer data is shown.
  1. NovaRetail account opening
  2. KenningCustomer identity check
  3. TitanCustomer file and ledger

Opening a retail account, in three steps

Each step has one owner. When the work is accepted, your team can see who decided what.

  1. Step 1 · The channel

    Nova

    Customer app and screens

    The app and screens a retail customer uses to start opening an account. Nova starts the journey. It does not keep the official customer file or the ledger.

  2. Step 2 · The customer check

    Kenning

    Customer identity check

    The know-your-customer (KYC) review. Kenning records the decision. When the customer is accepted, it passes a customer reference to Titan so the account can be created.

  3. Step 3 · The core

    Titan

    Customer file and ledger

    The official customer record, the accounts, and the ledger those accounts post to. Titan is the system of record for that job: it holds the official copy.

How we work with institutions

We work as a design partner. We build with your team, one journey at a time.

Choice

Take what you need

Customer channels, identity checks, accounts and payments, risk and records, and day-to-day operations. Buy the pieces your roadmap needs. There is no single package you must take whole.

Pace

One journey at a time

Each journey has a clear owner: the channel, the customer check, or the core. Start with one and add the next when your team is ready.

Control

A stop before sensitive changes

Aegis checks identity. Atlas checks permission, including an emergency stop. If that check cannot be made, the change to money or the customer record does not go through.

Family

Thirty-three platforms, one job each

Every platform is in the catalog with its own page. Adopt the ones your roadmap needs.

Each platform 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 sensitive changes. Read the architecture in plain language

All 33 platforms in nine groups, with the platform marks.

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.

Sensitive changes need a check first

The public summary for executives and risk leads. The detailed product security pack is shared under a non-disclosure agreement (NDA) when we work together. Full security page

A sensitive change is checked by Aegis (who is asking), then Atlas (is it allowed), then, where a risk check applies, Sentinel (is it safe). Sentinel can ask Aegis for a step-up. If any required check fails or cannot be made, the change stops. If all pass, it proceeds.
  • No check, no change. If a platform moves money or changes a customer record and the required check cannot be made, the change does not go through.
  • A trail a reviewer can follow. On the retail account path, Kenning’s decision is passed to Titan as a customer reference. A reviewer can see who approved the customer and which record was created.
  • Your duties stay yours. We help client banks meet their duties. Trudi is not a bank and does not claim a BSP or AMLC license.

Technology and delivery partners

Companies we build and deliver with. They are not banking clients or customer endorsements.

Questions people ask first

Short answers. The full FAQ covers cookies, privacy, and platform pages.

What does Trudi I.T. Solutions do?

We build banking software for Philippine institutions. You can adopt one customer journey at a time. We also do custom development when a roadmap needs it.

Is Trudi a bank?

No. Trudi I.T. Solutions is a software company. We help client banks meet their own regulatory and operational duties. We do not take deposits and we do not claim a BSP license.

Do we have to buy every platform?

No. Each platform does one job. You take the ones your roadmap needs. There is no single package you must buy whole. Prices are discussed with us, not listed here.

Who keeps the official customer record?

Titan. Channels such as Nova, Summit, and Mercury start the work. Kenning records the customer-identity decision. Titan holds the customer file, the accounts, and the ledger. Other platforms refer to that record. They do not replace it.

How do we request a demo or a pilot?

Use Request a demo or Request a pilot, then email or call us and say which journey matters. Talk to sales when you want a commercial conversation. We aim to reply within two business days. Writing to us starts a conversation. It is not an order and not a checkout.

Are the logos on this site your clients?

No. They are technology and delivery partners, not customer endorsements.

See all questions

Start with one journey

Ask for a demo, a pilot discussion, or a sales conversation, and tell us which journey matters. Prices are shared in that conversation, not listed on this site.