How telcos can build a sovereign IaaS platform

Telecommunications providers already play a central role in the cloud economy.

They own the networks businesses use to reach cloud services. They operate data centers, regional points of presence, edge locations, support teams and enterprise client relationships. In many markets, they are also trusted local infrastructure providers for businesses, governments and critical services.

For years, much of that infrastructure was used to connect clients to someone else’s cloud.

That is starting to change.

Enterprises, public-sector organizations and regulated industries are asking more specific questions about where workloads run, who operates the infrastructure, which laws apply to their data and how predictable their cloud costs are.

In Europe, this shift is also shaped by greater focus on cloud portability and reduced lock-in. The EU Data Act includes measures intended to help clients switch between data processing services, including cloud and edge services.

For telcos, this creates a clear opportunity.

Instead of only providing the network path to cloud services, telcos can become local cloud providers themselves. By building sovereign infrastructure-as-a-service (IaaS), telcos can deliver virtual machines, storage, networking, backup, disaster recovery, cyber protection and managed infrastructure services under a local operating model.

For telcos, sovereign IaaS is more than a technology project. It is a way to move beyond connectivity, create higher-value recurring services and serve clients that need local infrastructure they can trust.

Cloud infrastructure is no longer only about global scale.

Hyperscalers remain essential for many workloads, especially those that need global reach, cloud-native services or high elasticity. But many organizations are becoming more selective about where each workload should run.

This is also where regional cloud providers can differentiate from hyperscalers through local control, support and governance.

A bank may need tighter control over sensitive workloads. A health care provider may need patient-related data to remain in a specific country or region. A municipality may want local support and infrastructure operated by a provider subject to local regulation. A regional enterprise may want cloud flexibility without unpredictable consumption charges or distant support processes.

These requirements go beyond basic data residency. Understanding the difference between data residency and data sovereignty is essential for telcos building sovereign infrastructure services.

Data residency answers one question: Where is the data stored?

Data sovereignty goes further. It asks: Who operates the infrastructure? Who can access the data? Which laws apply? Who owns the platform? How is the service governed, protected, audited and supported?

This is where telcos can have a strong position. They already operate in regulated markets. They understand availability, resilience, incident response, client support and critical infrastructure expectations. They also have a local presence in the markets they serve.

That combination can make telcos credible providers for sovereign cloud infrastructure.

Sovereign IaaS is cloud infrastructure designed around local control, data governance, jurisdictional alignment, resilience and security.

In practical terms, it allows clients to consume cloud infrastructure services such as compute, storage, networking, backup and disaster recovery while having clearer answers to questions such as:

• Where are workloads hosted?
• Where are backups, logs and metadata stored?
• Who operates the infrastructure?
• Who provides support?
• Which jurisdiction applies?
• How is access controlled?
• How is the service protected and audited?

For telcos, sovereign IaaS can be delivered in two main ways.

The first is a multitenant sovereign cloud, where multiple clients consume services from shared infrastructure with strong tenant isolation, access controls, reporting and service-level separation.

The second is a private or dedicated cloud, where infrastructure is reserved for one client or one group of clients with stricter isolation, governance or performance requirements.

Both models can work. The right choice depends on the client segment, regulatory environment, workload sensitivity and commercial model.

Telcos have several advantages when building sovereign IaaS services.

The first is infrastructure.

Many telcos already operate national or regional assets, including data centers, edge sites, fiber networks, backbone connectivity and service operations. These assets can become the foundation for cloud services hosted closer to clients, users, devices and data sources.

The second advantage is trust.

Businesses and public-sector organizations already rely on telcos for connectivity, managed networks, voice, mobile, security and infrastructure-related services. Extending that relationship into cloud infrastructure is a natural next step.

The third advantage is regulatory familiarity.

Telcos are used to operating within demanding national frameworks. In Europe, cybersecurity expectations continue to rise, with ENISA guidance covering digital infrastructure and ICT service management sectors, including cloud computing providers, data center providers, managed service providers and managed security service providers.

The fourth advantage is network proximity.

Telcos can combine IaaS with private connectivity, low-latency access, regional cloud nodes and future edge services. For workloads that need to run close to users, applications, devices or data sources, this can create a differentiated offer.

A sovereign cloud is not just a cloud with a local address. It needs credible local operations, clear governance, strong protection, reliable support and a network foundation. Telcos can bring these elements together in a way many other providers cannot.

Building sovereign IaaS is not the same as placing virtual machines in a local data center.

To become credible cloud providers, telcos need platforms designed for secure, scalable, multitenant service delivery.

Key requirements include:

The platform must allow the telco to serve multiple clients from shared infrastructure while keeping each client environment isolated and governed.

This requires tenant separation, virtual data centers, resource quotas, role-based access controls, centralized management and client-level reporting.

Clients need clarity on where production workloads, backups, metadata, logs, snapshots and disaster recovery copies are stored and processed.

They also need to understand which entity operates the infrastructure, which teams can access it and which governance model applies.

Sovereign infrastructure must be resilient and secure by design.

Backup, disaster recovery options, anti-malware and anti-ransomware protection, workload monitoring, access control and operational visibility should be part of the service model, not added later.

Sovereign IaaS must make sense commercially.

Clients want pricing they can understand. Telcos need a model that supports service packaging, margin planning, client billing, infrastructure investment and long-term growth.

Sovereign cloud strategies often emphasize independence and reduced lock-in. Platforms built on open technologies can help telcos maintain flexibility and give clients more confidence in the long-term direction of the service.

Most telcos building a sovereign IaaS strategy will eventually want to operate infrastructure from their own data centers or regional facilities.

This gives the telco more control over data location, infrastructure operations, service branding, network integration, compliance positioning and long-term infrastructure economics.

For national cloud initiatives, public-sector programs, critical infrastructure clients and regulated industries, this local deployment model is usually the strongest fit.

Some telcos may extend the model across multiple regional or edge locations. This can support low-latency applications, edge analytics, regional workload hosting, local backup and recovery, private connectivity, 5G-enabled services and IoT workloads.

Other providers may prefer to start more gradually.

A hosted cloud model can help telcos validate demand before committing to a full local infrastructure buildout. They can begin selling IaaS, test client appetite, refine pricing and packaging, then move to local deployment when the business case is stronger.

This staged approach can also support clients evaluating cloud repatriation by giving telcos a practical way to test demand before expanding into local infrastructure at scale.

The important point is that sovereign IaaS does not need to begin as a massive transformation project. It can start with focused services, clear client segments and a deployment model that matches the telco’s maturity and market opportunity.

Sovereign IaaS should not be sold as raw compute.

Clients rarely start by asking for virtual machines. They ask for outcomes: local control, secure hosting, predictable costs, migration support, compliance readiness, resilience and trusted operations.

That means telcos should package sovereign IaaS around client needs.

A sovereign virtual machine service can provide cloud compute hosted in a specific country or region.

A protected cloud hosting package can combine virtual infrastructure with backup, cyber protection, monitoring and disaster recovery options.

A compliance-ready infrastructure package can support clients in finance, health care, the public sector, critical infrastructure and other regulated industries.

An edge cloud service can bring infrastructure closer to users, factories, hospitals, retail sites, devices or regional operations.

A private cloud service can serve enterprise clients that need dedicated or more tightly controlled environments.

A cloud migration service can support VMware migration, hyperscaler transitions, legacy hosting moves and on-premises infrastructure modernization.

This approach helps telcos move away from commodity infrastructure and toward outcome-based cloud services.

Acronis Cyber Frame is designed to help service providers deliver infrastructure services with integrated cyber protection, management and automation. Acronis positions Cyber Frame as a secure hyperconverged infrastructure (HCI) and IaaS solution for service providers that supports virtual machines, storage and networking with integrated backup, disaster recovery, security and RMM capabilities.

For telcos pursuing sovereign IaaS, the most strategic model is often Acronis Cyber Frame Local.

With Cyber Frame Local, the telco can run the platform on its own or colocated infrastructure, in its own data centers or regional facilities. This supports stronger positioning around data location, local governance, performance, compliance alignment and long-term infrastructure economics.

Cyber Frame also supports the commercial needs of service providers. Its service-provider capabilities support a white-label cloud platform model, helping telcos package infrastructure services under their own brand while managing clients through a service-provider-ready platform.

For telcos that want to validate demand before deploying locally, Cyber Frame Cloud can provide a lower-barrier starting point. Cyber Frame Cloud is Acronis-hosted infrastructure delivered through the Acronis console. Acronis operates the infrastructure, while the partner provisions and manages client workloads.

For telcos ready to build a sovereign cloud under their own control, Cyber Frame Local is the stronger strategic fit.

Telcos should plan Cyber Frame Local as production infrastructure, not as a small single-node deployment. Production environments should be sized and designed according to operational requirements, client demand, performance expectations and resilience goals.

The value is practical: Telcos can launch IaaS services faster, package protected infrastructure services, reduce operational complexity and build a cloud business aligned with local control and sovereignty requirements.

A successful sovereign IaaS strategy usually starts with focus.

Start with the clients most likely to value local cloud infrastructure. These may include government agencies, municipalities, health care organizations, banks, financial institutions, critical infrastructure operators, regional enterprises and SaaS providers with local compliance requirements.

Sovereignty should not be vague. Define what the service actually provides.

That may include in-country data storage, local operations, local support, client-controlled encryption, audit documentation, regulatory alignment or jurisdictional commitments.

Clients need clarity, not slogans.

Evaluate whether the platform supports multitenancy, scalability, integrated cyber protection, local deployment, service provider management, reporting, billing integration and operational automation.

The platform should support the business model, not only the technical environment.

Do not try to replicate every hyperscaler service from day one.

Start with services that match telco strengths, such as sovereign VM hosting, protected IaaS, backup-enabled infrastructure, managed private cloud, cloud migration services or regulated workload hosting.

Once the foundation is in place, the telco can expand into edge cloud, private connectivity, disaster recovery, industry-specific cloud packages, managed security and public-sector programs.

This staged approach reduces risk and helps the telco build momentum before expanding the portfolio.

The opportunity is strong, but sovereign IaaS is not automatic.

Telcos need to plan for infrastructure investment, platform skills, client onboarding, billing integration, support processes, compliance documentation and migration complexity.

They also need to avoid building the service around tools designed only for internal enterprise virtualization.

Sovereign IaaS requires more than virtualization. It requires tenant management, billing readiness, service automation, integrated cyber protection, operational visibility and repeatable packaging.

The right platform and partner ecosystem can reduce these barriers and help telcos bring services to market faster.

Telcos are well positioned to become sovereign cloud infrastructure providers.

They already have local infrastructure, network expertise, client trust, operational experience and regulatory familiarity. By adding cloud infrastructure services, they can move beyond connectivity and deliver higher-value offerings to enterprises, public-sector clients and regulated industries.

A successful sovereign IaaS platform needs multitenancy, local data control, integrated cyber protection, predictable economics and flexible deployment options.

Acronis Cyber Frame supports this strategy by helping telcos deliver protected, multitenant infrastructure services through Cyber Frame Cloud and Cyber Frame Local. For providers that want to build sovereign IaaS under their own operational control, Cyber Frame Local offers a practical path to turn existing infrastructure into a differentiated cloud business.

Sovereign IaaS is not just another cloud service.

For telcos, it is a path to becoming the trusted local cloud provider clients are already looking for.

Sovereign IaaS is cloud infrastructure designed to meet local requirements for data residency, jurisdictional control, operational governance, compliance, security and resilience.

Telcos already operate local infrastructure, networks, data centers and support organizations. They also have trusted client relationships and experience operating regulated services.

Telcos can offer virtual machines, storage, networking, backup, disaster recovery, protected cloud hosting, managed private cloud, edge cloud, migration services and regulated workload hosting.

Local deployment gives the provider greater control over where data is stored, how infrastructure is operated, which jurisdiction applies and how the service is governed and supported.

Acronis Cyber Frame helps service providers deliver IaaS with integrated cyber protection, management and automation. It supports virtual machines, storage and networking through Cyber Frame Cloud, which is Acronis-hosted, and Cyber Frame Local, which is service-provider-hosted. For telcos building sovereign IaaS under their own control, Cyber Frame Local is usually the stronger strategic fit.

Not necessarily. Building every component from scratch can increase cost, complexity and time to market. Many telcos are better served by using a service-provider-ready platform that supports multitenancy, local deployment, integrated cyber protection, automation and operational management.