Feature matrices are easy to win. Add more integrations. Add another dashboard. Put “AI-powered” somewhere near automation. Count the number of countries, APIs and provisioning partners. Then turn the spreadsheet green.

That approach may work for comparing relatively simple software products. It is a poor way to rank eSIM orchestration platforms.

The reason is simple: orchestration is not valuable because of what a platform contains. It is valuable because of what the platform can control when several systems, suppliers and customer journeys have to behave as one operation.

That distinction matters more in 2026 than it did even a few years ago. Consumer eSIM journeys increasingly involve entitlement, device transfer, recovery and OEM-controlled flows. IoT is moving into the SGP.31/32 era. Multi-provider connectivity models are becoming more common. And Counterpoint now evaluates consumer and IoT eSIM orchestration as distinct vendor categories rather than treating orchestration as another feature of remote provisioning.

So if orchestration platforms are going to be ranked, the methodology has to move beyond the brochure.

Rank the control layer, not the components underneath it

An orchestration platform may sit above an SM-DP+, entitlement server, connectivity management platform, billing stack, CRM, support system or several connectivity providers.

Owning those components does not automatically make a vendor a good orchestrator.

Neither does integrating with them.

The real question is whether the platform can coordinate decisions between them.

Consider something as ordinary as replacing a phone. The workflow may need to establish whether the subscriber and target device are eligible, initiate the transfer process, coordinate profile delivery, preserve the existing subscription until the right moment and recover cleanly if the download fails.

READ MORE: eSIM Orchestration Rankings 2026: Amdocs and Valid Lead 

Android’s current architecture makes the point unusually well. Google recommends keeping transfer and final activation separate so that an unsuccessful target-device download does not prematurely deactivate the old subscription. It also recommends fast backend processing for the authorised SIM-swap stage of TS.43 transfer.

The interesting capability is therefore not “supports transfer.”

It is whether the platform can manage the states, dependencies, timing and exceptions that make transfer reliable.

That should be the philosophy behind the entire ranking.

Start with twelve dimensions — but do not treat them equally

A credible eSIM orchestration benchmark needs a stable core methodology. Otherwise every annual ranking becomes a new opinion disguised as data.

Alertify would start with twelve dimensions.

Lifecycle automation and multi-supplier capability deserve the highest weighting because they sit closest to the central purpose of orchestration. A platform should be able to coordinate activation, suspension, transfer, replacement, recovery, top-up and termination without requiring people to manually move between systems. It should also be able to perform those functions across more than one provisioning or connectivity environment.

Supplier independence belongs alongside them. Supporting three suppliers is not the same as being independent of three suppliers. The test is what happens when the customer decides to replace one.

READ MORE: Who Controls eSIM? The Entitlement Battle Begins

Transfer and recovery also deserve substantial weighting. Initial activation is only one moment in what may become a multi-year subscriber lifecycle. Deleted profiles, lost devices, failed migrations and device replacements expose weaknesses that a successful QR-code download never will.

Observability belongs in the top tier too. If a customer cannot activate service, the operator should be able to trace what happened across entitlement, profile inventory, provisioning, device interaction, activation and billing rather than receiving a generic “API error.”

The remaining dimensions are entitlement, workflow configurability, integration breadth and depth, support tooling, billing flexibility, analytics and OEM integration.

A practical 100-point model could allocate 12 points each to lifecycle automation and multi-supplier capability; 10 each to supplier independence, transfer and recovery, and observability; 8 each to entitlement, workflow configurability, and integration breadth and depth; 7 to support tooling; 6 to billing flexibility; 5 to analytics; and 4 to OEM integration.

The precise numbers can evolve. The important thing is that operational consequence should carry more weight than sales visibility.

Evidence should have its own hierarchy

There is another problem with most technology rankings: they score what vendors say they can do.

That is useful, but insufficient.

A proper orchestration benchmark should distinguish between a capability described on a website, a documented API, a demonstrated workflow, a live customer deployment and independently observed performance.

Those are not equivalent forms of evidence.

A vendor saying it supports multiple SM-DP+ environments should receive less credit than one demonstrating the same customer lifecycle workflow across two different environments.

Similarly, “configurable routing” means little unless the buyer can actually change routing behaviour without waiting for the vendor’s engineering team.

A strong methodology could therefore attach an evidence multiplier to each score.

READ MORE: eSIM Orchestration: Open, Closed or Somewhere Between?

Public marketing documentation establishes that a capability is claimed. Technical documentation establishes that it has been designed. A controlled product demonstration establishes that it works under selected conditions. A reference deployment establishes that somebody is using it in production.

The highest confidence should come from reproducible testing.

That would immediately make the ranking harder to game.

The best ranking scenarios begin where demos usually end

Provisioning a working eSIM should almost be the admission test.

The actual benchmark should begin with failure.

Imagine a customer has purchased a plan and payment has succeeded, but the provisioning supplier times out.

What state does the transaction enter? Does the system retry? Can another configured environment be used? Does the customer see a duplicate charge? Can a support agent identify what happened without asking engineering to inspect logs?

Now change the scenario.

The customer is moving to a new device. Eligibility succeeds but the target profile fails to download.

Does service remain active on the original device? Can the attempt be resumed? Is another activation code generated? Does the orchestration layer know which actions are safe and which could create a duplicate or broken subscription?

Or consider a supplier outage.

READ MORE: Inside the eSIM Stack: Who Builds It vs Who Resells It 

A genuinely multi-supplier architecture should be able to explain whether traffic, provisioning or future orders can move elsewhere, which existing subscriptions remain dependent on the unavailable provider and what billing consequences follow.

These scenarios reveal far more about orchestration maturity than asking whether a platform has a “lifecycle management module.”

The original ranking methodology already points toward this kind of testing: device-transfer scenarios, supplier failures and support diagnosis are all more revealing than questionnaire responses alone.

Supplier independence needs a switching test

“Vendor agnostic” may be one of the most overused phrases in connectivity.

It should therefore never be scored from marketing language.

Instead, give the platform a supplier-replacement scenario.

Assume the customer currently uses Supplier A and wants future orders in selected markets moved to Supplier B.

What changes?

If the customer has to redesign its app logic, rebuild billing, recreate lifecycle flows and retrain support teams, the orchestration layer has not abstracted very much.

If the change can be handled primarily through orchestration policies while customer, order and operational state remain consistent, supplier independence is much stronger.

This distinction matters as connectivity platforms consolidate. A vertically integrated stack may deliver excellent operational simplicity. A neutral orchestration layer may deliver stronger optionality. Neither model should automatically score higher.

The ranking should expose the trade-off.

Consumer, travel and IoT cannot have the same winner

A single worldwide “best eSIM orchestration platform” ranking would look attractive.

It would also hide important differences.

A consumer mobile operator cares heavily about device eligibility, entitlement, OEM integration, number continuity, transfer and support.

A travel eSIM platform operates under different pressure. Supplier routing, catalogue complexity, billing models, reinstallation, multi-provider sourcing and support visibility may matter far more.

READ MORE: The eSIM Orchestration Buyer’s Guide: Know When You Actually Need It

IoT changes the equation again. SGP.31/32 introduces eIM-driven management and long-lived remote deployments where bulk operations, automation, resilience, policy control and regulatory requirements become central. Cisco, Tele2 IoT, IDEMIA and Kigen are already illustrating different approaches to this emerging operating model.

The answer is not to invent three unrelated methodologies.

Keep the same core dimensions and change the weighting.

That makes it possible to compare architectures while acknowledging that orchestration is solving different business problems.

Rankings should publish the sub-scores

A final number is convenient for headlines.

It is not enough for buyers.

A platform scoring 86 may be outstanding for lifecycle automation and observability while being relatively closed commercially. Another scoring 82 may have fewer advanced workflows but much greater supplier independence.

Depending on the buyer, the second platform could easily be the better choice.

For that reason, any serious orchestration ranking should publish category scores alongside the overall result.

That also forces the methodology to become more transparent.

Vendors can see where they were strong. Buyers can apply their own priorities. And the ranking becomes useful even to organisations that disagree with Alertify’s weighting.

That is much more valuable than another leaderboard.

The winner should be the platform that stays in control when things go wrong

eSIM orchestration is becoming a recognisable technology category, but it is still young enough for definitions to be stretched.

That makes methodology unusually important.

Counting APIs will not tell buyers whether a platform can recover from a failed transfer. Counting suppliers will not reveal whether any of them can be replaced. Counting dashboards will not show whether operations teams understand why a transaction failed.

The best orchestration platforms should demonstrate four things repeatedly: they know what is happening, they can decide what should happen next, they can coordinate the systems required to execute that decision, and they leave the buyer with meaningful choices underneath.

That is what Alertify ranks.

Not the brochure.

The control.