The eSIM market has spent years discussing who owns the profile, the network and the customer. In 2026, a more interesting question is emerging: who controls the software layer between them?

That question moved closer to commercial reality this year. Counterpoint Research published a dedicated global eSIM orchestration landscape and ranked Amdocs and Valid as the leading consumer-orchestration performers. In July, Soracom made its SGP.32-compatible IoT eSIMs and Connectivity Hypervisor commercially available, allowing customers to manage multiple operator profiles, including third-party profiles, through one control plane. Meanwhile, 10T Tech is marketing an off-the-shelf interface designed to work across multiple SM-DP+ platforms.

None of this means a new software category has fully arrived. It does suggest that eSIM’s most valuable company may eventually be the one that owns neither the radio network nor the profile factory, but makes several of them usable as one system.

Connectivity has acquired a control plane

An eSIM orchestrator sits above infrastructure that other companies may own. Its job is to connect profile repositories, mobile operators, entitlement systems, customer channels and business-support platforms, then coordinate what happens across them.

For a consumer service, that may mean selecting an SM-DP+, checking device and subscriber eligibility, managing activation and transfer journeys, monitoring failures and keeping multiple brands or MVNO tenants separate. Amdocs describes its cloud-native platform as supporting multiple SM-DP+ systems alongside activation, transfer, renewal and lifecycle automation.

READ MORE: Amdocs and the New Battle for eSIM Orchestration

IoT introduces a more explicit role. The GSMA’s SGP.32 architecture separates the profile assistant from the eSIM IoT Manager, or eIM, which can remotely trigger downloads and enable, disable or delete profiles across device fleets. That creates a standards-based place for policy: use operator A in Germany, download a local profile in Brazil, retain a bootstrap profile for recovery, or switch thousands of meters after a commercial agreement changes.

Choosing among roaming networks inside one profile is not the same as managing profiles from different connectivity providers. Marketing departments occasionally blur the two because “multi-network” travels well. Buyers should not.

Payments provides the useful comparison

Payment orchestration became valuable after merchants discovered that connecting several processors did not solve the operational problem. They still needed rules-based routing, retries, consolidated analytics, performance monitoring and reconciliation.

The parallel with eSIM is unusually strong. A profile order can fail. An SM-DP+ can be unavailable. Device eligibility may differ. A preferred provider may have weaker economics, coverage or regulatory suitability in a market. Enterprises may need a local profile rather than permanent roaming. Someone has to interpret those conditions and execute the next action.

READ MORE: Provisioning Is Becoming the Boring Part of eSIM

Stripe’s payment-orchestration product, currently in private preview, illustrates both the appeal and the boundary. It can route payments to supported processors, retry failures elsewhere and compare performance. Yet the third-party processor still carries its fees, liabilities and post-transaction responsibilities.

An eSIM orchestrator faces the same reality. Software can choose and automate the route; it cannot manufacture better radio coverage, rewrite an operator contract or make poor support disappear. Abstraction is useful. Absolution is not included.

The SaaS opportunity is wider than provisioning

The obvious customer is an operator managing more than one provisioning environment. The larger opportunity includes MVNOs, device makers, IoT enterprises, travel platforms, banks and other brands embedding connectivity without wanting to become telecom infrastructure specialists.

Their problem is rarely “We need an eSIM.” It is closer to: we need one integration for several suppliers, consistent activation journeys, usable reporting, commercial controls and the option to change providers without rebuilding the product.

This is where a genuine SaaS company could differ from vertically integrated offers. 1GLOBAL combines orchestration with its own core network, regulatory footprint and SM-DP+ capabilities. Soracom combines orchestration with its broader IoT connectivity platform. Those models reduce vendor complexity, but the customer is still buying into an ecosystem.

A neutral orchestration company would sell control across ecosystems. Its model could combine a platform subscription with charges per managed profile, active connection or workflow, plus modules for entitlement, analytics, policy automation and reconciliation. That is Alertify’s analysis rather than a settled market template; public pricing remains rare, and most current products are sold through enterprise discussions.

The economic test is straightforward. The layer must improve measurable outcomes: faster launches, higher activation success, fewer support cases, lower integration cost, better supplier leverage or reduced downtime. A polished dashboard with several logos is not a category.

Neutrality is difficult to prove

Payment orchestrators can compare processors using relatively mature transaction data. Mobile connectivity is messier. Network quality varies by location, device, frequency support, roaming configuration and time of day. Wholesale contracts may restrict how profiles are sold or moved. Identity checks and local telecom rules do not disappear because an API looks tidy.

A credible eSIM SaaS platform therefore needs more than connectors. It needs standards-aligned lifecycle management, audit trails, role-based controls, retry logic, supplier-level performance data, clear separation between profile availability and actual network experience, and an exit path that does not become another form of lock-in.

It also needs enough commercial access to be useful. The software may be neutral; its inventory never is. Every profile still comes from an operator, MVNO or provisioning partner with its own economics and permissions.

The valuable company may own the decision

eSIM orchestration can become a SaaS category, but IoT is likely to establish it first. SGP.32 gives enterprises a formal remote-management architecture, while long-lived devices make supplier flexibility, regulatory adaptation and recovery economically visible.

Consumer and embedded-connectivity markets should follow as more non-telecom brands sell mobile service inside their apps. The winning orchestrator will not merely connect SM-DP+ platforms. It will show why one route was chosen, what failed, what it cost and whether the customer experience improved.

That is the lesson from payments. Infrastructure remains essential, but the company making decisions above it can capture more strategic value. In eSIM, that company still has to prove it is genuinely independent, operationally competent and useful when the network—not the demo—misbehaves.