MantaRay SMO

Name: MantaRay SMO
Brand: Nokia

MantaRay SMO is a RAN-domain Service Management and Orchestration platform that automates operations across multi-vendor, multi-technology RAN environments using rApps and closed-loop automation aligned to TM Forum and O-RAN frameworks.

Est 1865|Valuation $57.8B|Raised $9.1B

LinkedIn 419K|Website|FTEs 78,005|HQ Espoo, Uusimaa, FI

MarketsEnterprise Networking

Platform CoversInfrastructure Monitoring

Published Oct 13, 2026

01Common complaints

- If transparent list pricing and rapid self-serve adoption are required - MantaRay SMO appears to be a sales-led, bespoke procurement product with no public list pricing. - If publicly documented security certifications and detailed security feature lists are required before engaging procurement - MantaRay SMO security and compliance posture is not clearly detailed on the public product pages; some operators may prefer vendors that publish explicit compliance documentation. - If the objective is a vendor-neutral, operator-controlled open-source-first SMO - Operator-led stacks using O-RAN Software Community components may be preferable for teams prioritizing maximal vendor neutrality and internal control, albeit with increased engineering ownership. - If the environment is not prepared for closed-loop autonomy governance - Without processes for policy control, testing, and rollback, autonomous actions can introduce operational risk. - Limited public transparency on security and compliance specifics - Key certifications and enterprise security feature detail are not clearly published for MantaRay SMO. - Limited public, user-generated review content - Lack of accessible, product-specific reviews on G2/TrustRadius/Gartner Peer Insights makes independent benchmarking difficult. - Openness and interface support is often staged - Public materials indicate an ongoing evolution toward fuller O-RAN interface support. Procurement teams should request a current interface support matrix (O1/O2/A1/R1, data models, versions) and interoperability test evidence. - Security risk surface inherent in Open RAN interfaces - Independent research on O-RAN highlights that open interfaces and exposed control planes introduce attack surface considerations that require security engineering and operational controls; this applies to SMO deployments generally and is not unique to Nokia.

02Why they buy

- Vendor-reported advantages (require verification) - Nokia reports alignment with TM Forum Autonomous Networks and O-RAN Alliance architecture and states support for open interfaces. - Nokia reports outcome metrics and asserts achievement of certain autonomy levels; the public materials do not disclose full methodologies, so these assertions should be validated via references and trial data. - Differentiation that may be present in practice - Continuity across the MantaRay product family (NM + SON + AutoPilot → SMO) can reduce architecture fragmentation for operators already using MantaRay components. - A vendor-operated rApp marketplace and SDK can provide a structured mechanism for rApp sourcing and lifecycle management, subject to marketplace maturity and certification processes. - Areas where competitors may have advantages - Ericsson provides extensive public material on SMO/rApp ecosystems and a branded platform with ecosystem documentation. - Systems integrators and integrator-led vendors (including Amdocs) may offer broader end-to-end transformation delivery capacity.

03Field reports

- Nokia-publicized outcomes (vendor-reported) - Official vendor product overview and feature pages for MantaRay SMO report performance and automation outcomes such as improved throughput/cell utilization and operational automation metrics (e.g., increased autonomous operations, faster incident detection and repair). These outcomes are vendor-reported and do not include detailed methodology, baselines, network context, or independent validation in public materials. - NTT DOCOMO co-innovation narrative - Nokia describes a collaborative SMO program with NTT DOCOMO involving multi-vendor Open RAN automation. Public descriptions of this collaboration are vendor-authored and may not include detailed challenges, costs, or neutral benchmarks. - Critical evaluation (what’s missing publicly) - Methodology gaps in public case study materials: - Baseline definitions (pre/post conditions) - Sample sizes (cells, sites), duration, and seasonality - Whether improvements were driven by SMO specifically versus concurrent RAN feature upgrades - The degree of vendor versus operator tuning and professional services required to achieve outcomes - Public case studies typically omit negative findings and lessons learned; procurement teams should request documented lessons learned, failure modes observed in trials, and remediation steps.

Availability of conventional SaaS review coverage

Major B2B review platforms (G2, TrustRadius) do not show a meaningful review volume or clearly indexed product page specific to "Nokia MantaRay SMO." This is common for carrier-grade telecom infrastructure software.
Gartner Peer Insights: no readily accessible, product-specific Peer Insights page for "MantaRay SMO" was found in the initial checks; categorization and access constraints can limit visibility for niche telecom products.

Community/social discussion (what is accessible)

Community posts around Nokia announcements appear mainly in investor- and company-focused community forums. These posts typically re-share vendor announcements rather than provide operator user reviews.
For market-signal purposes, community posts referencing Nokia’s licensing arrangements and strategic implications for SMO/automation are present on public forums.

Direct quotes (availability constraints)

There is a shortage of verifiable end-user operator quotes about MantaRay SMO on mainstream review platforms in accessible sources.
Procurement teams and operators should request operator references, trial/PoC acceptance criteria, and measurable outcomes when evaluating the product.

Why customers might select this product (inferred from vendor positioning and market logic)

Operators may select MantaRay SMO when:
- They already use MantaRay NM/SON and prefer an evolutionary path rather than a greenfield SMO stack.
- They want Nokia’s implementation approach to open interfaces, rApp marketplace support, and multi-vendor management.
- They prioritize automation capabilities that have been reported in commercial network deployments.

Why some customers may leave for competitors (evidence limitations)

No strong, direct churn narratives about MantaRay SMO were located in accessible sources.
Broader vendor strategy changes (e.g., RAN vendor swaps) can affect which operations software an operator uses; these dynamics are influenced by RAN vendor strategies, commercial terms, and integration complexity.

04Best fit

Ideal Customer Profile

- Company sizes - Large telecom operators and service providers - Practical proxy: national or regional MNOs with a large number of sites and multi-vendor RAN footprints - Industries and verticals - Telecommunications - Potential adjacency: private wireless / enterprise networks operated by service providers - Roles and personas - Decision makers - VP/Head of RAN Engineering - VP/Head of Network Operations / Autonomous Networks - CTO office (Open RAN strategy) - End users - RAN optimization engineers - NOC/SOC operations teams - Automation/AI operations teams managing rApp lifecycle and policies - Pain points the product addresses - Increasing RAN complexity (features, parameters, algorithms) - Multi-vendor operations complexity and cost pressure - Need for closed-loop automation, faster fault detection/repair, and performance optimization - Qualification criteria (good fit) - Multi-vendor RAN with a need for standardized interfaces and automation - Willingness to invest in integration, governance, and operational change management - Existing MantaRay footprint (NM/SON) that can be leveraged - Deal disqualifiers (poor fit) - Small networks where integration overhead outweighs benefits - Operators seeking transparent, off-the-shelf SaaS pricing and minimal services - Environments lacking organizational maturity for safe closed-loop automation

05The pitch

What the product does (core value proposition in objective terms)

- Nokia MantaRay SMO is Nokia’s RAN-domain Service Management and Orchestration (SMO) platform designed to automate operations across multi-vendor, multi-technology RAN environments. It uses automation techniques and an application model (rApps) to support closed-loop operations. - Nokia states alignment with industry autonomous network frameworks and with O-RAN SMO architecture, and states support for open interfaces intended to enable interoperability. - Nokia describes the product as an extension of the existing MantaRay portfolio (MantaRay NM, MantaRay SON, and MantaRay AutoPilot) toward an O-RAN-compliant SMO with Non-RT RIC capabilities and an rApp marketplace.

Target market and market positioning

- Primary buyers appear to be mobile network operators (MNOs) and telecom service providers pursuing: - RAN automation (SON → intent-based / closed-loop automation) - Open RAN and multi-vendor RAN operations - RAN slicing operations (RAN Slice Controller / slice orchestration) - Cost reduction (opex) and improved network performance/experience - The SMO positioning aligns to the operations/automation layer around RAN, typically discussed alongside Non-RT RIC, rApps, and O1/O2/A1 interfaces.

Get a comprehensive analysis of MantaRay SMO including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →