SGP.32 is commercially available now. Here's what actually changed for IoT fleet management.
tl;dr: SGP.32 is the new GSMA standard for remote SIM provisioning built specifically for IoT, not smartphones. It enables zero-touch provisioning, remote carrier switching, bulk profile management, and single-SKU global deployments. Commercially available now. Full implementation guide here.
The core problem SGP.32 solves is one most IoT teams know well: the logistical complexity of managing physical SIMs across thousands of devices, the inability to change carriers remotely when performance issues come up, and the friction of deploying globally while navigating local regulatory requirements. The older standards weren't built for this. They were built for smartphones.
SGP.32 is the GSMA's latest remote SIM provisioning specification, designed specifically for IoT deployments where embedded, headless devices are the norm. It's been finalized, and a few providers including Hologram have commercial availability now.
The practical difference comes down to a few things.
First, the architecture. The eIM (eSIM IoT Remote Manager) acts as the central orchestration point for profile management across a fleet. It handles bulk provisioning operations, policy enforcement, and integration with existing IoT platforms. This is the piece that was missing from earlier M2M approaches, a server-side component designed for automated, fleet-scale operations rather than one-at-a-time consumer provisioning.
Second, deployment flexibility. The IPA component can live inside the device itself (IPAd) or be hosted externally on a gateway or cloud platform (IPAe). That second option is what makes SGP.32 practical for constrained sensors that don't have the processing headroom to run provisioning logic on-device. The tradeoffs between IPAd and IPAe are worth reading through if you're still in the hardware design phase.
Third, protocol support. Earlier eSIM standards assumed devices could handle consumer-grade communication overhead. SGP.32 adds native support for CoAP and MQTT, which are essential for battery-powered and resource-constrained devices.
For teams planning 2026 deployments, the operational shift is from reactive SIM management to proactive, software-defined connectivity. Faster time-to-market for new products, simpler global expansion, and the ability to optimize carrier relationships based on real-time performance data rather than static contracts.
On cost: implementation runs $25,000–$50,000 total for smaller deployments under 1,000 devices, $50,000–$150,000 for mid-size deployments between 1,000 and 10,000 devices, and $150,000+ for larger fleets with decreasing per-unit costs. Ongoing eSIM profile costs run $0.50–$2.00 per profile depending on the provider, plus platform fees of $0.10–$0.50 per device per month. For deployments over 1,000 devices, typical ROI timeline is 6–12 months.
Hologram's SGP.32 Hyper SIMs are available now. For fleet-level profile lifecycle management, their Conductor platform handles automated profile switching, failover rules, and remote recovery without physical access to devices.
Posted Jun 8, 2026, 4:43 PM UTC · locked