Home / Finnosis Pulse
Product

Finnosis Pulse

Bank-wide monitoring, alerting and self-healing for any core banking system and the systems around it: cards, payments, SWIFT, digital channels, lending, AML, treasury and reporting.

Capabilities

Everything an operations team needs, nothing it has to build

Core banking, end to end

Day-end stages and batches, transactions by module and channel, interfaces, database, app servers and exceptions, in your CBS's terms.

Learn more →

Every system around the core

Twelve bank systems with their own KPIs, tiers, dependencies and an availability heatmap. Add more through configuration.

Learn more →

Alerting that reaches the right team

Owning team by system or area, escalation if nobody acknowledges, notes, email, Teams, Slack, webhook or ITSM.

Self-healing

Learned playbooks with four-eyes approval, three modes, run limits, cooldown, day-end block, verification and automatic suspension.

Learn more →

Executive dashboards

CEO, CFO, CRO, COO, CIO/CTO, CISO and Compliance views with a plain-language "needs your attention" list.

Learn more →

Roles & permissions

Own user ids and passwords or SSO, 15 built-in roles, unlimited custom roles, scope by system, every check on the server.

Learn more →

Audit-ready reports

Incident register, remediation log, playbook history, SLA (MTTA / MTTR), day-end runs, user activity, config changes, maker-checker; CSV export.

Learn more →

Any database, any app server

Oracle, SQL Server, PostgreSQL and SAP HANA health from each engine's own views; WebLogic, JBoss, WebSphere, SAP ABAP or any JVM.

Learn more →

Open by default

Prometheus /metrics for Grafana and existing NOC tools. Health endpoint. Docker deployment on your premises.

Learn more →
Inside Pulse

Real screens from the product

Architecture

Read-only by design

Pulse reads health and business signals through read-only accounts and standard endpoints. It never writes to a bank system. Automatic fixes run only through the bank's own scripts and runbooks, after approval.

YOUR BANK Collectors read-only SQL · REST · JMX Prometheus · JSON · TCP Database health CBS business queries App servers Bank systems Interfaces Pulse engine Rules · 107 + your ownAlert lifecycle & escalationHealth score & dependenciesSelf-healing playbooksRoles & permissionsAudit trail/metrics for Grafana PEOPLE & CHANNELS approved fixes run through the bank's own scripts and runbooks
Deployment

Inside your network, in days not months

01 · DISCOVERY

Map your estate

Agree the systems, the read-only accounts, and the business queries for your core banking release.

02 · INSTALL

One container

Docker on a server in your data centre or private cloud. No agents on bank servers.

03 · CONNECT

Check every source

A built-in check runs every query and endpoint once and reports what works, before go-live.

04 · OPERATE

Tune and teach

Adjust thresholds, set up roles and notification channels, and let the team start teaching Pulse its fixes.

Questions banks ask

FAQ

Does Pulse change anything in our core banking system?

No. Pulse uses read-only database accounts and read-only endpoints. Automatic fixes are executed only through the bank's own approved scripts or runbook tools, for playbooks a manager has approved.

Which core banking systems does it support?

Profiles ship for Oracle FLEXCUBE, Temenos Transact, Infosys Finacle, TCS BaNCS, SAP for Banking and in-house systems. Database health works on day one. Business queries (day-end, postings, authorisations) are built in for FLEXCUBE and agreed during discovery for the others, against your release's data dictionary.

How does Pulse learn a fix?

When a person resolves an alert, they record the root cause and the fix and can choose to teach Pulse. A different person with approval rights must approve it. From then on, the same alert on the same system triggers that fix within the limits set.

What if an automatic fix does not work?

Pulse verifies recovery against the alert rule. If the metric has not recovered, the run is marked failed and the alert is escalated to the on-call team. Two failures in a row suspend the playbook.

Can we use our own sign-on?

Yes. Pulse has its own users, passwords, lockout and roles, and single sign-on (AD, LDAP, SAML or OIDC) can replace the password step during implementation. Roles stay in Pulse.

Where does it run?

In your data centre or private cloud, as a container. Monitoring data stays inside the bank.

Does Pulse work with Grafana or our existing NOC tools?

Yes. Pulse publishes its metrics in Prometheus format at /metrics, and alerts can go to email, Microsoft Teams, Slack or a webhook into your ITSM tool.

Put Pulse on your estate

Start with a demo on a simulated bank that runs your core banking system.

Book a demo