Eseye adds SGP.32 support to AnyNet+ eSIM platform

Eseye has added SGP.32 support to its AnyNet+ eSIM and Infinity connectivity management platform, extending its approach to managing global IoT connections.

The update centres on the GSMA's latest remote SIM provisioning standard for IoT, designed for devices that need connections managed remotely, including constrained endpoints. The platform now supports SGP.02, SGP.22 and SGP.32 through a single interface.

Rather than presenting remote provisioning as a complete answer, Eseye frames the launch around a broader operational challenge in IoT deployments: keeping devices connected when networks fail, regulations vary by market, and long-lived devices need support across multiple countries.

Resilience focus

Eseye argues that while SGP.32 defines profile delivery, it does not by itself address network fallback, continuity across multiple networks, or the operational controls needed to avoid outages. Its Infinity platform takes on the eSIM Orchestrator role introduced by the standard, covering profile lifecycle management, network selection, compliance and billing.

The company combines this with multi-IMSI support, bootstrap connectivity and managed orchestration services. That mix is intended to reduce the risk of devices being stranded in the field if a profile switch, network change or commercial arrangement fails.

The argument reflects a wider debate in the IoT market over whether newer eSIM standards simplify global deployments or shift more technical and commercial work onto device owners. SGP.32 has been welcomed as a standard built for IoT use cases, particularly for constrained devices that may not support SMS and instead use lightweight protocols such as LwM2M or CoAP.

Large-scale deployments still face practical constraints, including local compliance rules, data sovereignty requirements, operator agreements, and the need to maintain service during transitions between profile types or connectivity models.

Managed model

Eseye expects many enterprises to use SGP.32 as part of a managed service rather than run it directly themselves. It argues that handling multiple profiles, network contracts, technical settings and connectivity platforms without a unifying orchestration layer can create operational risk.

Its broader platform also works with remote SIM provisioning providers including Thales, IDEMIA and Kigen. Eseye says this vendor-neutral approach is intended to help customers manage migrations between standards and avoid committing to a single provisioning model.

According to the company, its network footprint spans more than 800 networks across 190 countries, and it has delivered more than 1,000 IoT projects.

Industry discussion around SGP.32 has increasingly focused on how the standard fits into existing estates, rather than whether it replaces earlier models outright. Many enterprises already operate a mix of SGP.02, SGP.22, roaming arrangements and multi-IMSI strategies, particularly in sectors where connected assets remain in service for years and cannot be easily recalled for upgrades.

Eseye says migration between these approaches should be treated as a managed transition within a common orchestration framework, noting that physical and technical constraints mean such migrations are not always seamless.

A central theme in its message is that remote profile switching should be used selectively for localisation, lifecycle management and resilience, rather than as a routine mechanism for frequent commercial switching between operators. In practice, that means the value of SGP.32 may depend less on the switch itself than on the systems governing when, why and how it happens.

Ian Marsden, Chief Technology Officer and Co-Founder at Eseye, said: "SGP.32 is an important step forward for IoT, but true resilience depends on how it's implemented. By integrating SGP.32 into our Infinity platform and AnyNet+ eSIM, Eseye delivers multi-network continuity, fallback and orchestration guardrails, so enterprises get the resilience they need without having to become connectivity experts or effectively run their own MVNO."

He added: "However, the industry should be careful not to confuse remote provisioning with operational resilience. Giving customers a red button to switch networks without the right guardrails may sound empowering, but in practice it can increase risk, complexity and the chances of self-inflicted outages. The real opportunity is to give enterprises the best of both worlds: the flexibility of remote provisioning with the operational guardrails, automation and expertise needed to protect uptime at global scale."