Why SGP.32 matters for IoT
Earlier eSIM specifications were designed for consumer devices or operator-controlled M2M deployments. SGP.32 is designed for remotely managed IoT devices that may have no screen, keypad or user present.
One device configuration across markets
Choose operator profiles after manufacturing, reducing the need to define every market and operator before the device is built.
Remote profile operations
Download, enable, switch and retire profiles through remote workflows, reducing manual intervention in the field.
More control over operator choice
Give the organisation operating the fleet greater control over profile management and future operator choices.
How SGP.32 works
SGP.32 connects four components: the eUICC and IPA associated with the device, plus the eIM and SM-DP+ services used to manage and deliver profiles.
eIM
The remote management service that determines which profiles devices should hold and initiates profile operations.
IPA
The IoT Profile Assistant associated with the device. It receives and carries out profile-management instructions from the eIM.
SM-DP+
The service that prepares operator profiles and makes them available for secure download.
eUICC
The secure element that stores operator profiles and enables the profile selected for use.
The IPA can be implemented as IPAe in the eUICC or as IPAd in the device operating system. The right approach depends on the modem, operating system and level of device integration.
From manufacturing to fleet operations
Start with bootstrap connectivity at the factory, then manage profile changes remotely through the same platform used for the rest of your connectivity.
Bootstrap connectivity from first power-on
Load a bootstrap profile before shipment so the device can establish initial connectivity when it is first powered on in a supported market.
Fewer regional variants
Reduce the number of regional SIM variants you need to forecast and stock. Download a local profile later where regulation, coverage or cost requires it.
Fleet-wide profile operations
Download, enable, disable and delete profiles for individual devices or defined groups, with visibility into profile state across the fleet.
Automated through your systems
Use REST APIs and webhooks to trigger profile operations from your provisioning, device-management and operational workflows.
Questions from product and engineering teams
What is SGP.32?
How is it different from SGP.02 and SGP.22?
What are the eIM and IPA?
What does our device need to support?
Which SIM form factors are available?
Can we get test eSIMs?
© 2026 Cobira ApS · Sortemosevej 19, 3450 Alleroed, Denmark