Wireless Logic and SGP.32: The Lock That Isn’t a Layer

The short version: Wireless Logic is the one UK player whose lock-in isn’t a layer of the SGP.32 stack at all – it’s the managed-service relationship itself. Kigen locks you at the silicon, 1GLOBAL at the bootstrap, Eseye at the orchestration control plane. Wireless Logic locks you by running the whole machine so capably, and across so much of the stack, that you never build the capability in-house. SGP.32 was meant to commoditise connectivity. Wireless Logic’s answer has been to own more of it.

Who Wireless Logic actually is

Wireless Logic is Europe’s largest independent IoT managed-connectivity group, built from the start to be, in its own founding language, a critical layer between the mobile networks and the organisations that need to use them. That framing is the whole company in a sentence. It is not primarily a chip vendor, an OS vendor or a standards body. It is the intermediary – the business you hire so you never have to deal with carriers, provisioning, compliance and fleet management yourself.

Co-founded by Oliver Tucker and Philip Cole, it has spent years assembling that layer through acquisition and platform investment. Its own carrier-grade core network, Conexa, is the single pane of glass through which customers run their fleets, and it markets a tiered set of eSIM products – a global single-card option, regional multi-network cards, LPWAN SIMs and enterprise connectivity – all sitting on top of the richest carrier ecosystem of any UK player. Gartner has named it a Leader in managed IoT connectivity. Where the other three profiles in this series each own a slice of the SGP.32 architecture, Wireless Logic’s distinguishing feature is breadth: it wants to be all the slices you don’t want to touch.

What Wireless Logic brings to SGP.32

Wireless Logic supports all three GSMA remote provisioning standards – SGP.02, SGP.22 and SGP.32 – and it deliberately presents them as plumbing the customer never has to see. It runs the eIM, sources and manages the profiles, handles the SM-DP+ relationships and the carrier integrations, and exposes the result through Conexa. It has produced an SGP.32 buyer’s guide with Beecham Research, and it consistently frames the standard the same way: SGP.32 is powerful but operationally demanding, and the sensible move for most enterprises is to let a managed provider absorb that complexity rather than build an in-house RSP capability.

That framing is not wrong. Running your own eIM, negotiating your own carrier deals and operating your own profile lifecycle at fleet scale is genuinely hard, and most companies deploying IoT are not, and do not want to become, connectivity operators. Wireless Logic’s pitch – we have already built all of it, just plug in – is a real and valuable offer. It is also, precisely, the mechanism of the lock.

The story behind the facts

The most revealing thing about Wireless Logic in 2026 is not a product announcement. It is the shopping list.

In the space of a couple of years it has acquired Arqia, Brazil’s oldest M2M operator, to take Latin America; Webbing, for global eSIM technology; Blue Wireless, for fixed wireless access across Asia-Pacific and the US; and, on 10 July 2026, Simetry, a Houston managed-connectivity business. The Simetry deal is the tell. Simetry’s value sits specifically in the operational layer – multi-carrier SIM and device management, provisioning, 24/7 support for mission-critical deployments – not in wholesale airtime resale. Wireless Logic is not buying connectivity. It is buying the operational depth that keeps customers dependent after the initial activation.

Here is why that matters for lock-in specifically. SGP.32 was sold, correctly, as the great de-lock-in: separate the eIM, the SM-DP+ and the device-side IPA, and in principle a buyer can switch operators over the air and run a multi-vendor strategy. But that freedom only helps a customer who can exercise it. If Wireless Logic runs your eIM, holds your carrier relationships, operates your single pane of glass and provides the support desk your operations team leans on, then the theoretical ability to switch is worthless – because switching means rebuilding, in-house, the entire capability you outsourced precisely so you would never have to. The standard commoditised the components. Wireless Logic’s strategy is to make sure it still owns the assembly.

Where the lock-in actually lives

This is the flavour of conservation of lock-in that is hardest to see, because there is no single artefact to point at. Kigen’s lock is a chip. 1GLOBAL’s is a bootstrap profile. Eseye’s is an orchestration platform. Wireless Logic’s is a dependency – the accumulated set of things you no longer know how to do because someone has done them for you for years. It looks less like a lock than any of the others, right up until you try to leave, at which point it is the heaviest, because leaving is not a data export. It is rebuilding a department.

None of this is a criticism of doing it. For a large share of IoT deployments, outsourcing the connectivity operation to a scaled specialist is the correct, rational choice, and Wireless Logic is very good at it. The point, as with every profile in this series, is to see the trade clearly: you are buying capability you could not economically build alone, and the price is a dependence that deepens the longer you stay and the more of the stack the provider acquires.

If you are evaluating Wireless Logic

The applied questions for a managed-service lock are not about components. They are about exit and self-sufficiency:

• Can you take the single pane of glass with you? Establish what actually leaves with you if you go – profile ownership, carrier relationships, historical data, automation logic – versus what stays inside Conexa. See what to ask any eSIM provider.
• How much capability are you outsourcing permanently? There is a difference between buying connectivity and buying the ability to operate connectivity. Decide deliberately which you are handing over, because the second is far harder to take back.
• Does the roll-up change your terms? Wireless Logic is acquiring steadily. Understand how consolidation in the market affects your pricing power and your alternatives over a multi-year device lifecycle.
• What would in-housing cost later? Even if you outsource now, price the fallback. A lock you have costed an exit from is a much weaker lock.

Where Wireless Logic sits in the landscape

With Wireless Logic, the four UK lock types are complete and genuinely distinct: Kigen at the silicon, 1GLOBAL at the bootstrap, Eseye at the orchestration control plane, and Wireless Logic at the operational relationship that wraps around all of them. It is the broadest of the four and the hardest to pin to a diagram, because its lock is not a box in the architecture – it is the reason you stopped drawing the architecture yourself. In a standard sold on ending lock-in, the managed-service model is the quiet reminder that the most durable lock has never been technical. It has always been organisational.

By Peter Green