Introducing KORE’s SGP.32 eSIM Solution

SGP.32 is the GSMA eSIM standard built specifically for IoT. It is designed for connected devices that may be headless, remote, battery-powered, or deployed in large fleets, with support for remote provisioning and lifecycle management.

SGP.32 matters because enterprise IoT has outgrown rigid connectivity models. As deployments become more global, complex, and long-lived, businesses need a better way to provision, manage, and adapt connectivity over time.

SGP.02 was built for earlier M2M deployments and can be operationally heavy as deployments diversify. SGP.32 is designed for modern IoT operations at scale, helping reduce complexity, improve flexibility, and better support long-lived global deployments.

SGP.22 is designed for consumer eSIM experiences that typically involve user interaction, such as smartphones and wearables. SGP.32 is built for enterprise IoT fleets that need centralized remote orchestration instead of user-led activation.

SGP.32 can help enterprises simplify global deployment, reduce manual SIM operations, support long device lifecycles, and improve flexibility over time. It is especially valuable when connectivity needs may change after devices are already deployed.

Yes. One of the major advantages of SGP.32 is the ability to build one hardware SKU, ship it globally, and localize connectivity remotely when needed. That can help reduce inventory fragmentation, SIM logistics, and forecasting complexity.

Yes. SGP.32 is designed for IoT devices that may not have screens, may be difficult to reach after installation, or may be deployed in remote or distributed environments.

Yes, depending on the connectivity provider. SGP.32 enables remote activation of local profiles, which can help enterprises adapt to country-specific requirements without relying on physical SIM swaps or region-specific hardware. KORE is developing local and roaming profile options for different IoT use cases as part of its SGP.32 eSIM approach.

Yes. SGP.32 is especially relevant for deployments expected to remain in the field for years because it supports remote lifecycle management, future connectivity changes, and adaptation over time without physical intervention.

Yes. SGP.32 is better suited to constrained and low-power IoT environments than older approaches that rely more heavily on SMS-based triggers. That makes it relevant for battery-sensitive, large-scale deployments such as sensors and smart infrastructure.

The strongest fit is usually organizations deploying across multiple countries, managing long device lifecycles, operating large fleets, or supporting business-critical environments where downtime, manual intervention, or lack of flexibility creates real risk.

Strong-fit use cases include global asset tracking, smart metering, industrial IoT, connected healthcare, fixed infrastructure such as kiosks or EV chargers, and large-scale low-power sensor networks.

No. SGP.02 can still make sense for certain legacy fleets, and SGP.22 still fits user-facing devices with app- or screen-based activation. SGP.32 is best understood as the stronger fit for modern enterprise IoT, not as a universal replacement for every use case.

No. A direct over-the-air migration from SGP.02 to SGP.32 is not possible, so new SGP.32-ready hardware is required. Many organizations will likely adopt SGP.32 for new deployments and transition older fleets over time.

It may be a strong fit if you deploy in multiple countries, need a single global hardware approach, expect long device lifecycles, want the flexibility to change connectivity over time, or cannot afford manual intervention when devices are already in the field.