Is Network-as-Code Redefining the Telco–Cloud Partnership Through Programmable 5G and Network APIs?

Telecom operators are converting network capabilities into programmable software interfaces that developers can invoke on demand. Through standardised APIs, 5G Standalone cores, and cloud-native automation, connectivity now integrates directly into enterprise application architecture. This shift, widely described as Network-as-Code, restructures the telco–cloud partnership around shared control planes, coordinated infrastructure, and interoperable platforms. 

The defining issue is execution at scale. Operators and hyperscale cloud providers are aligning API frameworks, edge deployments, and core network modernisation programs to embed connectivity inside cloud ecosystems. Network programmability now influences enterprise cloud strategy, security architecture, and digital platform design. 

Standardised Network APIs Establish a Shared Control Plane 

Standardisation provides the foundation for Network-as-Code. The GSMA launched the Open Gateway initiative at Mobile World Congress 2023 to define common network APIs across operators. The initiative builds on the CAMARA open-source project hosted by the Linux Foundation. CAMARA specifies APIs for quality-on-demand, device location, number verification, SIM-swap detection, and edge-site selection. 

GSMA disclosures confirm that more than 60 mobile operator groups support Open Gateway, representing a significant share of global mobile connections. This scale creates a globally aligned exposure layer that application developers can integrate without having to negotiate bespoke operator contracts in each market. 

Large operators have operationalised these APIs. Vodafone Group has committed to deploying Open Gateway APIs across its European footprint and aligning its developer interfaces with CAMARA standards. Telefónica has embedded Open Gateway capabilities into its enterprise offerings and demonstrated quality-on-demand and fraud-prevention APIs in live environments. 

Standardised API exposure establishes a shared control plane between telecom operators and hyperscale cloud providers. Developers consume connectivity functions using established cloud-native patterns while operators maintain policy governance within 5G cores. 

Hyperscale Integration Embeds the Network into Cloud Infrastructure 

Programmability gains commercial traction when operators integrate core and edge infrastructure with hyperscale environments.

Amazon Web Services launched AWS Wavelength in collaboration with operators, including Verizon. AWS documentation confirms that Wavelength Zones place AWS compute and storage inside carrier data centres. Verizon states that it has deployed 5G Ultra Wideband with AWS Wavelength in multiple US metropolitan markets, enabling developers to run latency-sensitive applications within the 5G network footprint. 

In 2021, AT&T announced it would run its 5G core network on Microsoft Azure. Microsoft supports this transition through Azure Operator Nexus, which provides a carrier-grade hybrid cloud platform for telecom workloads. This integration aligns 5G core operations with hyperscale DevOps, observability, and automation frameworks. 

Google Cloud has partnered with operators to support 5G core and edge workloads on Google Distributed Cloud. These collaborations reflect a broader transition from network function virtualisation to fully cloud-native, containerised cores operating in distributed cloud environments. 

By embedding compute within carrier infrastructure and integrating cores into public cloud platforms, operators and hyperscalers create a unified infrastructure layer. Enterprises orchestrate compute, storage, and connectivity through integrated toolchains rather than siloed systems. 

Cloud-Native 5G Cores Institutionalise Automation 

Network-as-Code depends on 5G core architectures that support modularity, API exposure, and continuous deployment. 

The 3rd Generation Partnership Project defines the 5G core service-based architecture, enabling microservice-based network functions and standardised northbound interfaces. This specification supports programmatically exposing network capabilities while preserving interoperability. 

Infrastructure vendors have aligned with this architecture. Ericsson reports commercial deployments of its dual-mode 5G core supporting cloud-native environments. Nokia provides containerised 5G core solutions that operate on Kubernetes-based infrastructure across public and private clouds. 

Software-centric operators demonstrate this model at scale. Rakuten Mobile built its network on a fully virtualised, cloud-native stack and commercialised its Rakuten Communications Platform to other operators. Rakuten reports that its 5G core runs on containerised infrastructure aligned with cloud-native principles. 

Mid-sized software firms contribute to this transformation. Mavenir delivers cloud-native 5G core and Open RAN software and reports commercial deployments across multiple regions. These deployments enable operators to implement CI/CD pipelines and lifecycle automation across network functions. 

Automation frameworks treat network configurations as version-controlled software artefacts. Operators synchronise release cycles with hyperscale cloud environments and compress provisioning timelines for enterprise services. 

Commercial Network Slicing and Quality-on-Demand 

Network slicing has progressed from technical capability to commercial service. 

Deutsche Telekom has launched 5G Standalone and supports enterprise network slicing in Germany, including campus network deployments with dedicated resources. Orange has implemented 5G Standalone in several European markets and participates in GSMA Open Gateway to align slice management with standardised APIs. 

Quality-on-demand APIs enable enterprises to request defined bandwidth and latency parameters for specific time intervals. These services support broadcast production, large-scale events, manufacturing automation, and financial trading environments where predictable performance underpins operational continuity. 

Operators expose these controls through governed interfaces integrated with cloud orchestration systems. Enterprises can incorporate connectivity parameters into application logic and workload scheduling strategies. 

Identity and Security as Programmable Capabilities 

Programmable networks extend into identity verification and fraud mitigation. 

CAMARA specifications define APIs for number verification and SIM swap detection, enabling applications to validate user identity using telecom network signals.

Operators, including Vodafone and Telefónica, have demonstrated number verification APIs to reduce SMS-based fraud and strengthen authentication flows. 

Hyperscale cloud providers document integration pathways between telecom authentication signals and cloud-based identity services. These integrations enhance zero-trust architectures by incorporating carrier-validated signals into access management workflows. 

Security API exposure reinforces the telco role as a trusted infrastructure participant within digital ecosystems and complements hyperscale identity platforms. 

Strategic Outlook for the Telco–Cloud Partnership 

Network-as-Code formalises a coordinated operating model between telecom operators and hyperscale cloud providers. Standardised APIs through GSMA Open Gateway and CAMARA, cloud-native 5G cores aligned with 3GPP specifications, distributed edge platforms, and automated lifecycle management create a programmable connectivity layer embedded within enterprise cloud architectures. 

Commercial deployments by Verizon, AT&T, Vodafone, Deutsche Telekom, Orange, Rakuten Mobile, and others confirm production-scale adoption across major markets. Hyperscalers, including AWS, Microsoft, and Google Cloud, integrate telecom infrastructure into their platform strategies, aligning compute and connectivity within unified environments. 

Enterprises now treat connectivity as an addressable resource within cloud design frameworks. Network parameters, identity signals, and edge placement decisions integrate directly into application logic and infrastructure-as-code pipelines. 

Network-as-Code, therefore, defines the next stage of digital infrastructure integration. It positions programmable networks as a structural component of enterprise cloud architecture and establishes the telco–cloud partnership as a platform ecosystem grounded in shared standards, automation, and coordinated governance.