As Revolut expands across Europe and towards 100 million customers, its success highlights a challenge facing every rapidly growing fintech: how do you scale technology at extraordinary speed without losing operational control?
Revolut has secured another major milestone in its transformation from fintech start-up to global banking institution. On 10 August, Revolut announced that Revolut Bank S.A. had been granted a full French banking licence following assessment by France's Autorité de Contrôle Prudentiel et de Résolution (ACPR) and the European Central Bank (ECB).
On the surface, this is a banking story. Look underneath it, however, and there is an equally interesting IT operations story. Because Revolut isn't simply entering another country. It is attempting to build what it describes as the world's first truly global bank, and the infrastructure, operational data and governance supporting that ambition must scale with it. That is much harder than adding another flag to a map.
Revolut was founded in 2015. Little more than a decade later, it serves more than 75 million customers worldwide across approximately 40 markets. Western Europe alone accounts for around 30 million customers, with close to 8 million joining during 2025. The trajectory is still accelerating.
Revolut's 2025 reporting says approximately one million customers are now joining every 17 days, putting the business on course for its target of 100 million customers by mid-2027. Its pre-tax profit increased 57% to approximately £1.7bn, on revenue of around £4.5bn.
Its international expansion is equally striking. Revolut launched full banking operations in Mexico in January 2026, launched its UK bank in March, applied for a US national banking charter the same month, and received a full Australian banking licence in July.
France is therefore not an isolated expansion. It is another piece of a rapidly growing global banking infrastructure. That creates an enormous challenge for IT.
Every new customer eventually becomes an infrastructure challenge. We tend to describe business growth through customers, revenue and headcount. IT teams experience growth differently. They experience it as more infrastructure, more cloud resources, more servers, more applications, databases, and endpoints. More integrations, software, certificates, identities, network connections and more environments. Then critically, more relationships between all of them.
Some infrastructure can be provisioned almost instantaneously. New cloud instances can appear in minutes. New employees need devices and applications. New development teams create environments. New services introduce dependencies. New acquisitions and geographical operations bring additional technology into the estate. The danger is obvious.
For a fintech operating at Revolut's velocity, that gap matters. Because eventually somebody has to answer some deceptively simple questions: What do we actually have? Where is it? What does it support? Who owns it? What changed? Is it compliant? International growth makes the problem harder, the French banking licence adds another dimension.
Revolut Bank S.A. will initially serve France before progressively supporting customers in Germany, Ireland, Italy, Portugal and Spain. Its Lithuanian entity will continue serving other EEA markets, creating what Revolut describes as a dual-hub European banking model. The Financial Times reported that French regulators had pushed Revolut towards a French licence partly to provide closer oversight of one of its biggest European operations, with around 7 million French customers.
That distinction is important. A global technology platform may look unified to the customer. The regulatory environment underneath it isn't.
The UK has its own banking and operational resilience requirements. EU entities operate within European regulatory frameworks including DORA and GDPR. France adds local prudential oversight through the ACPR alongside ECB supervision. Australia operates under APRA regulation. Mexico has its own banking regime. Meanwhile Revolut has applied to establish a nationally chartered bank in the United States.
The challenge therefore isn't simply:
Can our infrastructure scale?
It becomes:
Can our infrastructure scale while we can continuously demonstrate that the right technology, data, controls and services comply with the requirements applying to each jurisdiction?
Those are very different questions.
This is where operational data moves from being an IT housekeeping issue to becoming part of corporate governance. Regulators don't care that an organisation has a CMDB. They care whether the organisation can demonstrate control. Which systems support critical services? Where are they hosted? Which applications depend upon them? Who owns those applications? Where does data flow? Which assets are covered by which controls? What changed? Can the organisation prove it?
Revolut's own recent regulatory experience illustrates why that matters. City AM reports that the ECB previously restricted the launch of new products after identifying deficiencies in Revolut's European approval processes and required a third-party review of its risk, compliance and legal functions. Revolut subsequently strengthened its internal review processes. That is an important lesson for every rapidly scaling fintech.
Growth does not reduce the requirement for operational governance. It increases it.
Finding infrastructure is therefore essential. Discovery alone doesn't solve the problem. An organisation needs to understand what it has and what that technology means to the business. That requires a trusted operational data layer capable of connecting discovery, asset information, applications, services, ownership, relationships and change.
Revolut's trajectory a provides a useful lesson for every rapidly growing technology company. Revolut now has more than 75 million customers and wants 100 million by the middle of 2027. Western Europe alone has around 30 million customers. Every step adds infrastructure and every technology change creates operational data.
It would be a mistake to wait until growth has already made the environment too complicated, before trying to understand it.
The companies that scale safely won't simply be those with the most or the best technology. They will be the organisations that are in continuous control of a changing environment. When a fintech grows from start-up to global bank, operational data stops being an IT issue. It becomes part of the licence to operate.To discuss how to create real operational trust in your IT environment, talk to our team.
TekWurx has encountered precisely these challenges in complex financial environments. At an international bank, the introduction of the EU's Digital Operational Resilience Act created a requirement to maintain a complete, accurate and continuously updated view of applications, infrastructure, dependencies, suppliers and data flows.
Using TekWurx uControl, the organisation modelled 633 service applications and approximately 1,500 application instances, including discovered and non-discovered infrastructure and dependencies, with SME review and sign-off built into the process. The result was 100% DORA compliance delivered within one working week. That case demonstrates an important point. Compliance becomes dramatically easier when the organisation already understands its operational estate.
The regulatory argument is compelling. But there is another side to this story: operational efficiency. Growth can hide enormous inefficiencies. Duplicated infrastructure. Unused software. Orphaned assets. Multiple tools containing conflicting information. Manual reconciliation. People maintaining spreadsheets because they don't trust central systems. Specialists spending hours establishing whether the data in front of them is actually correct.
At a Federal Reserve Bank, TekWurx was asked to support the retirement of ServiceNow Discovery and migration to BMC Discovery while maintaining the existing ServiceNow CMDB.
The migration had to be completed within a 40-day licence renewal window. TekWurx delivered the migration within that window, created bespoke integration between BMC Discovery and the existing ServiceNow environment, maintained 99.9% CMDB data accuracy, and eliminated more than £1 million in costs and inefficiencies. Visibility and cost control weren't separate objectives. Accurate operational data enabled both.
Another TekWurx engagement demonstrates the opposite problem. At a major international stock exchange, repeated attempts to migrate discovery platforms had left ServiceNow Discovery identifying only around 7% of the infrastructure previously identified by BMC Discovery.
The organisation effectively had large sections of its infrastructure hidden from its operational view. Following the TekWurx programme, discovered asset coverage increased from 7% to 98%, AWS and Azure assets were integrated into the CMDB, applications were linked to infrastructure through service mapping, and the enriched CMDB became a single source of operational truth. Imagine that visibility gap inside a fintech simultaneously adding millions of customers and expanding into multiple regulatory jurisdictions. That's the risk.