Business service monitoring, top-down
See what your customers see.
Most monitoring watches machines. MonX watches what your customers actually do: card payments, logins and transfers, every minute. When they stop, you know before the first customer calls.
- 15 years in banking operations
- On-prem or SaaS
- Built for NBS 102/2024 and DORA
- Support in Serbian
Product overview · 1:29
Friday, 18:00. Every light is green. No one can pay.
Ninety seconds on what happens next, and what MonX does about it.
The problem
All systems green. Payments down.
Component monitoring measures the parts of a system, not whether the customer completes a transaction. It's known as the watermelon effect: green outside, red inside.
Component monitoring
- Servers (CPU, memory)OK
- DatabasesOK
- NetworkOK
- Application servicesOK
Friday 18:00 · every check passing
Customer experience
Successful card payments per minute
2,847
Every component reports “OK”…
Who notices first: you, or your customer?
47%
of organisations say customers are often or very often the first to detect service degradation or outages.
Splunk and Oxford Economics, 2026
- 01
Your customers
“Payment declined.” They try again, then give up.
- 02
Your call center
The queue fills: 48 callers waiting.
- 03
Then you
Operations hears about it from the call center.
- 04
And soon, the regulator
A significant incident, with deadlines to report it.
The cost of downtime
Every minute costs more each year.
Unexpected outages and long recoveries cause losses across the business: revenue, customers, engineering time and trust.
Average cost of one minute of downtime (USD)
$5,600
2014 · Gartner
$9,000
2024 · Splunk
$15,000
2026 · Splunk
$95M
lost revenue per company, every year (Global 2000)
Splunk and Oxford Economics, 2026
$5M+
per hour of downtime for large banks and financial institutions
ITIC, Hourly Cost of Downtime, 2024
Customers don't wait for your fix
32%
of customers would stop doing business with a brand they loved after one bad experience.
PwC, Future of Customer Experience survey, 2018
29%
of Global 2000 executives report losing customers because of downtime
Splunk and Oxford Economics, 2024
90%
of tech leaders report more demand on customer support after downtime
Splunk and Oxford Economics, 2026
How MonX helps: you see the drop in successful transactions the moment it starts, not when complaints arrive.
“…I'm talking around $15 to $30 million for each downtime that we have.”
Technology executive, JPMorgan Chase (Splunk, 2024)
The top-down approach
From the customer to the cause.
MonX starts with what the customer experiences, then adds the layers below so you find the cause fast. The tools you already run keep watching the components.
1 · Customer experience
Successful payments, logins, completed orders
2 · Business services
Cards, instant payments, mobile banking
3 · Applications and integrations
APIs, message queues, batch jobs
4 · Infrastructure
Servers, databases, network
MonX starts here
It measures what the customer experiences, every minute.
Then add the layers below to find the cause fast.
Your existing tools
The component monitoring you already run stays. MonX doesn't replace it; it adds the layer above.
How it works
01
Connect any source
If your systems record it, MonX can watch it. Agents are the SQL queries, PowerShell scripts and REST or SOAP calls your team already knows. A lightweight Agent Service runs them on a schedule, inside your network.
02
Turn results into indicators
Each value lands on an indicator with the levels you set, grouped into business services such as Card payments. MonX learns what normal looks like for every hour and every kind of day.
03
Know first, then find the cause
One message when an indicator changes level and one when it's back, not hundreds. To Teams, Slack, SMS, email, Jira or ServiceNow. Then MonX shows what moved with it.
Inside MonX
From the first unusual minute to the report you send.
Live indicators, a learned sense of normal, the likely cause, the alert, and the paperwork for the regulator. In one product your team already knows how to feed.
Live business indicators
- Every minute
- Any source
Card payments, logins, transfers and anything else your systems record, as live indicators and charts. Group them by business service, put them on a wall screen, and scroll back through the history.
- Agents in SQL, PowerShell, REST and SOAP
- Levels per indicator, from good to very bad
- Dashboards, charts and a ticker for maintenance notices
Use cases
Indicators your customers feel.
Built in banking, and just as useful anywhere a service has to work around the clock: insurance, ticketing, fintech, delivery, and the internal systems large companies run on.
Banks
- Card authorizations per minute
- Instant payments in progress
- Mobile banking logins
Telecoms
- SMS delivered per minute
- Service activations
- Successful top-ups
Payments
- Approved transactions per minute
- Processor response time
- Failed charges
E-commerce
- Orders completed per minute
- Successful checkout payments
- Deliveries assigned
Alongside your tools, not instead of them
Your tools show how your servers are doing. MonX tells you whether your customers can pay right now.
Keep your existing monitoring for infrastructure. MonX adds the layer above it: is the service actually working for the customer?
Compliance
What MonX measures, regulators require.
NBS Decision 102/2024 applies from 1 January 2026, and DORA across the EU. Both ask you to detect problems early, know how long a service was down, and report it. MonX keeps that record for you.
| Requirement (NBS Decision 102/2024; DORA) | What MonX provides |
|---|---|
| NBS item 26: an adequate monitoring system | Continuous indicators of service delivery to customers, not just components |
| NBS item 40: early-warning indicators | Thresholds and alerts per indicator, and comparison with the same period |
| NBS items 41–42: incident classification and how long the service was down | Indicator history shows when the service stopped and when it recovered |
| NBS item 53: performance and capacity monitoring | Volume trends and system capacity limits |
| NBS chapter VII and Annex 1: reporting significant incidents | An incident register, Annex 1 classification for a person to confirm, deadlines, and drafted reports |
| NBS item 25: a yearly review of who has access | Last sign-in for every user and an access review export |
| DORA Art. 10: prompt detection of anomalies, alert thresholds | Top-down indicators with defined thresholds, on several levels |
Built to pass your security review.
Your security team gets a full pack to start from: an overview, the threat model, the NBS mapping, questionnaire answers and a software bill of materials for every release.
Runs inside your bank
Windows Server, IIS and SQL Server. Reached only from your network, and installs without internet access.
Your data stays with you
Everything MonX records lives in your own SQL Server database. MonX sends nothing to us.
Sign-in your way
Windows (Active Directory), single sign-on with your provider, or passwords with two-step sign-in.
Secrets nobody can read back
Agents' passwords are encrypted so only the MonX service can use them. Not even an administrator sees them.
Every change on record
Who changed what and when, in the app and in the Windows Event Log for your SIEM.
Least privilege
Viewer, Configurator and Administrator roles, checked by the API on every request.
Where MonX fits
MonX next to the tools you know.
Monitoring and observability platforms start from components. MonX starts from the business service. Most teams keep both.
Swipe the table sideways to compare →
| Aspect | MonX | Infrastructure monitoringe.g. Zabbix, PRTG, SolarWinds | Enterprise observabilitye.g. Datadog, Dynatrace, Splunk |
|---|---|---|---|
| Built around | Business services and customer outcomes | Hosts, devices and sensors | Applications, traces and cloud infrastructure |
| Business view | The starting point (top-down) | Built on top of component checks | Service views and SLOs, sometimes a separate module |
| Custom checks | SQL, PowerShell, REST, SOAP built in | Scripts, plugins and sensors | Custom metrics and extensions |
| Deployment | On-prem or SaaS | Mostly self-hosted | Mostly SaaS |
| Pricing | Annual subscription | Per device or sensor, or a free license with paid support | Per host, per product or by consumption |
| Setup | A lightweight agent and your own SQL | Agents or sensors on every device | Agents on every host, plus platform setup |
| Support | Direct, local, in Serbian | Vendor or partners | Global vendor and partners |
Why MonX
Proven in banking, built for you.
15 years in practice
The top-down approach was developed and used in one of the largest banking IT systems in Serbia. MonX turns it into a product.
Skills you already have
SQL, PowerShell, SQL Server, IIS. No new query languages or stacks to maintain.
Your data stays with you
Fully on-prem, or SaaS with a lightweight agent on your network. Minimal load on your systems.
Local and hands-on
A Belgrade-based team with support in Serbian. We help you design your monitoring and write the agents.
“Built by people who ran major incidents for fifteen years. The tool we wished we'd had.”
- DG
Dejan Gošić
Co-founder · architecture and methodology
More than 24 years in banking IT: developer, software architect, major incident and problem manager, and head of ICT application architecture.
- LG
Lazar Gošić
Co-founder · product development
Builds the MonX web app and services. Information systems and technologies, University of Belgrade.
Next step
Pilot: three critical services, eight weeks.
Start on the services that matter most and judge MonX by what it catches. You won't do it alone: our team designs and sets up the monitoring with yours.
Week 1
Workshop and service selection
Two 1.5-hour workshops for your team, and the choice of your three most critical services.
Weeks 1–2
First indicators live
We write the agents together with your team and move them to production.
Weeks 3–8
Thresholds and alerts
We tune thresholds and measure how fast problems are detected.
End of pilot
Joint review
What MonX caught before your customers did, and how we continue.
After the pilot: an annual subscription (OPEX) with new versions included. On-prem installation available.
FAQ
What clients usually ask.
Something we didn't answer? .
Good, keep them. MonX doesn't replace them. It adds the layer above: indicators of service delivery to customers.
Let's look at your three most critical services.
Bring the service you worry about most. We'll show you what MonX would have caught on it, live, at your site or online.
Dejan Gošić
Co-founder · architecture and methodology
dejan.gosic@mon-x.appLazar Gošić
Co-founder · product development
lazar.gosic@mon-x.appLive demo
At your site or online
Or watch the overview first