SGP.32 is getting a lot of attention right now, and for good reason. The GSMA specification published in May 2023 finally gives the IoT industry what it has been waiting for: a standard designed specifically for headless, constrained devices that can have their SIM profiles managed remotely without any user interaction at the device.
But there is a gap in the SGP.32 story that most of the coverage misses. SGP.32 defines the infrastructure – the eIM, the IPA, the eUICC, the CoAP transport. What it does not define is the enterprise-facing control layer that sits above all of that infrastructure and makes it accessible to the people responsible for actually running a connected device fleet.
The Problem SGP.32 Does Not Solve
Imagine you are the IT operations manager at a water utility. Your company has 85,000 smart meters deployed across the UK. They run on NB-IoT, they report twice a day, and they have been on the same operator SIM since they were installed in 2022. Your operator has just announced a price increase that will add £400,000 a year to your connectivity bill. A competitor is offering better coverage in the northwest and lower rates across the board.
SGP.32 technically enables you to switch those 85,000 meters to a different operator profile remotely. The question is: what does that actually look like in practice? Who manages the eIM? How do you see the status of each device during the migration? How do you handle the 200 devices where the switch fails on the first attempt? What is the rollback procedure? How do you prove to your operations team that the migration completed successfully?
SGP.32 does not answer those questions. The standard defines the plumbing. The eSIM switching platform provides the controls.
What eSIM Switching Is
eSIM switching is the ability to remotely change a device mobile network profile without physically replacing the SIM card. As a commercial category, an eSIM switching platform is the software that makes this operationally accessible at enterprise scale.
The functional requirements are straightforward:
- A unified view of your entire device estate and current network status
- The ability to instruct individual devices or fleet segments to switch profiles
- A policy engine that automates switching decisions based on signal, cost, location, or operator status
- Audit logging for every switching event
- API access for integration into existing operational toolchains
None of that is exotic. It is standard SaaS product thinking applied to the connectivity control problem. What makes it interesting is the timing.
The Timing
SGP.32 was published in May 2023. Certified hardware is reaching commercial availability in 2025-2026. The operator eIM infrastructure is maturing. The GSMA projects 195 million SGP.32 profile downloads by 2029 – 70% of all IoT eSIM activity.
Every one of those profile downloads represents a device in a fleet that needs to be managed throughout its operational lifetime. At current IoT device lifespans of 10 to 20 years, that is a lot of switching decisions, a lot of migration events, and a lot of operational complexity to manage without a proper control layer.
The market is creating demand for eSIM switching platforms faster than the platforms are being built. That gap is where the commercial opportunity sits.
What Already Exists
Several providers are building toward eSIM switching capability without necessarily naming it that way. Wireless Logic has built substantial eIM infrastructure and positions their platform as connectivity orchestration. Eseye offers multi-network profile management through their AnyNet+ platform. Tele2 IoT has built out bootstrap and provisioning capabilities that feed into managed switching for their hardware partners.
What is largely absent is a clean, vendor-neutral, product-category-named eSIM switching platform – something that positions itself explicitly as the control layer for profile orchestration, acknowledges the SGP.32 standard as its technical foundation, and presents the enterprise value proposition clearly without hiding it behind MVNO product branding.
That gap will close. The question is who closes it first and whether they name the category while doing so.
The SGP.32 Connection
SGP.32 is the standard. eSIM switching is the application. The relationship is the same as the one between TCP/IP and the internet applications that run on top of it. The protocol makes the capability possible. The application layer is where users actually interact with it.
For anyone building or specifying IoT connectivity infrastructure today, understanding both layers matters. The SGP.32 architecture guide on this site covers the standard in depth. The eSIM switching concept covers what the application layer looks like and why it matters commercially.
The devices are being deployed. The standard is maturing. The hardware is arriving. The control layer is the piece that is still being built.