What Comes After Provisioning? The Future of eSIM
For years, Remote SIM Provisioning (RSP) was the headline act of eSIM. It solved something real: how do you move connectivity from a physical object to a digital workflow? Future of eSIM architecture
That shift mattered. It’s what allowed QR codes, instant activation, and the entire travel eSIM category to exist. Under standards like SGP.22, provisioning became a “pull” experience. The user scans, the device downloads a profile from an SM-DP+ server, and you’re connected.
But here’s the uncomfortable truth: provisioning is no longer where the real innovation is happening.
It’s table stakes now.
And the industry knows it.
The architecture we built around provisioning
To understand what’s changing, you need to look at what provisioning actually is under the hood.
The classic consumer eSIM stack looks like this:
- eUICC (the chip)
- LPA (software on the device)
- SM-DP+ (profile delivery server)
- SM-DS (discovery layer)
It’s elegant. It removed vendor lock-in from earlier M2M standards and simplified profile downloads dramatically.
But it’s also… static.
Provisioning assumes a moment in time:
You install a profile → you use it → maybe you switch later.
That model worked when connectivity was a product.
It breaks when connectivity becomes infrastructure.
Why provisioning is starting to feel… old
There are three reasons provisioning is quietly losing relevance.
It’s event-based, not continuous
Provisioning is about getting connected.
Modern use cases are about staying optimally connected.
Latency shifts. Network quality changes. Pricing models vary by location and time.
Provisioning doesn’t handle that. It just gets you in the door.
It puts too much responsibility on the user
Even in 2026, most flows still look like:
Scan → install → manage → troubleshoot.
That’s fine for a tourist buying 5GB in Spain.
It’s completely broken for:
- enterprises managing fleets
- apps embedding connectivity
- always-on devices
It doesn’t scale to invisible connectivity
The moment you remove the UI, provisioning starts to collapse.
That’s exactly why the industry had to build SGP.32, a new standard designed for devices that don’t have screens at all.
And this is where things get interesting.
Enter orchestration, not provisioning
What SGP.32 introduces is subtle but important.
It shifts control away from the user and into platform-level orchestration.
Instead of:
User triggers profile download
You now have:
A remote manager (eIM) decides what profile should be active, at scale, without user interaction
That’s not provisioning anymore.
That’s connectivity orchestration.
And once you see it that way, the entire architecture changes.
The rise of the “connectivity layer”
What’s emerging now is a different mental model:
Connectivity is no longer a product you install
It’s a layer that adapts in real time
This layer does things provisioning never could:
- Dynamically switch profiles based on performance
- Route traffic based on latency or policy
- Apply enterprise rules across thousands of devices
- Optimize cost without user involvement
You already see early versions of this in:
- enterprise eSIM platforms
- multi-IMSI architectures
- API-driven connectivity providers
But the real shift is conceptual.
Provisioning was about delivery.
What comes next is about control.
Why APIs are becoming more important than profiles
Here’s where most people still underestimate what’s happening.
The value is moving away from the SIM profile itself…
…toward the interface that controls it.
In SGP.22, the profile is the product.
In newer architectures, the product is:
- the API
- the routing logic
- the policy engine
Profiles become interchangeable.
This is why infrastructure players are gaining power:
they sit above provisioning, not inside it.
And it’s also why two providers with “the same coverage” can deliver completely different experiences.
Because the differentiation is no longer in provisioning.
It’s in what happens after.
What this means for travel eSIM (and why most miss it)
Travel eSIM is still largely stuck in provisioning thinking.
- Buy a package
- Install a profile
- Use it until it runs out
But if you look closely, the cracks are obvious:
Same destinations
Same pricing structures
Same “unlimited” claims
Completely different real-world performance
Why?
Because provisioning is identical.
Architecture is not.
Some players:
- route traffic locally
- prioritize networks differently
- dynamically manage profiles behind the scenes
Others don’t.
From the outside, they look the same.
Underneath, they’re entirely different systems.
Where this is heading
The next phase of eSIM architecture is already taking shape.
And it looks less like telecom… and more like cloud infrastructure.
You’ll see:
- Zero-touch connectivity
Devices and apps connect without explicit provisioning flows - Policy-driven networks
Connectivity becomes programmable, not predefined - Real-time switching at scale
Not “download a new profile,” but “adjust in milliseconds” - Embedded connectivity inside platforms
Airlines, banks, travel apps integrating connectivity as a feature, not a product
SGP.32 is just the beginning of this shift. It introduces the idea of remote, platform-controlled profile management at scale.
But the real story is what comes after that.
Conclusion: Provisioning isn’t dead. It’s just no longer the point.
The industry spent a decade solving how to digitize SIM distribution.
That problem is largely solved.
Standards like SGP.22 made provisioning accessible. SGP.32 is making it scalable and invisible.
But the competitive frontier has already moved.
The real battle is now happening above provisioning:
- orchestration layers
- API ecosystems
- network intelligence
Compare how different players are positioning themselves:
- Traditional eSIM providers still compete on packages and destinations
- Infrastructure players focus on control, APIs, and integration
- Enterprise platforms treat connectivity as a managed resource, not a product
And that gap is only going to widen.
Because once provisioning becomes invisible,
the only thing that matters is what controls it.
That’s where the next generation of winners will be built.

