When we last wrote about cloud adoption in telecoms, the open question was still whether operators would commit to cloud-native infrastructure or stay tied to hardware-heavy, site-based systems. Two years on, that debate is effectively over.
The destination — a cloud-native, software-first network — is now an industry consensus. The interesting questions in 2026 are sharper and, frankly, more consequential: which cloud, under whose control, and how you get there without disrupting services your customers treat as critical national infrastructure.
For the messaging core specifically — the SMSCs, MMSCs, SMSFs and firewalls and RCS platforms that quietly carry billions of business-critical messages a day — these questions are no longer abstract. They decide cost, agility, compliance and, increasingly, sovereignty. Here’s how we see the landscape today.
The destination is settled — the market has already moved
The numbers tell the story. Omdia estimated that the telco network-cloud market grew by roughly 12% in 2025, double the rate of the year before, with cloud-native tooling and automation now mature enough for operators to migrate and scale quickly rather than cautiously pilot.
What we heard across MWC 2026 reinforced it. The conversation has shifted from speculative theory to operational reality: operators are no longer asking if network functions belong in the cloud, but actively re-platforming from virtual network functions (VNFs) to cloud-native network functions (CNFs), with growing confidence in Kubernetes for production-grade deployment. Cloud-native has matured from a quick way to acquire computing power into a full platform transformation. The leading 5G core deployments are now unapologetically “all in” on cloud-native — but, importantly, with a practical, risk-aware deployment model rather than a stampede.
That nuance matters for messaging. A messaging core is a near real-time, always-on system. The move to cloud-native is settled in principle; the discipline is in the execution.
Cloud-native vs. legacy — through a messaging lens
Legacy SMSCs and MMSCs are reliable and familiar, and that counts for a lot when you’re carrying A2P traffic for banks, governments and health services. But the same rigidity that makes them dependable can also make them slow to change and increase costs.
For mobile network operators weighing a cloud-native messaging core — whether built fresh or migrated — the compelling reasons are consistent:
- Lower total cost of ownership. Autoscaling replaces stranded peak capacity, and a single software platform absorbs new generations of telco standards without a forklift upgrade each time. With AI workloads now pushing up memory and storage costs across the industry, TCO has become a board-level planning input, not an afterthought.
- One platform, many functions. A common cloud-native base lets you add microservices — firewall, anti-fraud, charging, analytics, RCS — without starting from scratch, and consolidate previously siloed “properties” onto shared infrastructure.
- A safe migration path. Cloud-native gives operators a controlled route to public, private or hybrid cloud, and the option to consolidate multiple network properties onto a single platform.
- API-readiness. An open, scalable messaging core is the foundation for exposing network capabilities as products — more on that below.
Telco Cloud vs. IT Cloud — still a real distinction
It’s worth repeating a point that often gets lost: a Telco Cloud and an IT Cloud are not the same thing. IT Cloud is optimised for enterprise applications and elastic scale. Telco Cloud is engineered for telecom realities — resilience, low latency, real-time operation, sovereignty and regulatory obligation. Messaging sharpens this further: messaging traffic carries sensitive personal data and sits under lawful-intercept and data-residency requirements that an off-the-shelf enterprise cloud posture doesn’t automatically satisfy.
This is precisely why a blanket “lift everything to public cloud” strategy rarely survives contact with a messaging core, and why hyperscalers themselves have built telco-specific offerings to court an industry that remains, understandably, careful.
The 2026 plot twist: sovereignty and the lock-in question
The biggest change since our original piece isn’t technical — it’s geopolitical and commercial. Sovereignty has moved from conference rhetoric to architecture decision.
The signals are everywhere. Deutsche Telekom is expanding its T Cloud Public with the explicit goal of reaching full core feature parity with US hyperscalers by the end of 2026, pitched as a sovereign European alternative. At MWC 2026, Deutsche Telekom, Orange, Telefónica, TIM and Vodafone announced the European Edge Continuum — a federated, operator-run edge designed to keep latency-sensitive, jurisdiction-sensitive workloads under European control. In APAC, operators are forming alliances to balance hyperscaler scale against operator-defined sovereignty, after Omdia found that around 60% of operators there view public-cloud lock-in as an existential threat.
The smart framing emerging from all this is graduated sovereignty: not “cloud or not”, but deciding layer by layer how much control each workload demands. Core network functions and sensitive subscriber data sit at the high-control end of that spectrum — and messaging lives squarely there. For a messaging core, the sovereignty conversation isn’t optional; it’s a design constraint.
Pragmatic paths to a cloud-native messaging core
The destination is shared; the routes differ. Three remain the practical options:
Hybrid, as the default. Most operators will run a hybrid model for some time — keeping core, high-control messaging functions on private or sovereign infrastructure while moving suitable workloads to public cloud for elasticity. Done well, hybrid isn’t a compromise; it’s a deliberate placement of each workload where its cost, latency and sovereignty profile fit best.
Sovereign and hyperscaler clouds, together. Operator-to-hyperscaler collaboration is now well-trodden — AT&T moved its 5G core onto Microsoft Azure (later productised as Azure Operator Nexus), and Telefónica Germany migrated its 5G core to AWS citing security and sovereignty. The 2026 evolution is pairing that hyperscaler capability with sovereign or operator-run platforms to avoid single-provider lock-in.
Edge integration. Cloud-native plus edge unlocks ultra-low-latency use cases and keeps sensitive processing close to the user — increasingly relevant as messaging blends with identity, location and real-time interaction.
Why messaging sits at the centre of the API economy
Here’s the strategic reason a cloud-native messaging core matters beyond cost savings: it’s the control point for the network-API economy that operators are now monetising in earnest.
The GSMA Open Gateway initiative, built on CAMARA-standardised APIs, has moved from ambition to execution — by early 2026 there were more than 300 commercial deployments of around 20 standardised APIs across 65-plus markets, with GSMA and TM Forum now offering joint conformance certification to scale it. These APIs — Number Verification, Silent Authentication, SIM Swap, Location — are how operators replace declining legacy SMS revenue with programmable, developer-friendly services.
For a messaging business, that’s a double-edged signal worth saying out loud. Some of these APIs explicitly aim to replace SMS one-time passwords with something more secure and less clunky. But the same shift makes the messaging core — and the fraud, identity and routing intelligence around it — more central, not less, provided it’s cloud-native, programmable and API-ready. A legacy, appliance-bound messaging stack simply can’t participate in this economy. A modern one becomes the operator’s trust and monetisation layer.
This is also why the move to a cloud-native messaging core and the arrival of capabilities like a 5G-native SMSF aren’t separate trends — they’re the same trend. The operators positioning their messaging infrastructure as software, exposed through standardised APIs and governed by intelligent fraud and routing controls, are the ones who’ll turn a cost centre into a revenue and trust platform.
Final thoughts
Two years ago, the headline was that cloud is a mega-trend telcos couldn’t ignore. That’s now simply true. The 2026 headline is different and more useful: the destination is cloud-native, but the path is a deliberate set of choices about cost, control and sovereignty — and for the messaging core, those choices carry more weight than almost anywhere else in the network.
At Openmind Networks, our focus remains on giving operators the best of both worlds: cloud-native innovation and programmability, without surrendering the resilience, compliance and sovereignty that business-critical messaging demands. The operators who treat their messaging core as software — open, scalable, sovereign-aware and API-ready — won’t just lower their costs. They’ll own the layer where trust, fraud prevention and the next wave of network-API revenue all converge.
Related reading: Sustainable Core Messaging: From Hardware-Heavy to Cloud-Ready · The Future of Core Messaging: A Roadmap for Operators
To learn more about the topics covered in this article, or to discuss how Openmind Networks can help you navigate the future of messaging, please get in touch or contact our team of messaging experts online here.
