Telecom Network Automation

Name: Telecom Network Automation
Brand: Google

Telecom Network Automation is a telecom-focused automation control plane that automates Day 0/1/2 lifecycle operations for cloud infrastructure and network functions using intent-driven declarative configuration and GitOps-style workflows, and integrates with Google Distributed Cloud Edge and GKE for multi-vendor, distributed edge deployments.

Est 1998|Valuation $4081.3B|Raised $26.1M

LinkedIn 41.9M|Website|Web traffic 3.3M|FTEs 198,933|HQ Mountain View, California, US

01Competitive Landscape

| Aspect | Google Cloud Telecom Network Automation (TNA) | Nokia Autonomous Networks Fabric | IBM Cloud Pak for Network Automation (CPNA) | |--------|----------------------------------------------|----------------------------------|--------------------------------------------| | Starting Price | Contact sales; published metered usage pricing available from the vendor | Not publicly transparent; enterprise deal pricing typical | Uses IBM Resource Units (RU) licensing metric; pricing usually quote-based | | Recommended For | CSPs pursuing Kubernetes/GitOps-based CNF lifecycle automation integrated with Google Cloud edge/Kubernetes offerings; organizations aligned with Nephio and open-source intent automation | CSPs seeking an NEP-led autonomous network suite with telco-specific domain apps and workflow packaging | CSPs standardized on Red Hat/OpenShift or IBM Cloud Paks, or those seeking IBM-supported automation integrated into the broader IBM portfolio | | Key Strength | Managed implementation of Nephio; intent-driven, declarative automation; alignment with Kubernetes control-loop and GitOps paradigms | Telco-focused packaging and domain framing; NEP domain expertise and workflow apps | Integration with IBM’s automation/AI portfolio; formal licensing model and enterprise packaging | | Key Weakness | Limited independent review footprint; pricing transparency is limited; may require partner ecosystem for assurance/NOC workflows | Pricing opacity; may require commitments to the Nokia stack; adoption may be shaped by NEP-specific choices | Complexity and licensing overhead; may require IBM platform skills and integration effort | - Narrative analysis - Nokia vs Google Cloud TNA - Nokia positions its Autonomous Network Fabric to support network automation efforts and emphasizes telco domain knowledge and data-driven features; Nokia publicly notes integrations with cloud AI services (including Google Cloud services) in some solution narratives, indicating potential coopetition where cloud providers deliver underlying cloud/AI capabilities and NEPs provide telco domain packaging. - For some CSPs, Nokia may be preferred when operators want a single integrator accountable for domain outcomes across RAN/core/transport operations. - Google TNA may be preferred by operators intentionally building a cloud-native platform layer with open intent automation and sourcing CNFs from multiple partners. - IBM CPNA vs Google Cloud TNA - IBM CPNA is documented as a network automation tool to automate lifecycle of cloud network services, with formal RU-based licensing documentation. - IBM may be preferred by operators standardized on Red Hat/OpenShift and IBM Cloud Paks, or those who want a vendor with a long presence in telco OSS. - Cisco Crosswork vs Google Cloud TNA - Cisco Crosswork is positioned to support network automation and provisioning workflows; vendor marketing contains quantitative claims that should be validated via customer references and methodology. - Crosswork may be advantageous when the network environment is Cisco-heavy or when Cisco’s domain modules align closely with an operator’s processes. - Market share and adoption trends - Public, quantified market share for telecom-specific network automation products is not disclosed in accessible sources. - Analyst artifacts for the broader category (e.g., industry peer review platforms) indicate the category is established, but they do not directly validate TNA’s relative market position.

01Competitive Landscape

Aspect	Google Cloud Telecom Network Automation (TNA)	Nokia Autonomous Networks Fabric	IBM Cloud Pak for Network Automation (CPNA)
Starting Price	Contact sales; published metered usage pricing available from the vendor	Not publicly transparent; enterprise deal pricing typical	Uses IBM Resource Units (RU) licensing metric; pricing usually quote-based
Recommended For	CSPs pursuing Kubernetes/GitOps-based CNF lifecycle automation integrated with Google Cloud edge/Kubernetes offerings; organizations aligned with Nephio and open-source intent automation	CSPs seeking an NEP-led autonomous network suite with telco-specific domain apps and workflow packaging	CSPs standardized on Red Hat/OpenShift or IBM Cloud Paks, or those seeking IBM-supported automation integrated into the broader IBM portfolio
Key Strength	Managed implementation of Nephio; intent-driven, declarative automation; alignment with Kubernetes control-loop and GitOps paradigms	Telco-focused packaging and domain framing; NEP domain expertise and workflow apps	Integration with IBM’s automation/AI portfolio; formal licensing model and enterprise packaging
Key Weakness	Limited independent review footprint; pricing transparency is limited; may require partner ecosystem for assurance/NOC workflows	Pricing opacity; may require commitments to the Nokia stack; adoption may be shaped by NEP-specific choices	Complexity and licensing overhead; may require IBM platform skills and integration effort

Narrative analysis
- Nokia vs Google Cloud TNA
  - Nokia positions its Autonomous Network Fabric to support network automation efforts and emphasizes telco domain knowledge and data-driven features; Nokia publicly notes integrations with cloud AI services (including Google Cloud services) in some solution narratives, indicating potential coopetition where cloud providers deliver underlying cloud/AI capabilities and NEPs provide telco domain packaging.
  - For some CSPs, Nokia may be preferred when operators want a single integrator accountable for domain outcomes across RAN/core/transport operations.
  - Google TNA may be preferred by operators intentionally building a cloud-native platform layer with open intent automation and sourcing CNFs from multiple partners.
- IBM CPNA vs Google Cloud TNA
  - IBM CPNA is documented as a network automation tool to automate lifecycle of cloud network services, with formal RU-based licensing documentation.
  - IBM may be preferred by operators standardized on Red Hat/OpenShift and IBM Cloud Paks, or those who want a vendor with a long presence in telco OSS.
- Cisco Crosswork vs Google Cloud TNA
  - Cisco Crosswork is positioned to support network automation and provisioning workflows; vendor marketing contains quantitative claims that should be validated via customer references and methodology.
  - Crosswork may be advantageous when the network environment is Cisco-heavy or when Cisco’s domain modules align closely with an operator’s processes.
Market share and adoption trends
- Public, quantified market share for telecom-specific network automation products is not disclosed in accessible sources.
- Analyst artifacts for the broader category (e.g., industry peer review platforms) indicate the category is established, but they do not directly validate TNA’s relative market position.

Aspect

Google Cloud Telecom Network Automation (TNA)

Nokia Autonomous Networks Fabric

IBM Cloud Pak for Network Automation (CPNA)

Starting Price

Contact sales; published metered usage pricing available from the vendor

Not publicly transparent; enterprise deal pricing typical

Uses IBM Resource Units (RU) licensing metric; pricing usually quote-based

Recommended For

CSPs pursuing Kubernetes/GitOps-based CNF lifecycle automation integrated with Google Cloud edge/Kubernetes offerings; organizations aligned with Nephio and open-source intent automation

CSPs seeking an NEP-led autonomous network suite with telco-specific domain apps and workflow packaging

CSPs standardized on Red Hat/OpenShift or IBM Cloud Paks, or those seeking IBM-supported automation integrated into the broader IBM portfolio

Key Strength

Managed implementation of Nephio; intent-driven, declarative automation; alignment with Kubernetes control-loop and GitOps paradigms

Telco-focused packaging and domain framing; NEP domain expertise and workflow apps

Integration with IBM’s automation/AI portfolio; formal licensing model and enterprise packaging

Key Weakness

Limited independent review footprint; pricing transparency is limited; may require partner ecosystem for assurance/NOC workflows

Pricing opacity; may require commitments to the Nokia stack; adoption may be shaped by NEP-specific choices

Complexity and licensing overhead; may require IBM platform skills and integration effort

Telecom Network Automation

01Competitive Landscape

02Market Map

01Competitive Landscape

02Market Map