Any core banking system. Every system around it.

Profiles for six core banking systems, health for four database engines and any Java app server, and twelve bank systems in one view.

Core banking

Pulse speaks your core banking system's language

Product names are trademarks of their owners. Pulse monitors these systems through read-only connections; Finnosis does not claim partnership or certification with these vendors.

Bank systems

Twelve systems, one view

System	What Pulse watches	Example automatic fix
Core banking	Day-end progress and aborts, posting failures, pending authorisations, suspense, branches, interfaces, database, app servers	Re-run aborted batch from checkpoint
Cards	Approval rate, authorisation time, HSM latency, technical declines	Fail over to the standby HSM
ATM / POS	Terminals online, success rate, cash-outs	Raise cash replenishment requests
Payments hub	UPI / IMPS / NEFT / RTGS success, response time, RTGS queue	Switch to the secondary link
SWIFT	Outgoing queue, NAKs, time since last ACK, sanctions holds	Restart FIN link and resend NAKed
Digital banking	Login success, 5xx errors, response time, sessions	Rolling restart of the mobile API
API gateway	Error rate, p95 latency, throttling	Alert to owning team
OTP / SMS	Delivery rate, delivery time, queue	Switch to aggregator B
LOS / LMS	Core sync lag, disbursement queue, bureau errors	Restart sync job and replay
AML & sanctions	Screening time, queue, alerts pending	Alert to owning team
Treasury	Rate feed age, position lag	Alert to owning team
Data warehouse	Load age, failed regulatory jobs	Alert to owning team

Under the hood

How Pulse connects

DATABASES

Oracle, SQL Server, PostgreSQL, SAP HANA

CPU, sessions, blocking, waits, storage and replica lag from each engine's own monitoring views. Pure-JavaScript drivers: no vendor client or extra licence pack.

APP SERVERS

WebLogic, JBoss, WebSphere, SAP ABAP, any JVM

WebLogic through its REST API; others through a Prometheus endpoint (for example the JMX exporter) or JSON.

BANK SYSTEMS

SQL, REST, Prometheus, JSON, TCP

Each system is configured with its own sources, KPIs, thresholds, tier and dependencies.

INTERFACES

Queues, error rates, heartbeats

API and ESB layers, message queues, SWIFT and payment links, with last-message age.

OUT

Prometheus, email, Teams, Slack, webhook

/metrics for Grafana; alerts to people and to your ITSM tool.

CHECK

Source check before go-live

One command runs every query and endpoint once and prints what works and the exact error for what does not.

Architecture

Read-only by design

SCOPEWhat works on day one. Database health works on day one for all four engines. Day-end, posting, branch and authorisation queries are built in for FLEXCUBE; for other core banking systems they are agreed during discovery against your release's data dictionary, because table layouts vary by release and bank. IBM Db2 is not supported directly in this release; its figures can come in through Prometheus or JSON.

Map Pulse to your estate

Send us your list of systems; we will show you what Pulse watches on day one.

Book a demo