Tec Nikan
فارسی
Talk to us
All news

An eSIM Manager Built to Work Without Its Own Vendor

Onomondo has released an SGP.32 eIM that runs independently of its own connectivity, on the argument that the tool meant to end vendor lock-in should not become the new lock-in point.

eSIMSGP.32vendor lock-incellular IoTfleet management

Onomondo launched its own eSIM IoT Remote Manager on 16 September — the eIM, the control element defined by GSMA SGP.32 that lets an operator remotely download, enable, disable and delete profiles on deployed eUICC devices.

The positioning is unusual: the eIM is designed to operate independently of Onomondo's own connectivity, and is available either with a complete Onomondo ecosystem or standalone with third-party connectivity providers. CTO Henrik Aagaard put the argument directly, calling SGP.32 the industry's opportunity to finally put IoT companies in control of their cellular connectivity, and warning that the tool should not become the new lock-in point.

That warning identifies a real gap. SGP.32 mandates eIM configuration operability for eUICC devices, but technical interoperability does not guarantee commercial interchangeability. A standard that lets you move a profile between carriers is worth little if moving between eIM providers requires the same negotiation the standard was supposed to eliminate.

The buyers this matters to are those managing large, long-lived device fleets — water meters, trackers, industrial gateways, anything with a ten or fifteen year service life. Over that period a carrier will change terms, be acquired, or shut down a network generation, and the alternative to remote profile management is a truck roll per device.

Whether the promise survives contact with procurement depends on exactly the question Aagaard raised, and the honest answer will not be visible until someone actually migrates a fleet from one eIM to another and reports how long it took.

Want to work with us?

Tell us what you're building and we'll help you scope the first deployment.