Vendor lock-in in IoT is rarely a single decision. Nobody signs a contract intending to be stuck. Lock-in builds up quietly, through a carrier’s SIMs soldered into devices, a provider’s portal that becomes the only place certain tasks can be done, years of device history stored in a format only one system understands, and integrations built against one vendor’s API.
Each choice made sense at the time. Together, they decide how much room an enterprise has to adapt when circumstances change.
And circumstances always change. The real question isn’t whether an enterprise will want to switch providers. It’s whether the organization can absorb change over the life of its devices without rebuilding how it operates.
Why Lock-In Matters More in IoT Than in Most Technology
Most enterprise software is replaced every few years, and the cost of moving is mostly a migration project. IoT is different, because the devices outlive the decisions made around them. A smart meter can stay in the field for ten to twenty years, and smart metering is only the sharpest example. Industrial sensors, connected fleet hardware, and remote monitoring equipment routinely run through several carrier contracts, platform generations, and organizational changes before they’re retired.
Over that span, a great deal can shift underneath a deployment:
- Carriers change their pricing, coverage, and commercial terms, and some networks are sunset entirely.
- Regulations change, including rules on permanent roaming and data residency that affect how devices can be connected in a given country.
- The enterprise itself changes, through acquisitions, divestitures, new regions, and new business units with their own preferred providers.
- Technology changes, as eSIM, satellite connectivity, and private LTE or 5G networks become part of the estate.
None of that is predictable in detail at deployment time. What is predictable is that change will come, and that a program locked to a single provider will have to absorb it the expensive way.
The Five Forms of IoT Lock-In
Lock-in shows up in different layers of the stack, and it helps to separate them.
Physical lock-in. Devices with carrier-specific SIMs can’t change networks without someone visiting them. For assets in remote or hard-to-reach locations, that site visit is often the single biggest barrier to change.
Contractual lock-in. Bundled agreements, volume commitments, and provider-managed SIM inventories make leaving costly even when it’s technically possible.
Operational lock-in. When a provider’s portal is the only place teams activate, suspend, and report on devices, the organization’s processes are built around that tool. Changing providers means retraining people and rewriting procedures.
Data lock-in. Device history, usage records, and audit trails stored in a provider’s system, often keyed to SIM rather than to device, don’t move cleanly. When the provider goes, much of the context goes with it.
Integration lock-in. Connections to ITSM, finance, and security systems built against one provider’s API have to be rebuilt for every new provider added.
Physical lock-in gets the most attention, and eSIM has made real progress against it. But the other four can keep an enterprise tied to a provider long after its SIMs have become technically flexible.
What “Provider-Agnostic” Should Actually Mean
Many platforms describe themselves as provider-agnostic. The useful test is whether that independence covers all five forms of lock-in, not just the SIM. In practice, a genuinely independent approach has a few characteristics:
- It sits above providers rather than belonging to one. Carriers, connectivity management platforms, and eSIM providers plug into it, and none of them owns it.
- It keeps one device-centric record. The record follows the device, not the SIM, so a new profile or carrier doesn’t start its history over.
- It normalizes actions and data. Activating, suspending, or reporting works the same way whichever provider is underneath, so adding one doesn’t add a new process.
- It integrates once. Enterprise systems connect to the governing layer, not to each provider separately.
- It makes connectivity changes a policy decision. Moving devices between networks happens by rule and remote workflow, not by field visit.
eSIM Is Necessary, but Not Sufficient
eSIM under the GSMA SGP.32 standard is a real step forward. Devices can receive and switch carrier profiles over the air, which addresses physical lock-in directly and is especially valuable for long-lived devices in places nobody wants to drive to. Simetric’s SIM and eSIM lifecycle management covers that layer, including fleets still running SGP.02, the earlier M2M provisioning model many deployments haven’t fully migrated off.
But the ability to change profiles raises a new question: who decides when a profile changes, and which systems record it? If that decision lives in one provider’s tooling, the enterprise has traded one kind of dependence for another. Owning the orchestration control plane is what turns eSIM’s technical flexibility into an operational choice. For Simetric, eSIM is one capability within a governed lifecycle rather than the point of it, and Simetric Validated eSIM Orchestration runs each profile change as a validated, repeatable workflow driven by enterprise policy. (Learn more about eSIM orchestration.)
Watch: Simetric CEO Allen Boone on Why the IoT Stack Is Coming Apart
This is exactly the shift Simetric CEO Allen Boone unpacks in the first episode of Simetric Signals. SGP.32 disaggregates what used to be a tightly-coupled eSIM stack, trading inflexibility for a new kind of complexity, the one this article is about putting back together on your own terms.
Simetric Signals, Season 1, Episode 1: The IoT Stack Is Coming Apart
Allen Boone, CEO, Simetric
Read the transcript
The promise of SGP.32, or the promise of eSIM in general, especially as it’s related to the IoT industry, has been something that’s been talked about for many years. And we started out with the SGP.02 spec, and that SGP.02 spec, if you really look closely at what it did, it worked well for people that really needed and wanted a technology stack that was very tightly coupled.
And for those like me that have been in the technology industry for many years, we’ve seen this repeatedly, this notion of being able to create a solution of different pieces of applications that become very tightly interwoven and fulfill a need. Now, what that also means is that this technology stack can be a little bit inflexible, and in the case of SGP.02, it was fairly expensive, so it didn’t really fit the need of the billions of devices that aren’t cars or aren’t high value-oriented devices.
So there’s been this promise of SGP.32 and what that SGP.32 spec means for the industry, and it’s very exciting. We saw this coming as we digested the spec, but we also need to be clear about what it’s done. What it does, in effect, is it disaggregates that very tightly interconnected SGP.02 spec. So you’ve got a disaggregation of the technology stack, and from within that disaggregation comes an enormous amount of flexibility, an enormous amount of customization in how enterprises want to utilize eSIMs, and that’s very powerful.
But what we noticed at the time, and again, if you’ve been in the technology industry for a long time, when you have to reaggregate a tech stack and do it with levels of flexibility in what you’re trying to accomplish, it creates a fair amount of complexity. So what we did at Simetric is we are trying to allow for people to reaggregate that tech stack in a way that fits their needs, so they get all the great benefits of eSIM and this SGP.32 standard, but we can hide some of the complexities that arise from that disaggregation and really hit the need of what the enterprise is looking for.
Designing for Change From the Start
The cheapest time to avoid lock-in is before the estate grows. A few decisions make the biggest difference:
- Choose eSIM-capable hardware for long-lived or hard-to-reach devices, so physical lock-in isn’t designed in.
- Keep the system of record in the enterprise’s hands, tied to devices rather than SIMs.
- Integrate enterprise systems with the governing layer, not with individual providers.
- Separate commercial relationships from operations, so changing a contract doesn’t mean changing a process.
- Plan for multiple providers from day one, even if the first deployment uses only one.
How Simetric Keeps the Options Open
Simetric is a carrier-agnostic enterprise orchestration control plane, and because it doesn’t sell connectivity, SIMs, or eSIMs, it has no stake in which provider an enterprise picks. Its job is to keep the operating model steady while the carriers, platforms, and profiles beneath it are free to change.
The same independence works at large volumes, too. Simetric’s governance spans millions of SIMs across more than 300 mobile network operator integrations and 1,200+ normalized APIs, which means a new carrier or region is usually a configuration decision rather than a new integration project. Because Simetric sits above the carriers, an operator can execute a change across every carrier in the estate in a single session, rather than working portal by portal. And because device history, policies, and integrations live in the orchestration control plane, they stay intact when a provider is added, changed, or retired.
The result isn’t a program built around switching. It’s a program that can absorb a carrier sunset, an acquisition, a new region, or a new connectivity type without rebuilding how it runs. Simetric’s multi-carrier IoT management is designed for that kind of long-term flexibility, so enterprises can adopt, govern, and scale connected technologies safely, deliberately, and repeatedly.
Frequently Asked Questions
How can enterprises avoid vendor lock-in in IoT?
By addressing all five forms of lock-in, not just the SIM: using eSIM-capable hardware, keeping a device-centric system of record under enterprise control, integrating enterprise systems with a governing layer instead of individual providers, and separating commercial relationships from day-to-day operations.
Does eSIM eliminate IoT vendor lock-in?
Not on its own. eSIM under GSMA SGP.32 removes much of the physical barrier to changing networks. But if profile decisions, device history, and integrations still live in one provider’s tooling, the enterprise remains dependent on that provider operationally.
What is a provider-agnostic IoT platform?
It’s a platform that sits above carriers, connectivity management platforms, and eSIM providers rather than belonging to one, normalizes data and actions across them, and keeps device history and policies under enterprise control. That way providers can be added or changed without rebuilding operations.
Is avoiding lock-in the same as switching carriers often?
No. Most enterprises don’t want to switch frequently. Avoiding lock-in is about keeping the ability to adapt when carriers, regulations, technology, or the business itself change, without disrupting devices in the field or rebuilding operational processes.
Keep Your Options Open
If your devices, records, and processes are tied to one provider today, the cost of change is already building up. Schedule a demo to see how Simetric keeps the operating model stable across your carriers and providers, or read how the Simetric platform stays independent of any one provider.