Soracom has moved its Connectivity Hypervisor and SGP.32-compatible IoT eSIM ‘s from pre-order to general availability. It signals something bigger: IoT connectivity is moving from a factory decision to a software decision. More about SGP.32 IoT eSIM from Soracom find out below.

The new capability is now available for purchase, with SGP.32-compatible SIMs offered in both card and chip-type form factors. Connectivity Hypervisor lets customers add, remove, manage and switch multiple operator profiles, including third-party MNO profiles, on remote SIMs and eSIMs through an SGP.32 eSIM IoT Manager, or eIM. Soracom also includes a fallback to its own profile so devices can stay connected if a target profile is unavailable.

In consumer eSIM, failure is annoying. In IoT, it can mean a truck disappears from view, a meter stops reporting, or a medical device loses its link.

Why SGP.32 changes the conversation

Enterprise IoT has had an awkward eSIM problem for years. SGP.02 was built for machine-to-machine deployments, but it kept much of the control around operators and provisioning systems. SGP.22, the consumer eSIM model, gave more control to users but assumed a phone-like experience: screen, settings menu, QR code, human intervention.

Most IoT devices have none of that. A utility meter does not scan a QR code. A tracker in a shipping container does not politely choose a profile.

SGP.32 was designed for that gap. GSMA lists SGP.31 and SGP.32 as the IoT architecture and technical specification family, with SGP.32 v1.3 published in May 2026 and active at the time of writing. Soracom explains the difference simply: SGP.22 is built around a device screen and user opt-in, while SGP.32 is built for unattended IoT devices using a remote eIM to manage profiles across a fleet.

In plain English: SGP.32 is what happens when eSIM stops being a user feature and becomes fleet infrastructure.

Soracom’s control-plane angle

Soracom’s move is not only “we support SGP.32.” Plenty of companies are starting to say that. The interesting part is the orchestration layer around it.

Connectivity Hypervisor is positioned as the control plane where enterprises decide which profile runs, where, and when. That can help manufacturers avoid building different SKUs for different markets. It can also help with permanent-roaming rules, local-carrier requirements, shifting commercial terms, and long device lifecycles. Soracom says customers can ship one device and later choose carriers in software, including adding local profiles in the field without a firmware change.

READ MORE: SGP.32 IoT eSIM: What It Means for Global Connectivity

Kenta Yasukawa, CTO and Co-Founder of Soracom, put it this way:

“We built the Connectivity Hypervisor infrastructure before the market asked us to certify it, because we expected SGP.32 would finally allow customers to gain control over which SIM profiles to use where and when. It has done that. Commercial availability means a customer can order a device today that activates through Soracom and has the capability to add and remove profiles in the field, making those devices future-proof and eliminating the need to prepare different SKUs even when deployments cross a border. Managing connections across multiple operators from a single API and console is also a necessity for customers managing a large fleet of devices with multiple profiles.”

That captures the procurement story. Enterprises do not buy SGP.32 because they enjoy standards acronyms. They buy it because they are tired of redesigning devices, renegotiating operator constraints, and learning too late that a “global” SIM is not quite global enough.

A market starting to move

Soracom is not alone. Telenor IoT announced commercial availability of SGP.32 SIM cards earlier in 2026, with deliveries beginning April 17, positioning the standard around single-SKU deployment and remote operator switching. floLIVE has also moved with Kigen, using Kigen’s SGP.32-compliant eIM and secure eSIM OS to support a “factory-to-field” model for global IoT deployments. Eseye is taking a broader orchestration message, promoting support for SGP.02, SGP.22 and SGP.32 within one platform, while also warning that SGP.32 alone does not solve operator relationships, billing, compliance, or device behaviour.

READ MORE: floLIVE Launches SGP.32 IoT eSIM Operations

That caution is useful. SGP.32 is powerful, but it is not magic dust. 1NCE has been particularly blunt, arguing that SGP.32 is not a simple software patch and may require compatible SIM hardware, device support and serious architectural planning. For smaller or single-market deployments, high-quality roaming, multi-IMSI, or a managed global IoT SIM may still be simpler.

Final thoughts about SGP.32 IoT eSIM by Soracom

Soracom’s commercial launch matters because it turns SGP.32 from “roadmap language” into something enterprises can actually buy. But the bigger story is the end of static connectivity planning. IoT companies are no longer building devices for one network, one country, and one commercial model. They are building products that may live for ten years, cross borders, face new roaming rules, and need to stay reachable without a truck roll.

In that world, the winners will not be the providers with the most coverage logos. They will be the ones that make profile control operationally usable: clean APIs, reliable fallback, partner-profile depth, transparent limits, and fleet management real teams can understand. Soracom has a credible position because it combines connectivity, cloud integration and orchestration. The open question is how quickly partner operator integrations mature. That will decide whether Connectivity Hypervisor becomes a niche advanced feature or one of the more practical control layers in the new IoT eSIM stack.