- Market
- Saudi Arabia
- Written for
- CIO, COO
- Decision
- Change a live, regulated core system without downtime or an error
The two constraints
The two things a financial system may never do at the same time
We do not have an office in Saudi Arabia
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
A bank or an insurer runs on a core with two absolute constraints that pull against each other. It may not stop, because customers transact around the clock and a downtime window is measured in reputational and regulatory cost. And it may not be wrong, because a balance that is off by a fraction, once, is a breach of trust and often of regulation. Most software gets to trade one of these against the other — move fast and fix forward, or move slowly and carefully. A core financial system is denied both trades, and that denial, not the size of the feature list, is what makes changing it genuinely hard.
That constraint shapes every decision. A change goes live behind controls that can reverse it before a customer notices; a new capability runs alongside the old, reconciled continuously, before it carries real money; every action leaves an audit trail, because a regulator, an auditor or a dispute will ask what happened and “we think” is not an answer. The interesting engineering in financial services is not the customer app, which is the visible tenth; it is doing all of this to a system that is simultaneously live, regulated and unforgiving of a single wrong number.
Before it ships
What a change to a live financial system has to satisfy before it ships
These are the conditions a change clears in a regulated core, and they hold whether it is a new feature or a small fix, because the cost of an exception is measured in customer money and regulatory standing.
Reversible without customer impact
A change can be rolled back before anyone transacting notices, rather than committed in a way that has to be right the first time.
What it protects: The institution never bets live service on a single irreversible switch.
Reconciled continuously
A new path runs beside the old and is checked against it before it carries money, so a discrepancy shows up in reconciliation, not on a statement.
What it protects: A discrepancy caught in a report rather than in a customer’s balance.
Auditable to the action
Every change and access is logged and attributable, because a regulator, an auditor or a dispute will ask exactly what happened and when.
What it protects: An answer that is evidence rather than recollection.
Correct under regulation
The design meets the rules that apply before it is built, not after a review discovers it does not.
What it protects: A capability that does not have to be unwound because it was non-compliant.
The routes
Three ways to modernise a core, and where each actually fits
There is no single right answer; there is the right answer for a specific institution, its book and its risk appetite. These are the three shapes a core modernisation takes and the conditions each suits.
| Option | Operational risk during the change | Speed to first value | Fit for a heavily regulated core | What it demands of the team | Best for |
|---|---|---|---|---|---|
| Replace the core outright | Highest — one large cutover that has to be right for everyone at once | Slowest — value arrives only at the end | Rarely, and mainly for a new or genuinely small institution | A long freeze and a heavy data migration | A greenfield build, or a small book where the old core is genuinely beyond extending. |
| Wrap and extend | Low — the core keeps running untouched | Fast — new capability sits beside the old | Strong — the regulated core is not disturbed | Integration discipline and a clear contract | An institution that needs new channels and products without touching a core that still works. |
| Strangle in slices | Managed — one capability moved at a time with a rollback | Steady — value arrives per slice | Strong — risk is bounded to one slice per step | Sustained programme discipline over time | A core that must eventually be replaced but cannot be stopped to do it. |
Our role
What we build and what stays with your risk and compliance teams
- 01
Change without stopping
We build the reversible, reconciled release path so an improvement to a live core never costs an outage or introduces an error a customer feels.
- 02
Auditable by construction
The audit trail and the controls a regulator expects are part of the design from the start, not added under pressure when a review or a dispute demands them.
- 03
The institution owns the risk
We are not a bank; licensing, regulatory sign-off and the acceptance of risk stay with you, and we build so those decisions are yours to make on evidence rather than on hope.
The licences, the regulatory approvals and the risk appetite stay with the institution; we build the systems and the controls that let you change a live core without a customer feeling it or a regulator questioning it.
Common questions
What buyers ask
How do you change a core banking system without downtime for customers?+
By making the change reversible and running the new path beside the old before it carries any real transaction. Rather than a maintenance window in which the system is switched and hoped to be right, the new capability is deployed behind controls that can roll it back before a customer notices, and it is reconciled continuously against the existing system until it is proven correct. Customers keep transacting throughout, because the old path is still carrying them until the new one has earned the traffic. Downtime is treated as a failure of method, not an unavoidable cost of change.
How do you keep an audit trail a regulator will accept?+
By building it into the system from the start rather than reconstructing it when a regulator asks. Every change and every access is logged and attributable to a named actor, retained for as long as the rules require, and structured so that the answer to “what happened to this account, and when” is a query rather than an investigation. An audit trail bolted on after the fact tends to have gaps precisely where the difficult questions land, which is why it is a design requirement here, not a reporting feature added later. What we do not do is decide what satisfies the regulator — that judgement stays with your compliance team, and we build so they have the evidence to make it.
Is it safer to replace our core banking system or to modernise it in slices?+
For a live institution with a real book, moving in slices is almost always safer, and a full replacement is the exception rather than the default. Replacing the core outright means one large cutover that has to be right for every account at once, discovering what it missed in production, whereas moving one capability at a time with a rollback bounds the risk of any single step and delivers value along the way. A full replacement earns its place mainly for a new institution or a small book where the old core genuinely cannot be extended. Which route fits yours depends on the state of the core and your risk appetite, and that is a decision we would reach with you on evidence rather than arrive with.
In this cluster
Begin with your systems
A technical review of one planned core change that establishes how it is made reversible, how the new path is reconciled against the old before it carries money, and what audit evidence it leaves, before any code is committed.
Start the conversation
