At this year’s Mobile World Congress, one theme stood out across conversations with customers, partners, and analysts: the IoT connectivity industry is moving beyond the plastic SIM. What is emerging is not just a shift in technology, but a fundamental change in how connectivity is deployed, managed, and operated.
With roughly 450 million IoT devices shipped globally each year, we are approaching a turning point. The emergence of the SGP.32 standard signals something bigger than another technical update. It marks the beginning of the software-defined era of IoT connectivity.
For decades, connectivity followed a predictable model based on ordering, shipping, and inserting a SIM card into a device. With SGP.32, that model no longer applies. Connectivity becomes something that must be continuously operated across the lifecycle of a device rather than deployed once.
The industry is not simply replacing plastic SIM cards with digital profiles. It is fundamentally changing how connectivity is deployed, managed, and operated. Standards define the architecture. How that architecture is operated is what determines outcomes.
This shift is widely acknowledged at a high level, but its operational implications are still underestimated.
From a Linear Process to a Managed System
For most of its history, connectivity followed a simple and predictable model.
A SIM card was ordered, shipped, inserted into a device, and activated on a network. Once deployed, it remained largely static. Connectivity was something you set up once and rarely revisited.
With SGP.32, this model no longer holds.
Devices now rely on an initial bootstrap connectivity layer, profiles are provisioned and updated remotely, and connectivity can change over time depending on location, performance, or business requirements.
These profiles act as the digital identities of a device. A bootstrap profile establishes the initial connection and ensures the device can come online, while operational profiles provide day-to-day connectivity and can change over time depending on location or regulatory requirements.
What used to be a one-time deployment becomes an ongoing process. Connectivity is no longer a component. It becomes a system that must be continuously managed across its lifecycle.
A Structural Shift Is Underway
Across the ecosystem, customers, partners, and analysts are converging on a shared conclusion: Connectivity is entering a new operational phase where deployment, management, and lifecycle control are tightly interconnected. At the same time, there is still limited alignment on how this model works in practice.
Earlier eSIM standards introduced important capabilities but struggled to scale across diverse IoT deployments. SGP.32 moves closer to addressing these limitations and also introduces new dependencies across systems, vendors, and processes that are only now becoming visible in real-world deployments.
The transition is underway, and the path toward scalable and interoperable implementations remains uneven.
From SIM Logistics to Digital SIM Logistics
The real transformation is not from SIM to eSIM, but from physical logistics to digital logistics-what we at emnify call Digital SIM Logistics.
This is not just a feature or a component. It is a new category that defines how connectivity is operated in a software-defined world.
The ability to operate this system -not just participate in it- is what will differentiate providers in the next phase of IoT connectivity.
Digital SIM logistics spans multiple layers:
- eUICC hardware embedded in devices
- bootstrap connectivity to establish initial network access and enable profile provisioning
- profile provisioning across providers
- orchestration layers coordinating systems and decisions
- policy control and lifecycle automation over time
What was previously a linear supply chain becomes a multi-layered system that must be coordinated continuously across stakeholders and platforms. It is no longer a single-threaded process, but a multi-threaded one that requires ongoing orchestration.
Flexibility Is Not the Same as Simplicity
The prevailing industry narrative focuses on flexibility and programmability. But this framing overlooks something critical.
Software-defined connectivity does not remove complexity. It redistributes it.
Control of infrastructure, not just access to it, is what determines how manageable that complexity becomes.
Enterprises are no longer managing SIM cards. They are coordinating systems, providers, and lifecycle processes across a fragmented ecosystem - one that spans multiple connectivity vendors, platforms, and integration points that must remain aligned over time.
The problem is no longer getting devices connected. It is keeping an increasingly fragmented system working.
This introduces a new class of operational challenges. Systems may become misaligned across providers, profile behavior can vary between vendors, and integration overhead increases as deployments scale. These issues often do not appear in early pilots and become critical at production scale.
Flexibility without orchestration introduces operational risk. This remains the most underestimated aspect of the shift.
Bootstrap Connectivity Is the Entry Point
At the center of this new model is a layer that often goes unnoticed: the bootstrap layer.
Every SGP.32-enabled device depends on an initial mechanism to establish connectivity, authenticate, and begin its lifecycle. Without this step, no profile can be provisioned and no orchestration can take place.
This makes bootstrap connectivity more than a technical prerequisite. It defines how reliably and at what scale devices can enter the connectivity lifecycle.
In a world of digital SIM logistics, bootstrap connectivity becomes the entry point into the entire system. It determines whether devices can be activated globally from day one, how quickly they can be brought online, and how smoothly they transition into operational profiles.
This is also where architectural differences become visible. Many providers approach bootstrap as a resale layer, relying on third-party infrastructure and indirect network access. This limits control, consistency, and scalability.
In contrast, a native bootstrap approach is built on direct network relationships and owned infrastructure, enabling full technical and commercial control from the moment a device connects.
While often treated as an implementation detail, the bootstrap layer is emerging as a distinct layer within the connectivity architecture. As deployments scale, its role becomes increasingly critical to ensuring consistency, coverage, and operational reliability across regions and environments.
Real-World Implications for IoT Deployments
One customer operating smart EV charging infrastructure across thousands of distributed devices relies on always-on connectivity as a core part of their business model. In these scenarios, connectivity is no longer a static infrastructure decision. It becomes part of the operational model of the business. Devices must be activated seamlessly, remain connected across different environments, and adapt over time as conditions change.
Enterprises now must manage a set of interdependent processes: device activation at scale, continuous profile management, cross-provider orchestration, and lifecycle governance as fleets grow and conditions change.
At the same time, traditional challenges such as multi-SKU device management and factory enablement remain relevant. These challenges intersect with the new digital model and can introduce additional complexity if not addressed within a coherent operating framework.
Operating Connectivity, Not Just Providing It
This raises a fundamental question about responsibility in the new model.
As the ecosystem becomes more fragmented, simply providing connectivity is no longer sufficient. The challenge shifts toward coordinating how connectivity works across multiple systems, providers, and lifecycle stages.
This requires aligning multiple layers that must remain synchronized over time:
- bootstrap connectivity
- profile provisioning
- orchestration across platforms
- lifecycle management across devices
If these elements fall out of sync, the system breaks down.
At the center of this system is the bootstrap layer. It is the entry point into the lifecycle and the foundation that everything else depends on.
Many of these challenges are not entirely new. They were simply hidden by a simpler, more linear model. As that abstraction disappears, the need to actively operate connectivity becomes visible.
This requires a fundamentally different architecture. Connectivity needs to be managed as a unified control layer rather than a set of static integrations. This is where a cloud-native approach becomes critical to operate connectivity consistently on a global scale.
That architecture is ultimately defined by how bootstrap connectivity is implemented and controlled.
At emnify, we have built this architecture by owning and controlling the bootstrap layer.
We are not a reseller of connectivity. Resellers depend on third-party infrastructure. We operate our own. As a native bootstrap provider, we own the core network infrastructure required to operate connectivity globally, including the HLR and HSS systems that enable bootstrap at scale.
This allows us to provide bootstrap connectivity across the full lifecycle of a device, independent of the operational profile in use. This level of control is not possible in resale-based models. Customers can rely on a consistent, globally available entry point into the connectivity system, without being tied to a single provider or constrained by indirect network access.
At the same time, we provide operational profiles on the same underlying infrastructure. This ensures consistency in behavior, features, and performance- avoiding the fragmentation that occurs when profiles are orchestrated across multiple cores and vendors.
By combining native bootstrap capabilities, direct network relationships, and a cloud-native architecture, we enable enterprises to operate connectivity as a unified system rather than a collection of loosely connected components.
The Shift Moves to Execution
The transition to software-defined connectivity is inevitable, and the defining question is how it is operated in practice.
Digital SIM logistics introduces new responsibilities across systems, stakeholders, and lifecycle stages. This fundamentally changes how connectivity must be designed, implemented, and managed.
Success in this new model depends on the ability to:
- activate devices globally from day one
- maintain connectivity across regions and providers
- adapt profiles over time as conditions change
- ensure continuity across the full lifecycle
The companies that succeed in this next phase will be those that can operationalize this model at scale. Providing connectivity alone is no longer enough. The ability to manage it as an integrated, reliable service across a complex ecosystem becomes the differentiating factor.
This transition is already underway. The industry is moving from early alignment toward execution, where operational capability will determine who leads.
The companies that will lead are not the ones who understand the shift. They are the ones who can operate it.
In a system defined by coordination, control, and scale, the architecture behind that operation becomes the differentiator.
