Core Banking Modernization in the US: inside the $20 billion category rewriting the bank system of record

A community bank CIO in Iowa used to schedule her mainframe core upgrade for the third weekend of every quarter and hope nothing broke before Monday. In 2026, the same CIO deploys a configuration change to her cloud-native core at 10am on a Tuesday, watches the automated test suite pass, and moves on to the next ticket. The rails behind that shift are core banking modernization, and it is why Fortune Business Insights values the global core banking software market at $19.67 billion in 2025, projected to reach $83.78 billion by 2034 at a 17.40% CAGR, with North America holding a 42.20% regional share and the US market alone projected at $15.87 billion by 2032. A parallel Grand View Research estimate pegs the 2024 market at $12.37 billion growing to $21.61 billion by 2030 at a 10.2% CAGR.

How core banking modernization became a software category

For four decades, the “core” of a US bank was a mainframe system running code written in the 1970s and 1980s, patched continuously, and guarded with suspicion by a small priesthood of long-tenured engineers. Fiserv’s DNA and Premier, FIS’s IBS and Horizon, and Jack Henry’s SilverLake and Core Director were the dominant platforms. A tier-one bank might have thirty cores running in parallel from mergers and acquisitions. Mid-sized banks rented the same cores as a service from the same three vendors. Changing anything took eighteen months and cost millions.

What broke that model was the combination of cloud computing, API-first architecture, and the recognition that the core system of record was the binding constraint on every other digital transformation program a bank wanted to run. Mambu launched cloud-native core banking for European neobanks in 2011. Thought Machine launched Vault in 2016 and won Lloyds Banking Group as its anchor customer. 10x Banking was founded by the former Barclays CEO with the explicit mission of replacing legacy cores. FIS, Fiserv, and Jack Henry all started shipping cloud-native modules to bolt onto or replace their legacy stacks.

The incumbent response, running 2018 to 2025, was to treat core modernization as a decade-long program rather than a one-time migration. Tier-one banks built new-to-the-bank greenfield cores for specific product lines — digital-only brands, business banking, wealth — while keeping their legacy cores alive for decades of accumulated retail deposits. By 2026, core banking modernization has matured from a disruption narrative into a software-category investment thesis — the same pattern that played out in payments a decade earlier.

The core banking software market in 2025

The two research houses converge on the category structure. Global core banking software is a $20 billion market growing at 10% to 17% per year. North America dominates the regional mix, and the US alone accounts for a large fraction of global spending. SaaS delivery has become the dominant deployment model, overtaking licensed on-premises installations. Large banks command the biggest revenue share today, but community banks and credit unions are growing fastest as they migrate away from legacy service-bureau contracts.

Five core modernization workloads inside US banks

Core modernization at a US bank in 2026 has consolidated around five recurring workloads.

The first is ledger and deposit system replatforming. The general ledger, deposit subledger, and posting engine are the heart of any bank’s core. Modern platforms move these to cloud-native, real-time architectures with immutable transaction logs and configurable product definitions. The migration path typically runs greenfield-first on a new product line, then rolls existing books to the new platform over years.

The second is product configuration and origination workflow. Deposit accounts, loans, cards, and treasury products have hundreds of variants. Modern cores expose product parameters as configuration rather than code, letting product teams launch and adjust offerings without a release cycle. The overlap with the open banking rails rewriting who owns access to US financial data is structural — configurable product APIs are a prerequisite for open-banking data sharing.

The third is digital channel and API enablement. Every modernization program involves an API layer in front of the core that exposes customer data, account-opening, transactions, and transfers to web, mobile, and third-party channels. The overlap with the embedded finance category turning every app into a financial product is direct — embedded-finance platforms depend on modern core APIs to operate.

The fourth is data and analytics modernization. Legacy cores ship nightly batch files to downstream data warehouses; modern cores stream events continuously into data platforms. The overlap with the machine learning systems US financial firms have deployed for credit-scoring and model-risk management is explicit — real-time ML models need real-time core data, not T-1 extracts.

The fifth is risk, compliance, and controls migration. Every control, policy engine, AML rule, and reporting pipeline built on top of the legacy core must be rebuilt or rewired when the core changes. The program-management cost of this migration is often larger than the software-licence cost of the new core itself, and it is the single largest reason modernization programs take years.

The US core banking vendor map

The US core banking vendor map splits into three layers.

At the incumbent vendor layer, FIS (IBS, Horizon, Profile, Systematics), Fiserv (DNA, Premier, Signature, Portico), Jack Henry (SilverLake, Core Director, Banno), and Finastra (Fusion Phoenix, Essence) continue to dominate installed base at US banks and credit unions. Each has shipped cloud-native modules, open APIs, and digital-channel products to compete with newer entrants, and each competes aggressively on renewal-and-extend deals for their existing customers.

At the cloud-native challenger layer, Mambu, Thought Machine, 10x Banking, Temenos Transact on cloud, and Nymbus have won deployments at US neobanks, challenger banks, and select community banks and credit unions. Tally, Narmi, Nymbus, and similar vendors compete for the community-bank and credit-union digital-transformation budget. Each competes on speed-to-launch, configurability, and cloud-native architecture.

At the adjacent infrastructure and integration layer, vendors like Alkami (digital banking platform), Q2 Holdings (digital banking platform), Backbase (engagement banking), and MANTL (deposit account opening) provide the digital-channel overlay that banks run on top of their cores. System-integrator-driven implementation firms like Accenture, Deloitte, Capco, and PwC command a large share of the program-services revenue. This layer is where most of the long-term program spending still flows.

What the regulators are watching in 2026

Core modernization is supervised by the OCC, Federal Reserve, FDIC, and NCUA (for credit unions), with additional oversight from state banking departments. The programs touch every material process in the bank, so every supervisor touches the program.

The first supervisory concern is technology-change risk. Regulators expect formal change-management governance, board-level oversight, and documented contingency plans for every core migration. The 2023-2024 wave of failed digital banking launches at mid-sized banks raised the bar for what counts as adequate testing, rollback, and go-live planning.

The second concern is third-party risk and vendor concentration. When three vendors power the cores of most US community banks and credit unions, a vendor failure is a systemic concern. Interagency third-party-risk-management guidance and updated vendor-concentration expectations apply to every core-vendor relationship, and banks are expected to maintain exit-readiness plans they can actually execute.

The third concern is data lineage, books-and-records accuracy, and recordkeeping. Every core migration is also a data migration, and the accuracy of account histories, transaction records, and statements is a first-order supervisory issue. Banks that have botched data migrations in past modernization programs have faced consent orders, restitution requirements, and prolonged supervisory attention.

What it means for founders and operators

For founders, the core banking modernization category remains one of the larger structural opportunity sets in financial-services software. The $20B global market is expanding faster than most adjacent categories, and the structural opportunities — cloud-native cores for community banks and credit unions, product-configuration engines, real-time event-streaming data layers, integration and migration tooling, and digital-channel overlays — remain far from mature. Defensible startups pair deep core-banking domain expertise with modern data engineering and the regulatory and vendor-concentration documentation that OCC, FDIC, and NCUA examiners expect.

For operators at incumbent banks, credit unions, and neobanks, the cost question has shifted. Core modernization investment has grown double-digits per year through 2020-2025, and CFOs and boards are starting to push back. The institutions landing cleanly in 2026 are the ones that measured program ROI by time-to-launch for new products, cost-to-serve per account, digital-channel adoption, and fraud-and-operational-loss reduction — not by the size of the initial migration budget or the number of vendor logos signed. The institutions that ran disconnected modernization programs without business-line accountability are the ones justifying the line item to the board quarter after quarter.

The bottom line

Core banking modernization is the software category that is rewriting the system of record at the heart of every US bank over the current decade. At $20 billion globally in 2025 and growing at 10% to 17% annually, the category is both structurally expanding and tightly supervised. North America dominates the regional mix with over 42% of the market, the US is on track for $15 billion-plus by the early 2030s, SaaS delivery has become the dominant deployment model, and large banks command roughly 30% of end-user spending. The firms getting the most value from core modernization are the ones that treat it as strategic operating infrastructure — with product management, business-outcome accountability, and regulatory governance — not as an IT line item. In banking, as in the rest of financial-services technology, the operational-excellence plays are the ones that compound.