For most banks in Central Asia, the debate about cloud core banking has not really been about cloud.
It has been about geography.
The technical case settled some time ago. Cloud-native platforms deploy faster, scale on demand, and let an institution launch a product in weeks rather than quarters. Nobody in a modern bank’s technology function seriously argues otherwise. The blocker was never whether the architecture worked. It was whether the bank could give a clear answer to a single question: where does the data actually sit.
That question has stalled more modernisation programmes in the region than any technical objection ever has.
Fimple and Bulutistan Uzbekistan Partnership have formed a strategic answer to it.
Two companies, two halves of the same capability
This is a mutual partnership in a specific and useful sense. Each side brings something the other cannot manufacture on its own. And the combination is worth considerably more than either half.
Fimple brings the platform. A cloud-native, composable, API-first core banking system built from the ground up in 2022. Operating from London and Istanbul, and structured around a Financial Function as a Service model. That model matters here. Rather than shipping a monolith that a bank has to accept whole. Fimple delivers banking capability as modular services across payments, lending, deposits, treasury and the rest, assembled to fit the institution rather than the other way around. The platform exposes several thousand API services, which is what makes assembly practical rather than theoretical.
Critically for this market, Fimple is cloud-agnostic. The platform does not require any particular hyperscaler underneath it. That is a design decision that looks unremarkable in London and turns out to be decisive in Tashkent. As it means the deployment question can follow the regulation rather than the vendor’s preferred region map.
Bulutistan brings the ground. The company has operated as Türkiye’s leading domestic cloud provider since 2015. Running eight data centres across three Turkish provinces alongside infrastructure in Baku, Frankfurt, London, Thessaloniki and Uzbekistan. Serving customers connecting from more than sixty countries. Bulutistan completed its company registration in Uzbekistan and opened a physical office there in October 2025, moving from remote service into genuine local presence.
The credentials behind that footprint are not incidental to a banking conversation. Bulutistan was the first Türkiye-based cloud service provider to achieve CSA STAR certification and the first Turkish company to integrate into the Equinix Global Connection network. It provides cloud services to two thirds of Türkiye’s largest 500 companies and sixteen of the twenty largest holding groups. With a partner network exceeding 350 organisations. For a regulated financial institution evaluating whether a cloud provider can carry a core banking workload, that operating history is the substance of the answer.
Put the two together and the constraint dissolves. A bank in Uzbekistan can run a modern, composable core banking platform, with the infrastructure and the data inside the jurisdiction its regulator supervises. No on-premise compromise, no multi-year hardware procurement. And no trade-off between modern architecture and local compliance.
Why Uzbekistan, and why now
Uzbekistan’s banking sector is in the middle of a real structural shift, not a cosmetic one.
The emphasis across the sector has moved away from headline growth and toward the harder measures: efficiency of capital allocation, institutional resilience, and transparency of financial operations. That shift is showing up as a set of concrete workstreams. Development of the interbank money market. Strengthening of liquidity management systems. Broad expansion of digital banking services. And preparation for Islamic financial instruments, with an Islamic banking bill on the parliamentary agenda.
Each of these lands on individual institutions as the same operational requirement, expressed differently.
A bank building out participation banking needs to stand up a compliant product set without rebuilding its core. And responding to interbank market reform needs to reconfigure treasury and liquidity products as the rules settle rather than after they settle. Which is competing for a young, mobile-first customer base needs to ship digital propositions on a cadence its legacy system was never designed to support.
On monolithic infrastructure. Each of these is a project with a business case, a vendor negotiation and a delivery timeline measured in quarters. On a composable platform, most of them are configuration.
This is precisely the pattern Fimple was built for, and it is why the timing of this partnership matters. Uzbekistan’s institutions are being asked to move quickly by their own regulator’s reform agenda. At exactly the moment when the infrastructure to let them move quickly has become locally available.
The participation banking dimension
The Islamic finance track deserves separate attention, because it is where the partnership’s value is most concentrated.
Standing up participation banking is not a feature toggle. It requires a core system that can handle fundamentally different product mechanics, profit and loss sharing rather than interest accrual, with the accounting, reporting and Sharia governance that follows from that. Retrofitting this onto a conventional legacy core is expensive, slow, and frequently produces a compromise that satisfies nobody.
Fimple supports participation banking natively rather than as an adaptation layer. Which is a direct consequence of the platform’s origins and its founding team’s background in the participation banking sector. For Uzbek institutions preparing to open Islamic windows or establish dedicated participation banks as the legislative framework takes shape. That removes one of the largest technical unknowns from the plan.
Combined with in-country infrastructure, it means an institution can move from legislative clarity to live product without the infrastructure question reopening.
What each side gains
Mutual partnerships work when the exchange is genuine, so it is worth being explicit about it.
For Fimple, Bulutistan provides compliant, certified, in-country infrastructure in a priority growth market. Along with deep regional relationships in Türkiye and Central Asia built over a decade. It converts Uzbekistan from a market that requires a bespoke deployment answer into one where the answer already exists.
For Bulutistan, Fimple provides an anchor workload in financial services. One of the most demanding and most strategically valuable verticals a cloud provider can serve. Core banking is the workload that proves a platform. It also supports Bulutistan’s stated strategy of establishing presence wherever data is governed, extending the company’s financial services position beyond Türkiye into Central Asia.
For institutions in Uzbekistan, the practical outcome is the only one that matters: a modern core banking platform, running locally, available now.
The pattern beyond Uzbekistan
There is a version of this story that is only about one market. There is a more interesting version that concerns every market where data sovereignty expectations and modernisation ambitions pull institutions in opposite directions.
That tension is not easing. It is intensifying, across Central Asia, across the Gulf, across North Africa. Regulators are becoming more specific about where financial data may reside, at the same time as competitive pressure is making legacy infrastructure less tenable every quarter.
The institutions that resolve this first will not be the ones that waited for the rules to relax. They will be the ones that found architecture flexible enough to work inside the rules as written.
Cloud-agnostic is not a line item on a feature comparison. In markets like this one, it is the entire proposition.