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 SGP.32 marketing does exactly that. Eseye, the Guildford company that has been fighting this particular problem since 2007, is one of the few vendors that says out loud it isn’t true. SGP.32 standardises how an operator profile gets onto a device. It doesn’t sign the operator contract, keep the device online when the network carrying the switch command falls over, or decide whether a meter in Brazil should roam or go local.

Eseye spent nearly two decades building those surrounding pieces before the standard existed. Its story starts not with a SIM but with a radio chip, a lesson learned designing ZigBee, and a stubborn engineering ambition: build a product once, ship it anywhere, and have it simply work. Follow that ambition from Philips to AWS to AT&T and you end up with the clearest case study going for the difference between having an SGP.32 eSIM and actually running global IoT on one.

Eseye SGP.32 at a glance

SGP.32 moves profiles. It doesn’t move connectivity.

Start with what the standard actually does. SGP.32 is the GSMA’s eSIM IoT specification for remote SIM provisioning on devices with no screen, no user and often no SMS. An eIM (eSIM IoT Remote Manager) in the cloud tells an IPA (IoT Profile Assistant) on the device to download, enable, disable or delete operator profiles held on the eUICC. The SM-DP+ prepares and delivers those profiles. That’s the whole job, and the architecture pillar walks through it properly.

Look at that list and notice what isn’t on it. No operator contracts. No coverage. No roaming policy. No billing. No traffic routing. No logic for when to switch. A profile only exists if somebody has a commercial agreement with the operator that issues it, and a device can only receive one if it can still reach the eIM. Eseye’s own SGP.32 material is blunt about this, and its April 2026 announcement framed resilience as something that depends on implementation rather than on the specification. CTO Ian Marsden put the pitch plainly: enterprises want resilience without having to “effectively run their own MVNO”.

That sentence is the whole Eseye proposition. To understand why a Guildford company ended up making it, you have to go back to the late 1990s and a radio standard that has nothing to do with SIM cards at all.

The Eseye story: from a ZigBee lesson to a global eSIM platform

Philips, CompXs and the lesson ZigBee taught

Ian Marsden and Paul Marshall met at Philips Consumer Electronics in the late 1990s, Marsden as a software team leader and Marshall in senior radio design. In 2001 they left to found CompXs, which delivered the world’s first ZigBee design. Marshall developed the first IEEE 802.15.4 radio, the physical layer ZigBee runs on, and Marsden went on to chair the ZigBee Network Working Group. If you have a smart meter, there is a fair chance something they started is talking inside it.

ZigBee left them with a question that turned out to be worth a company. As Marsden has described it, designing ZigBee forced them to ask how you make a product that can be manufactured once, somewhere, and then go anywhere in the world and fundamentally work. Short-range mesh radio couldn’t answer that. Cellular, as a genuinely global standard, could. Except it couldn’t, quite, because every cellular device needed a SIM, and every SIM belonged to one operator in one country.

That is the founding problem of Eseye, and it is worth pausing on, because it is exactly the problem SGP.32 was written to address fifteen years later. The GSMA arrived at “build once, ship anywhere” by committee in 2023. Two radio engineers in Surrey had arrived at it in 2007.

2007: one SIM, many identities

After a successful exit from CompXs, Marsden and Marshall founded Eseye in October 2007 with Julian Hardy, who ran the company as CEO for its first decade. Its first big technical move was the one everything else still rests on: a SIM carrying multiple operator identities. Rather than a single IMSI tied to one home network and its roaming deals, the Eseye SIM could hold several, and switch between them. Marsden and Marshall patented the approach, and it became the multi-IMSI heart of what is now AnyNet+.

It’s worth being clear what multi-IMSI was and wasn’t. It wasn’t remote provisioning in the GSMA sense. The identities were baked in rather than downloaded. But it solved the two problems that actually killed early IoT projects: the device that dropped off a failed network with no way back, and the product that needed a different SIM for every market. One SKU, several ways to reach home.

The M2M years: learning that the device is the problem

For most of its first decade Eseye was an M2M connectivity provider, and a quietly substantial one. By 2016 it was serving customers in 160 countries through more than 440 operator partnerships, and it featured in Gartner’s 2016 Magic Quadrant for managed M2M services.

Those years also gave Eseye the conviction that still defines it. Marsden has written about more than ten years of device optimisation work across over 200 projects, and the lesson from all of them was the same: projects rarely failed because the SIM was wrong. They failed because the modem behaved differently on a second network, the firmware didn’t recover a dropped session, the APN was wrong after a switch, or nobody had tested the device in the country it ended up in. Eseye’s long-running argument, that IoT connectivity starts with the device rather than the contract, wasn’t a slogan. It was a decade of support tickets.

2016: AnyNet Secure and the AWS bet

The first inflection came in 2016 with AnyNet Secure, a multi-IMSI SIM that let devices connect and certify themselves remotely and securely over what Eseye called a managed global network-of-networks. Julian Hardy described the pre-AnyNet Secure provisioning burden as daunting to the point of impossible.

The bigger move was who Eseye pointed it at. It became Amazon Web Services’ global strategic partner for cellular IoT, integrating with AWS IoT Core so that security certificates could be delivered zero-touch to the device, and running a single global private APN for customer traffic. For a Guildford firm with a few dozen engineers, that was a distribution channel no amount of direct selling could have bought. Enterprise customers building on AWS found cellular connectivity that simply plugged in, and Eseye was the company behind it.

2018: the Cisco man arrives

Nick Earle joined Eseye’s board as a non-executive director in 2016 and took over as Chairman and CEO in 2018, with Hardy moving to President to focus on partnerships and new territories. At the handover Eseye counted over 1,000 customers across 130 countries.

Earle’s background matters to this story. At Cisco he ran the cloud and managed services business and worldwide field services, and was tasked with leading the company’s shift from a hardware-centric business to a cloud, software and services-led one. Before Eseye he had been an SVP at Virgin Hyperloop One. In other words, the man Eseye brought in had already run exactly the transition it was about to attempt: from selling a thing, the SIM, to selling a platform. He also became the company’s loudest voice, hosting the IoT Leaders podcast and repeating, to anyone who would listen, that IoT is about the device and the outcome, not the connectivity.

2019: the AnyNet Federation

Multi-IMSI and roaming deals have a ceiling. Roaming is somebody else’s commercial arrangement, and several countries restrict or tax permanent roaming. So at MWC in February 2019, Eseye launched the AnyNet Federation, a new association of mobile operators built for IoT, with MTN bringing its networks across 12 markets as a founding partner. The Federation initially focused on growing cellular connectivity onto AWS, letting customers buy and manage connectivity from within the AWS environment.

What the Federation really created was direct interconnects: operator relationships deep enough to supply local profiles, not just roaming access. Eseye now quotes 25 and growing, inside a total reach of 800+ networks. That is the commercial asset this whole article keeps coming back to, because it is the one thing a shiny new eIM cannot conjure: an operator that has agreed to issue you a local subscription.

2021: TELUS and the operator behind the operator

In February 2021 Canadian operator TELUS launched TELUS Global Connect, a white-labelled global IoT service built on Eseye’s AnyNet platform and multi-carrier eSIM, offering a single SIM with multi-IMSI carrier profiles across 700 networks in 190 countries. Alongside it, TELUS Ventures invested CAD 26.3m, about £15m, in Eseye. Earle called it an inflection point.

He was right, and not just because of the money. TELUS proved a second business model: Eseye didn’t only have to compete with operators for enterprise customers. It could sit inside them, powering a carrier’s own global proposition under the carrier’s brand. That model would later bring in MTN and AT&T, and it explains how a company of Eseye’s size reaches so far beyond its own sales offices.

2022: Infinity and bring your own contract

In May 2022 Eseye launched Infinity, billed as a “mission control” platform and, more usefully, a platform of platforms. It could manage Eseye SIMs, legacy SIMs and emerging iSIMs side by side, and integrate with other providers’ connectivity platforms including Cisco Jasper, Vodafone GDSP and Ericsson DCP. Its software-defined network was designed to onboard new operators quickly, with network switching delivered as a service.

The headline feature was commercial rather than technical. Eseye says Infinity was the first platform to offer Bring Your Own Contract, letting customers bring their own negotiated carrier rates onto a single platform. Earle pitched Infinity as solving carrier lock-in, connectivity and security in a single solution. That’s marketing, but it was also a strategic tell: four years before SGP.32 went commercial, Eseye had already decided that the money would be in orchestrating other people’s connectivity, not just reselling its own.

2023: SMARTconnect, Integra and MTN

Two moves in 2023 extended the platform in both directions. In January, Eseye launched AnyNet SMARTconnect at IoT Solutions World Congress in Barcelona: on-device software, supplied as a plug-in module, that monitors the device’s real connectivity and switches network when things go wrong, with protocol extensions for MQTT, CoAP and LwM2M that respond to the underlying network state. Eseye claimed it could cut device development time by 50%. It was the device-first philosophy finally shipped as a product.

In September, MTN South Africa, a founding Federation partner, chose Eseye’s Integra platform after a tender to power its next-generation global eSIM and IoT service, with the aim of extending it to 18 MTN operating companies across Africa. The same year Gartner named Eseye a Visionary in its Magic Quadrant for managed IoT connectivity services.

2024 to 2025: Thales, Hera and AT&T

In February 2024 Eseye adopted Thales Adaptive Connect, an SGP.32-based service that connects a device to the right local profile when it first powers up and through its life, so manufacturers stop personalising SIMs per country in the factory. COO Adam Hayes framed the benefit as choice: personalise for local networks before deployment, or let TAC do it in the field. The same year it launched the Hera 200, its smallest IoT router to date, a reminder that Eseye still builds hardware.

Then in March 2025, AT&T launched Global SIM Advanced on a version of Eseye’s AnyNet eSIM and Infinity: an AT&T bootstrap IMSI plus up to nine additional network profiles, with in-region routing for low-latency use cases. AT&T has said it found Eseye was already supplying some of its own larger enterprise customers. Earle called the deal a major milestone, and it was the biggest validation yet of the operator-behind-the-operator model.

2026: a new CEO, analyst validation and SGP.32

By 2026 the leadership had shifted again. Tony Byrne, previously Eseye’s CFO and before that a finance director at COLT Telecom and BT Broadband, became CEO, with Earle moving to Executive Chairman. In January 2026 Counterpoint ranked Eseye a Leader in both its IoT connectivity management platform and IoT eSIM orchestration reports, which Byrne read as confirmation that enterprises had moved beyond needing a basic SIM.

And on 22 April 2026, Eseye integrated SGP.32 into AnyNet+ and Infinity, managed alongside SGP.02 and SGP.22 from a single interface. For most SGP.32 vendors, that announcement is the story. For Eseye it was the nineteenth year of one.

What drove Eseye: the key to its success

Strip away the product names and Eseye’s history has a remarkably consistent shape. It kept solving the next layer of the same problem, usually a few years before the market agreed it was a problem. Six things made that work.

A founding problem, not a founding product. Eseye didn’t start with a SIM to sell. It started with an engineering requirement, one product that works anywhere, inherited from ZigBee. Every product since, multi-IMSI, AnyNet Secure, the Federation, Infinity, SMARTconnect and now SGP.32, is another attempt at the same requirement. That gave it unusual strategic continuity for a small company.

Device-first, not SIM-first. Most connectivity providers treat the device as the customer’s problem. Eseye treated it as its own, building routers, on-device software and years of device optimisation alongside the SIMs. It means Eseye sees failures that a pure connectivity reseller never sees, and it is why its SGP.32 pitch leads with resilience rather than with the standard.

Borrowing distribution from giants. The AWS partnership turned a Surrey start-up into the default cellular option for enterprises building on the world’s biggest cloud. Later, TELUS, MTN and AT&T did the same in the operator market. Eseye repeatedly scaled by embedding itself inside bigger companies rather than by trying to outsell them.

Owning the operator relationships. The Federation’s direct interconnects are the asset that SGP.32 cannot replicate. Anyone can buy an eIM. Not everyone has operators willing to issue them local profiles in Brazil, Turkey or the US.

Getting to commercial flexibility first. Bring Your Own Contract landed in 2022, long before “SGP.32 ends lock-in” became a conference slogan. By letting customers bring their own carrier deals, Eseye defused its biggest objection and repositioned itself as the orchestrator rather than the gatekeeper.

The right outsider at the right moment. Nick Earle had already led a hardware-to-software-and-services transition at Cisco. Eseye’s transition from SIM supplier to platform company followed the same playbook, and the timing, platform first and standard second, turned out to be right.

So the USP in one line: Eseye is a connectivity company that thinks like a device engineer and sells like a software platform. Earle’s own description of the founders’ vision was a cloud platform that could connect any device to any network anywhere, giving customers one global SKU for every IoT product. Network switching as a service.

The honest counterpoint

None of the individual pieces is unique. Multi-IMSI SIMs, connectivity management platforms, eIMs and federated roaming all exist elsewhere, and several rivals are much bigger. Eseye’s edge is the combination plus the head start. Its risk is the flip side of that: SGP.32 commoditises the SIM layer, which means Eseye must increasingly win on orchestration alone, against well-funded competitors who have read the same playbook. Third-party trackers put Eseye’s headcount at roughly a hundred-odd people. That is lean for a company with its technology inside AT&T, which is either a sign of a very efficient platform or a sign of how much it depends on its partners. Probably both.

Who Eseye connects

Eseye’s own materials name Amazon, Shell, BP and Bosch among enterprises running hundreds of thousands of connected devices on its connectivity, with Amazon Key for Business as a published case study, and earlier coverage citing Amazon’s locker network, Shell Recharge EV chargers and Itron smart meters. The pattern is consistent: large, geographically spread estates of unattended devices that have to keep working for years in places nobody wants to send an engineer. That is precisely the estate SGP.32 was designed for, which is why Eseye’s customer base is a better guide to its SGP.32 credibility than its press releases.

What SGP.32 provides, and what Eseye adds

The cleanest way to understand any SGP.32 vendor is to separate the GSMA-defined components from everything the vendor wraps around them. Remote profile download is not unique to Eseye. Nor is an eIM, an IPA or an SM-DP+. Those are the standard. The differentiation is in the layers above, below and beside it, and after the history above, every orange box in this diagram should look familiar.

Is Eseye’s eSIM Orchestrator the same as an eIM?

No, and this is the distinction most coverage muddles. The eIM is a defined SGP.32 function: it issues profile operations to the IPA. The eSIM Orchestrator (eSO) is a broader role covering profile lifecycle, network selection, compliance and billing, and Eseye positions Infinity in it. The GSMA architecture explicitly allows an eIM to sit inside a higher-level management system, which is exactly what is happening here.

A useful mental model: Infinity decides, the eIM executes, the IPA obeys, the eUICC stores. Infinity also talks to things that aren’t SGP.32 at all, including SGP.02 subscription managers, SGP.22 profiles and other operators’ connectivity platforms. That is the “platform of platforms” idea from 2022 doing its job. It is also why calling Infinity “Eseye’s eIM” undersells it, and why it is where an Eseye customer’s dependence actually accumulates. More on that below.

Why multi-IMSI still matters after SGP.32

There is a quiet flaw in a lot of single-profile SGP.32 deployments, covered in detail on our bootstrap issues page. If the device has one active operator profile and that operator fails, the device needs connectivity to receive the command that would give it new connectivity. You need the network to fix the network.

Eseye’s answer is to keep its patented multi-IMSI technology underneath SGP.32 rather than replace it. AnyNet+ carries several bootstrap identities, so when the active network goes, the device can usually still get home, and Infinity can then decide whether to sit on the fallback or push a fresh profile. Eseye explicitly contrasts this with SGP.32 implementations that rely on a single operator profile. It’s not a criticism of the standard. Multi-IMSI and SGP.32 solve different halves of the problem, and they stack. There’s a neat irony in it, too: the technology Eseye patented in 2007 turns out to be the safety net under the standard that was supposed to make it obsolete.

Roaming versus localisation

SGP.32 gets sold as the end of roaming. It isn’t. A tracker crossing four European borders a week wants a good roaming profile, not a new local subscription at every frontier. Localisation matters for the other case: a device installed permanently in a market that restricts permanent roaming or wants local data handling. Eseye names Brazil, Turkey and the US among the markets where this bites.

The bottom line of the right-hand column is the one that matters. SGP.32 can deliver a Brazilian profile only if a Brazilian operator has agreed to issue it. That is what the Federation’s interconnects are for, and it’s the asset that took Eseye from 2019 onwards to build. Eseye also quotes 15 regional points of presence for local breakout, which is the part that addresses latency and data sovereignty rather than just the identity on the SIM.

One device, four countries: what a deployment looks like

Take a manufacturer building 50,000 industrial monitors in one factory, destined for the UK, Germany, the US and Brazil. Each unit ships with an SGP.32-capable eUICC, an IPA and bootstrap connectivity. Nobody in the warehouse needs to know which unit ends up in Munich. This is, almost word for word, the problem Marsden and Marshall set themselves after ZigBee.

The interesting bit is the mixture. Infinity’s bring-your-own-contract capability means an enterprise that already has good operator deals doesn’t have to bin them to get global orchestration. Eseye fills the gaps from its own federation. That separates two things the old global-SIM model welded together: who orchestrates the connectivity, and who supplies each subscription. SGP.32 makes that separation practical. Eseye’s bet is that customers will still want someone else running the orchestration.

Three years later, when the German agreement turns sour, the change is a profile operation rather than a fleet of vans. That, not the acronym, is the economic case for remote SIM provisioning.

The operator behind the operator

The least obvious thing about Eseye is how much of its technology ships under other people’s brands. TELUS Global Connect, MTN’s IoT platform and AT&T Global SIM Advanced all run on Eseye machinery. Infinity faces enterprises. Integra faces operators who want to sell global IoT connectivity under their own name without building a federation, a multi-IMSI SIM and an orchestration platform themselves.

This matters for SGP.32 buyers in a way that isn’t immediately obvious. If you buy a “global eSIM” from a large operator, you may already be an Eseye customer one layer removed, and the questions about fallback, localisation and portability below apply to you too. For the wider UK picture of who supplies whom, see the UK SGP.32 landscape.

The small print that turns diagrams into truck rolls

The APN. A router configured for one operator’s APN can switch profile perfectly and then pass no traffic, because the new profile expects a different APN:

APN before switch:  operator-a.iot
APN after switch:   (whatever Operator B expects)
Result:             attached, registered, no data

Eseye’s answer is the single global private APN it has run since the AnyNet Secure era, designed to work across its partner connectivity. Without that, the device needs a reliable way to change its APN remotely, which is a device design decision, not a SIM one.

Old SIMs don’t upgrade over the air. Eseye states that customers on older AnyNet SIMs (ES7xxx and below) need to swap to a current SGP.32-compatible AnyNet+ SIM. SGP.02 and SGP.32 are different architectures, and for most estates the migration will happen at the hardware refresh, not via a cloud upgrade. That is why support for all three RSP models in one place is more useful than it sounds: a utility can easily be running 2019 SGP.02 meters and 2026 SGP.32 sensors side by side well into the 2030s.

The modem. A perfectly orchestrated eSIM cannot make a module transmit on a band it doesn’t support, and plenty of “eSIM-capable” modules aren’t SGP.32-ready at the firmware level. The SIM can go global before the device does, which is the oldest lesson in Eseye’s book. Our SGP.32 modem compatibility page covers the BIP and firmware gap in detail.

The network count. 800+ networks is Eseye’s figure for the scale of its ecosystem, not a promise that any SIM can select any of them at will. Some access is direct interconnect, some roaming, some localised profile. Ask which is which for the countries you actually deploy in.

Where the lock lives

Our position on this site is that SGP.32 doesn’t end lock-in, it moves it. Each UK vendor in this series sits at a different point in that relocation: Kigen at the eUICC OS fixed at manufacture, 1GLOBAL at the bootstrap profile, Wireless Logic at the managed service. Eseye sits at the control plane.

Be precise about this, because it isn’t a hit piece. Eseye’s design genuinely reduces lock-in at the operator and SIM layer. Bring Your Own Contract means you can keep your own carrier deals. Multi-RSP support means you aren’t forced into a rip-and-replace. The eUICC can take profiles from operators Eseye didn’t choose.

But the value that makes all that work, the policies, the switching rules, the contract mappings, the multi-IMSI fallback behaviour and years of per-device connectivity history, lives in Infinity. The better the orchestration, the more of your operational knowledge ends up encoded in it, and the harder it becomes to leave. That isn’t sinister. It’s what orchestration is, and it’s the logical end point of a company that has spent nineteen years moving up the stack. The honest buyer question isn’t “will SGP.32 free me from Eseye?” but “if I leave Infinity in five years, what do I take with me, and does the fallback still work without it?” The multi-IMSI bootstraps, for instance, are Eseye’s patented technology. A profile you downloaded is portable. The safety net under it may not be.

Questions to put to Eseye, or anyone selling SGP.32

Our what to ask an eSIM provider checklist goes deeper, but these are the ones this profile surfaces:

• Who operates the eIM, and can I point my eUICCs at a different eIM later?
• Which SM-DP+ environments do you work with, and which profiles come from my own contracts?
• If the active profile fails, what bootstrap path remains, and is it multi-network?
• For each target country, is the service roaming or genuinely localised, and where does my data break out?
• What happens to my APN when a profile changes?
• Can I manage my existing SGP.02 devices alongside new SGP.32 ones, and what has to be physically swapped?
• If I migrate away from your platform, what configuration, history and profiles can I export, and what stops working?

Eseye SGP.32 FAQ

Who founded Eseye?

Eseye was founded in Guildford in October 2007 by Ian Marsden and Paul Marshall, who had previously co-founded ZigBee pioneer CompXs after meeting at Philips, together with Julian Hardy, who served as CEO for the company’s first ten years.

Who runs Eseye now?

Tony Byrne is CEO, having previously been CFO. Nick Earle, CEO from 2018, is Executive Chairman. Founders Ian Marsden and Paul Marshall remain CTO and CCO respectively.

What is Eseye’s USP?

Eseye combines patented multi-IMSI SIM technology, direct operator interconnects for localisation, a multi-RSP orchestration platform and on-device connectivity software. Individually these exist elsewhere; Eseye’s differentiation is the combination and its device-first engineering approach.

Does Eseye support SGP.32?

Yes. On 22 April 2026 Eseye announced SGP.32 integrated into its AnyNet+ eSIM and Infinity connectivity management platform, managed alongside SGP.02 and SGP.22 from a single interface.

Is Eseye Infinity an eIM?

Not exactly. The eIM is the SGP.32 function that issues profile operations to the device. Infinity is Eseye’s broader orchestration platform, operating in the eSIM Orchestrator role, within which SGP.32 management runs alongside other RSP models and connectivity controls.

What is the difference between Infinity and Integra?

Infinity is Eseye’s platform for enterprises managing their own IoT estates. Integra is the white-label version for mobile operators that want to sell global IoT connectivity under their own brand, as MTN does.

Does SGP.32 replace multi-IMSI?

No. SGP.32 manages full operator profiles remotely. Multi-IMSI provides alternative identities that keep a device reachable when its active network fails. Eseye deliberately layers the two.

Can I use my own operator contracts with Eseye?

Yes, in principle. Infinity has offered Bring Your Own Contract since its 2022 launch, letting enterprises import existing operator agreements and use Eseye’s federation to fill coverage gaps. Feasibility depends on the operator and profile involved.

Do existing Eseye SIMs work with SGP.32?

Eseye says customers using older AnyNet SIMs (ES7xxx and below) need to swap to its current SGP.32-compatible AnyNet+ SIM. Existing SGP.02 deployments generally migrate at hardware refresh rather than over the air.

Which operators use Eseye technology?

AT&T Global SIM Advanced (2025) runs on a version of Eseye’s AnyNet eSIM and Infinity. TELUS Global Connect (2021) is built on Eseye’s platform, with a CAD 26.3m TELUS Ventures investment. MTN South Africa selected Integra in 2023.

Does SGP.32 guarantee global connectivity?

No. SGP.32 standardises profile provisioning. Global connectivity still needs operator agreements, coverage, routing, compatible device hardware and ongoing management, which is the gap Eseye and its competitors are selling into.

Further reading and sources

Within the cluster: the UK SGP.32 landscape, the SGP.32 v1.2 specification explainer (v1.3 was published on 28 May 2026; v1.2 remains the certification baseline), and euicc.co.uk’s news analysis of Eseye’s April 2026 announcement. For the wider market picture, IoT Portal’s mid-2026 UK and European state of play.

Company history: Eseye’s founders on the road from ZigBee; Ian Marsden profile, Computing; AnyNet Secure launch, 2016; Nick Earle appointed CEO; AnyNet Federation and MTN, MWC 2019; TELUS Global Connect; Infinity launch, 2022; AnyNet SMARTconnect launch; MTN selects Integra; Eseye selects Thales Adaptive Connect; AT&T Global SIM Advanced; Counterpoint 2026 rankings; Eseye leadership team.

SGP.32 offering: Eseye SGP.32; Eseye SGP.32 announcement, April 2026.