Eseye and SGP.32: How a Guildford IoT Pioneer Built the Orchestration Layer
Draw an eSIM, draw an arrow to something called an eIM, put an SM-DP+ at the other end and announce that global IoT connectivity is solved. Plenty of...
Read more →SGP.32 Challenges: The Traps That Break IoT eSIM Deployments
SGP.32 does one job well: it gets an operator profile onto an IoT eUICC and switches it on, under the control of an eIM, without anyone touching the...
Read more →Onomondo and SGP.32: Its eSIM, Its New eIM, and the Lock-In It Wants to Break
Onomondo has done something most SGP.32 connectivity providers have quietly avoided: it has built its own eIM, the eSIM IoT Remote Manager, and it says you can use...
Read more →Is Your Cellular Modem Really Ready for SGP.32? BIP, STK and the Hidden Hardware Problem in IoT eSIM
Buying an eSIM-capable modem does not make your product SGP.32-ready. As of August 2026 the specification is stable, certified eUICC hardware is shipping, and the orchestration platforms that...
Read more →The UK SGP.32 Landscape: Who Sits Where, and Where the Lock Lives
The short version: SGP.32 frees the operator profile, but the lock-in does not vanish – it scatters up and down the stack. Four UK companies each own a...
Read more →1GLOBAL and SGP.32: The Lock That Ships Switched On
The short version: 1GLOBAL owns the bootstrap – the profile burned into the device at the factory so it wakes up already connected – and that is where...
Read more →Kigen and SGP.32: The Lock Burned Into Silicon
The short version: Kigen sits on the deepest lock-in point in the whole SGP.32 architecture – and is the vendor working hardest to prove it isn’t one. The...
Read more →Eseye and SGP.32: Where the Orchestration Lock Lives
The short version: Eseye is the clearest UK example of where SGP.32 moves the lock-in rather than removing it. The standard hands enterprises the freedom to switch networks...
Read more →SGP.32 Didn’t End Operator Lock-In. It Moved It.
Answer-first summary: The industry sells SGP.32 as the end of operator lock-in. That claim is half true, which is what makes it dangerous. SGP.32 genuinely dissolves the lock...
Read more →SGP.32 v1.3: What Changed, and Why You Should Still Design Against v1.2
On 28 May 2026 the GSMA published SGP.32 v1.3, alongside a matching SGP.31 v1.3 architecture update and, the day before, an updated eUICC PKI Certificate Policy v2.3. If...
Read more →