SGP.32 isn’t a pilot-phase spec anymore. It’s shipping. Which means the question your team should be asking has already changed from “should we deploy it” to “who actually controls it once we do.”
That’s the exact shift Kaleido Intelligence’s Chief of Research, Steffen Sorrell, and Monogoto Co-Founder & CTO Maor Efrati got into during our live session, Not All SGP.32 Is Created Equal. If you missed it, or want the recording to send to your team, the on-demand recording is live now.
The headline number nobody’s talking about enough
Kaleido’s own research puts cellular IoT at 3.9 billion connections across top verticals by 2030, 57% of the global total. SGP.32 is set to underpin roughly a quarter of IoT eSIM activations by 2029. The standard is done. The certifications exist. First commercial end-to-end deployments are already happening in 2026.
So why does “SGP.32-ready” still mean wildly different things depending on who’s selling it to you?
Because the spec never answered the one question that matters
SGP.32 standardizes the crypto, the signed package format, the operations (download, enable, disable, delete), rollback, and fallback behavior. What it does not standardize: who owns the eIM, the cloud control plane that decides which operator profile lands on your fleet, and when.
And whoever owns that answers a much bigger question: whose devices are they, really, once they’re in the field?
In the session, Maor and Steffen walk through:
- The three ownership models: provider-owned, enterprise-owned, and hybrid; and the very different tradeoffs each one buys you in time-to-live, control, and what happens the day you want to leave
- Why “we support portability” is not the same claim as “you can add a second eIM while you’re still our customer,” and why that distinction is the one worth pressure-testing before you sign anything
- The dormant profile “insurance policy” almost nobody buys, until the day their operator has an outage, hikes rates, or sunsets a network
- What iSIM changes and what it doesn’t, hint: the physical card disappears, the ownership question does not
The three-question test
The session closes with a blunt, three-question test you can run on any vendor, including Monogoto:
- Who owns the eIM my eUICCs are registered to — me, or you?
- Can I add a second eIM alongside yours, while I’m still your customer?
- What is the exit process, fee, notice period, and is it actually in the contract?
A vendor comfortable answering all three has built something open. Vagueness on two or three of them is a walled garden wearing a standards label.
Watch it on demand
If you’re evaluating SGP.32 vendors, building a multi-market IoT fleet, or just tired of “no lock-in” being a sentence instead of a contract term, this one’s worth the 45 minutes.
