SGP.32 eSIM: Remote SIM Provisioning Built for IoT
The new GSMA standard makes eSIM practical for unattended devices at scale. Atomic Mobile delivers SGP.32 provisioning, profile management, and connectivity in one platform.
What is SGP.32 eSIM technology?
SGP.32 is the GSMA's eSIM standard for IoT, enabling remote profile download and carrier switching on unattended devices without user interaction. It replaces the complex M2M eSIM architecture with a simpler model using an eSIM IoT Manager (eIM). Atomic Mobile provides SGP.32 provisioning and connectivity as a managed service.
The problem: legacy eSIM standards weren't built for IoT
The consumer eSIM standard (SGP.22) assumes a human tapping a screen; the older M2M standard (SGP.02) demands heavyweight, carrier-hosted infrastructure and pre-negotiated integrations between every party. Both made large-scale IoT eSIM deployments slow, expensive, and operationally fragile — so most fleets stayed locked to whatever SIM they shipped with.
SGP.32 simplifies everything
SGP.32 introduces the eSIM IoT Manager (eIM), which orchestrates profile downloads and switches for entire fleets without device-side user interaction or per-carrier integration webs. Devices ship with a bootstrap profile, connect anywhere, and receive their operational profile over-the-air. Carrier changes later are a platform command, not a truck roll.
- Remote profile download and switching for unattended, headless devices
- Fleet-level orchestration through the eIM — manage thousands of devices as one
- No physical SIM swaps, ever: carrier changes are over-the-air
- One hardware SKU ships globally; the profile adapts to the market
- Standards-based: no proprietary lock-in on provisioning infrastructure
SGP.32 on the Atomic platform
Atomic Mobile pairs SGP.32 provisioning with the connectivity itself: bootstrap profiles, operational profiles on Atomic's multi-carrier network, and lifecycle APIs that tie eSIM operations into your device management stack. UsageIQ closes the loop with near real-time visibility into what every profile is consuming — so profile strategy is driven by data, not guesswork.
Key Capabilities
SGP.32 provisioning
Standards-based remote profile download and switching.
Bootstrap connectivity
Devices connect out-of-the-box anywhere, then receive operational profiles.
Fleet orchestration
Bulk profile operations across thousands of devices via the eIM model.
Lifecycle APIs
Integrate eSIM operations into your own device management systems.
UsageIQ visibility
Near real-time usage data per profile and per device.
Who This Is For
IoT device makers
Design one global SKU and finalize connectivity after devices ship.
Existing IoT fleets
Escape carrier lock-in on deployed devices with over-the-air migration.
Solution integrators
Offer clients future-proof connectivity without proprietary eSIM stacks.
Frequently Asked Questions
What is SGP.32 eSIM technology?
SGP.32 is the GSMA standard for eSIM in IoT devices. It enables remote SIM provisioning — downloading and switching carrier profiles over-the-air — on unattended devices, using an eSIM IoT Manager (eIM) to orchestrate fleets. It replaces the older, more complex SGP.02 M2M standard.
Why is eSIM important for IoT deployments?
eSIM decouples hardware from carrier choice: devices can change networks remotely without physical SIM swaps. For IoT fleets, this means protection from carrier price changes and roaming restrictions, one global hardware SKU, and connectivity decisions that can be revisited long after deployment.
With SGP.32 specifically, these benefits finally work at IoT scale — fleet-level orchestration without user interaction or heavyweight carrier-side infrastructure.
How is SGP.32 different from consumer eSIM?
Consumer eSIM (SGP.22) requires a user to scan a QR code or confirm actions on a screen. SGP.32 removes user interaction entirely: an eSIM IoT Manager remotely triggers profile downloads and switches, making it suitable for headless devices like sensors, trackers, meters, and routers deployed in the field.
Can existing devices migrate to SGP.32?
Devices need an SGP.32-capable eUICC (eSIM chip) and compatible firmware. New designs should specify SGP.32 support now; existing SGP.02-based fleets typically migrate at hardware refresh. Atomic Mobile helps teams plan the transition path and can support mixed fleets during migration.