SaaS, Hosted or On-Premise: What 'Cloud Core Banking' Means for Your Bank
"Cloud" on a core banking proposal can mean three different setups. Each one changes who controls upgrades, how you exit, and what your regulator will want to see before go-live.
Three setups that vendors all call cloud
Three vendors on your shortlist can all say they offer cloud core banking and still be selling three different products. The word covers at least three separate core banking deployment models. The one you pick decides who sets your upgrade calendar, who holds the encryption keys, how hard it is to leave, and what goes into your outsourcing notification to the supervisor.
- Multi-tenant SaaS: one shared codebase and platform serves many banks. The vendor runs everything.
- Vendor-hosted single tenant: you get your own isolated instance, usually on a hyperscaler, and the vendor runs it as a managed service.
- Bank-operated deployment: the vendor licenses software that you deploy in your own AWS, Azure or Google Cloud account, or in your own data center. You or your integrator run it.
Before you compare features, ask every vendor which of these they're pricing. Some offer all three at very different price points. The demo you saw may have run on a model they aren't quoting.
Multi-tenant SaaS: one codebase, run on the vendor's calendar
With true SaaS core banking, every client runs the same version. The vendor ships updates continuously or on a fixed release train, and you can't defer them for long. That's deliberate. It means no multi-year upgrade projects and no customizations stranded on an old version.
You pay for that in control. You configure products, rates and workflows, but you can't change code. Extensions sit outside the core and connect through APIs or event streams. If your product team is used to writing custom ledger logic, expect friction.
Get three answers in writing before you sign:
- How much notice do you get before a breaking API change?
- Can you hold back a release during a peak period such as year-end?
- How is your data isolated from other tenants: separate databases, separate schemas, or only row-level tagging?
Cloud-native vendors such as Mambu and 10x Banking are built around a SaaS model, though vendors in this group may also offer more isolated options to larger banks. Ask what's actually on the table for your size.
Vendor-hosted single tenant: your own instance, run by the vendor
This is the common middle ground, and it's often what an established vendor means by "our cloud offering." You get a dedicated environment. The vendor, or a managed-service partner, handles infrastructure, patching, monitoring and backups.
The multi-tenant vs single-tenant core question matters most at upgrade time. A single tenant usually lets you schedule upgrades and sometimes run a version or two behind. That feels safe, but it's how technical debt creeps back. Every release you skip makes the next one bigger, so negotiate a maximum lag into the contract rather than treating flexibility as free.
Single tenant also makes some regulatory conversations easier. You can usually choose the region, ask for customer-managed encryption keys, and give auditors a clearly bounded environment. Expect to pay for the isolation: hosting in this model generally costs noticeably more than the shared-platform equivalent at the same volumes. How much more varies widely by vendor and contract, so get both models quoted side by side.
Bank-owned cloud account or on-premise: most control, most work
Here the vendor supplies software and support, and you run it. Thought Machine's Vault is often deployed this way, in the bank's own cloud tenancy. Long-established cores such as Temenos, Infosys Finacle, Oracle FLEXCUBE and TCS BaNCS can be run on premise, in a bank's private or public cloud, or as a vendor-run service, depending on edition and region.
Your cloud provider becomes your outsourcing counterparty for infrastructure, and the core vendor becomes a software licensor rather than an operator. In some jurisdictions that simplifies the supervisory filing. It also gives you the cleanest exit, because the data and environment already sit in an account you own.
The catch is staffing. You need site reliability engineers, database administrators, a security team and cloud cost discipline that many mid-sized banks don't have in-house. Banks without an established cloud platform team usually end up handing this model to a systems integrator under a managed-service contract, which brings back the outsourcing questions they hoped to avoid.
How the three models compare on what buyers care about
| Factor | Multi-tenant SaaS | Vendor-hosted single tenant | Bank's own cloud or on-prem |
|---|---|---|---|
| Upgrade cadence | Vendor-set, frequent, mandatory | Negotiated; can lag | Bank-controlled; tends to lag |
| Code-level control | None; configure and extend via APIs | Limited | High, within license terms |
| Region and key control | Vendor's available regions | Usually choosable; customer-managed keys often available | Full |
| Exit difficulty | Highest; depends on data export terms | Moderate | Lowest for infrastructure; license terms still apply |
| Internal ops staffing | Lowest | Low to moderate | Highest |
| Indicative annual run cost, mid-sized bank* | USD 0.5M to 3M subscription | USD 0.8M to 4M subscription plus hosting | USD 0.4M to 2.5M license and support, plus cloud and staff |
*Indicative 2026 market ranges for banks with a few hundred thousand to a couple of million accounts. Pricing varies by contract, region and volume, so confirm directly with vendors. Implementation is extra and frequently costs a multiple of the first year's run cost.
What EU and UK supervisors expect before you go live
Cloud outsourcing regulation for banks treats the core as a critical or important function almost everywhere. Plan for a formal filing, not an informal heads-up.
In the EU, the Digital Operational Resilience Act (DORA) governs ICT third-party arrangements, with the EBA outsourcing guidelines still relevant for wider outsourcing governance. Expect to record the arrangement in your register of information and to inform your competent authority about planned contracts for ICT services that support critical or important functions. The contract needs to cover audit and access rights, service locations, incident reporting, subcontracting chains and an exit strategy you've actually tested. Some major cloud providers are now under direct EU oversight as critical ICT third-party providers. That doesn't reduce your own due-diligence obligations.
In the UK, the PRA's supervisory statement on outsourcing and third-party risk management expects notification before a material outsourcing arrangement, stressed-exit planning, and a clear link to your operational resilience impact tolerances. The UK critical third parties regime adds oversight of designated providers, but the risk stays with the bank.
India, the Gulf and Southeast Asia: data location carries more weight
Outside Europe, data location and supervisory access often get as much scrutiny as the contract itself.
- India: the RBI's Master Direction on outsourcing of IT services requires board-approved policies, sets cloud-specific controls, and expects unrestricted audit and inspection access for the RBI. Separate payment-data storage rules require certain payment system data to be stored in India, which affects where transaction records can sit.
- Gulf: the Saudi Central Bank (SAMA) and the Central Bank of the UAE generally expect prior notification or a no-objection before material outsourcing, along with strong in-country data residency. In-country hyperscaler regions have made SaaS workable, but check which regions your vendor actually supports today rather than on its roadmap.
- Southeast Asia: MAS in Singapore expects banks to manage material outsourcing, including cloud, with audit access and exit planning. Bank Negara Malaysia's Risk Management in Technology policy calls for consultation or notification before critical systems move to the cloud. Indonesia and the Philippines have their own data-location and approval requirements.
These rules change, and their scope depends on your license type. Have local regulatory counsel confirm what applies to you before you sign.
Cost drivers and red flags in cloud core proposals
Run cost in all three models comes down to a handful of variables: account and transaction volumes, the number of non-production environments, the disaster-recovery tier, and whether you need a dedicated region. Non-production environments are the line buyers underestimate most. Four or five full test and staging instances on single tenant can add a substantial share to the hosting bill, so ask for them to be priced separately.
Red flags worth pushing back on:
- No contractual data export format. "You can have your data" isn't an exit plan. Ask for a documented schema, export frequency, and fees for an exit-assistance period.
- Vague subcontracting. You should know which hyperscaler, which regions and which support centers touch your data. Your supervisor will ask.
- Audit rights limited to vendor-supplied reports. Third-party assurance reports help, but supervisors in the EU, UK, India and the Gulf generally expect direct access rights as well.
- Volume tiers with steep step-ups. Price your three-year growth case, not today's book.
- A "SaaS" label on what is really hosted single tenant with optional upgrades. Not necessarily bad, but it isn't what you were sold, and the upgrade risk sits with you.
Choosing a model: a decision rule and a worked example
The rule we'd apply: choose multi-tenant SaaS if your products are fairly standard, your IT team is small, and your supervisor accepts the vendor's hosting regions. Choose vendor-hosted single tenant if you need region or key control, or a negotiated upgrade window, but don't want to run infrastructure. Choose your own cloud account only if you already run production workloads in the cloud with a mature platform team, or if data-location rules leave you no other option.
Hypothetical example: say a 600,000-account digital bank in Malaysia has 60 IT staff and is evaluating a vendor whose SaaS platform runs in Singapore. On paper, SaaS is the cheapest quote. But if the bank's regulatory consultation points toward local hosting, a single-tenant instance in a Malaysian region may be the only viable route, and its premium is simply the real price of the deal. Comparing the SaaS number against anything else would have been misleading from the start.
Your next step: send every shortlisted vendor the same three questions. Which deployment model is this quote for? Which regions does it cover? What do your standard exit and audit clauses say? Line the answers up against the table above before you score a single feature.
Common questions
Do bank regulators allow cloud core banking?
Yes, in most major jurisdictions, including the EU, UK, India, Saudi Arabia, the UAE, Singapore and Malaysia. It's treated as a material or critical outsourcing, though. Regulators typically expect advance notification or approval, audit and access rights, a known data location and a tested exit plan. Confirm the specifics for your license type with local regulatory counsel.
What's the practical difference between multi-tenant and single-tenant core banking?
Multi-tenant means you share one platform and codebase with other banks, so everyone upgrades on the vendor's schedule. Single tenant gives you an isolated instance, usually with more control over region, encryption keys and upgrade timing. That control typically costs more and makes it easier to fall behind on versions.
Does running the core in our own cloud account avoid outsourcing rules?
Not entirely. Your hyperscaler is still a material third party, and you'll usually still need to notify the supervisor about that arrangement. It can reduce the core vendor's role to that of a software licensor. But if a systems integrator runs the environment for you, that becomes an outsourcing arrangement too.
How long should a core banking exit plan assume?
Plan in years, not months. Smaller banks with simple products may migrate in about a year; larger or more complex banks often need multi-year windows. Whatever you assume, the contract should guarantee continued service and exit assistance for the full period, specify the data export format, and set the fees for the transition upfront.
Written by the Equitystack Pro editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.