Eseye sells IoT continuity across the carrier boundary

Summary

Eseye is best understood as a managed IoT connectivity and eSIM orchestration provider. The paid unit is not just a SIM card; it is an account that combines multi-network access, device-lifecycle control, carrier localization, cloud/API integration, support and recurring management through Eseye's Infinity platform.
The public evidence supports the Cloud service dependency and Cross-border connectivity topics. Eseye offers customer-facing platform accounts, SIM lifecycle management, reporting, billing, API integration, cloud connectivity, support tiers and single-platform management for IoT estates across many markets.
Network-resource evidence is useful but bounded. Public RIPE data shows Eseye organization records and provider-assigned address ranges, while PeeringDB did not show a matching public network profile in the searches used here. That supports an operating-surface clue, not a claim that Eseye runs an independent public backbone.
The main judgement risk is execution rather than stated market fit. Eseye's proposition depends on carrier partnerships, permanent-roaming and localization rules, support quality, platform reliability, customer trust and the ability to keep replacing brittle one-carrier arrangements with a managed continuity account.

Why this account matters

A device fleet does not ask whether the procurement team bought a clean telecom contract. It asks whether the payment terminal can authenticate at the roadside, whether the coffee machine can report a fault before a technician visits the wrong site, whether a health monitor can stay connected when the user crosses a region, and whether a field device can be repaired without someone opening the enclosure to change a SIM. That is the commercial opening for Eseye. The company is not trying to sell cellular data as a commodity bucket in the way a consumer mobile plan does. It is selling a managed control layer around cellular IoT, where the customer has more to lose from a silent device than from a marginally higher per-megabyte charge.

This makes Eseye a useful company for reading the boundary between telecom infrastructure and cloud service. The physical access still depends on mobile network operators. Radio coverage, spectrum, local lawful-intercept rules, wholesale roaming, outage handling and network acceptance remain carrier and regulator territory. Yet the enterprise buyer often experiences the problem through a platform account: activate a SIM, suspend a device, set connectivity rules, see data use, route traffic into a cloud environment, receive support, and decide whether a device is ready for another market. Eseye's public pages repeatedly frame the offer around this account experience. AnyNet+ is the multi-IMSI eUICC SIM product. Infinity is the connectivity management platform. Integra is the white-labelled eSIM orchestration offer for mobile network operators. Secure Cloud Connect is the device-to-cloud routing and cloud integration offer. The company also sells support packages and consulting-like help around device readiness, certification, deployment and troubleshooting.

The important point is that the economic unit is continuity. Eseye's customer is often not buying one national network. It is buying the ability to keep a fleet connected through many networks, many years and many product revisions. The company therefore earns its place in a cloud-service category through a customer-facing managed platform and recurring service surface, not through evidence of owning a large autonomous network. A global operator can undercut a reseller on raw connectivity in one market. A specialist platform provider competes by making cross-border connectivity less brittle, by giving the customer a single operating console, and by translating carrier complexity into policy, support and billing controls.

That distinction matters for public judgement. Eseye's claims about 800-plus networks, 190-plus countries and near-100% uptime describe the ambition and marketed outcome of its partner model. They do not, by themselves, prove every customer gets the same performance, that every local roaming rule is solved, or that a carrier will accept every device indefinitely. The evidence supports a strong service thesis but still requires caveats. For a buyer, the question is not whether Eseye can name many networks. It is whether its platform, carrier relationships, support organization and device-specific advice can reduce the failure modes that normally appear after deployment.

Identity and legal footprint

Eseye Limited is a UK private company registered with Companies House under company number 06397669. The official register lists it as active, incorporated on 12 October 2007, with a registered office at 20 Nugent Road, Surrey Research Park, Guildford, England, GU2 7AF. Its listed SIC activities are wireless telecommunications activities and information technology consultancy activities. Those classifications fit the public commercial identity: the company sits between telecom access and technical implementation, rather than presenting as a pure software vendor or a conventional regional ISP.

Companies House filing history shows recent corporate activity, including group accounts made up to 31 December 2024 filed on 1 October 2025 and multiple share-allotment filings in 2025 and 2026. The public filing record does not, by itself, explain revenue quality or profitability in the material reviewed for this article. It is still useful because it anchors the legal entity, registered address, continuing status and activity codes. The company should therefore be treated as an operating UK technology company with a telecom-adjacent registration, not as a newly formed shell or an untraceable domain-only vendor.

Eseye's leadership and board pages reinforce the same identity. The current leadership page names Tony Byrne as CEO, Nick Earle as executive chairman, Ian Marsden as founder and CTO, Paul Marshall as founder and CCO, Adam Hayes as COO, David Langton as CMO, Anand Gandhi as SVP Worldwide Sales, Kirsty Kay as SVP Human Resources, Kieran McNamara as GM North America and Ana Carolina Bussab as Managing Director - Brazil. The page emphasizes technical and telecom backgrounds: Byrne previously worked in finance roles at COLT Telecom and BT Broadband; Marsden and Marshall have hardware, radio and embedded-design histories; Hayes' role includes commercial and regulatory arrangements with carrier partners. The board page names directors and advisers with Cisco, TELUS, investment and telecom backgrounds.

The current public profile is broader than the original machine-to-machine connectivity language that surrounded many IoT firms in the 2010s. Eseye now presents itself as a global IoT connectivity and eSIM orchestration company. It still sells SIMs and routers, but the identity is no longer just "SIM supplier." The product family now includes connectivity management, eSIM orchestration, cloud integration, intelligent on-device connectivity software, support packages, and services that help customers design, test, certify and deploy devices.

That evolution is commercially important. A SIM-only supplier has less strategic power if carriers reduce roaming friction or if device makers integrate connectivity management directly. A platform and service supplier can defend the account by becoming the customer's operational control point. The company still depends on carriers, cloud providers, standards and device makers. But it tries to sit where the customer makes decisions: which network profile to use, how to localize, when to suspend or activate a SIM, how to route data, how to read device status, and who answers when the connection fails.

What Eseye is selling

Eseye's core offer has three visible layers. The first is connectivity access through AnyNet+ and related SIM/eSIM products. The official AnyNet+ page describes a multi-IMSI eUICC SIM for IoT devices with access to more than 800 mobile networks in more than 190 countries, multiple SIM form factors, LTE/4G/3G/2G, NB-IoT support, 5G readiness, over-the-air profile updates, up to 10 bootstrap profiles, and localization through eUICC network switching. In plain terms, Eseye wants a device maker to avoid the classic problem of shipping different SIM variants for every country and then finding out, years later, that a permanent-roaming rule or network sunset has stranded part of the estate.

The second layer is platform control. Eseye's Infinity connectivity management platform is described as a way to manage SIM activation, suspension and termination, ordering, billing, reporting, alerts, data use, connectivity status, location data, network switching and API integration from one account. The same page says customers can set connectivity rules using a combination of eUICC-orchestrated localization, roaming and on-SIM switching logic. It also highlights "bring your own contracts," where a customer can keep an existing mobile operator agreement but use Eseye's platform and AnyNet Federation infill to extend coverage options. That is a more nuanced position than a simple global MVNO pitch. Eseye is saying it can manage both its own connectivity options and external carrier contracts within a common operating view.

The third layer is service and support. The service-level page describes support packages from basic business-hours email support to enhanced and premium tiers with phone support, public-holiday support, out-of-hours emergency telephone support, quarterly review meetings, a technical account owner, service-achievement reporting and one-hour first response for Priority 1 incidents in higher tiers. This is part of the paid unit. IoT fleets create support load because failures are hard to diagnose. A device may fail because of firmware, antenna design, local carrier refusal, building coverage, a suspended subscription, an API problem, a cloud certificate problem or a regulatory rule. A provider that sells only data cannot easily own that diagnosis. Eseye sells itself as a company prepared to sit across device, network, platform and cloud.

The company also has a cloud-integration layer. Secure Cloud Connect is positioned as a way to send data securely from devices to AWS IoT, Azure IoT, Google Cloud Platform and other cloud environments using regional points of presence, policy-based networking, private APN and VPN tunnels, and IoT security concepts. An AWS Partner Network post from 2018 describes Eseye as an AWS IoT Competency Partner and says its AnyNet Secure SIM integrated with AWS IoT Management Console for remote activation, provisioning, authentication and certification. Even though that post is older, it is third-party support for the idea that Eseye has long sold connectivity as part of a cloud-managed device flow rather than as a loose SIM resale.

The MNO-facing Integra offer is a fourth angle. Eseye describes Integra as an end-to-end global IoT connectivity solution for mobile network operators, backed by eSIM orchestration and federated localization. The page says the offer includes policy-based software-defined networking, a global MPLS backbone, data centers, regional points of presence, multi-currency billing, backend integration and access to the AnyNet Federation across more than 800 networks in more than 190 countries, including 25 direct interconnects. The existence of an MNO-facing white-label proposition matters because it shows Eseye is not only trying to win enterprise end-customers; it is also selling its platform and orchestration layer into carriers that need global IoT coverage without building every relationship themselves.

Why the carrier boundary is the product

The expensive part of global IoT is not always the radio session. It is the carrier boundary. A device can be designed in one country, manufactured in another, shipped with a single SKU, installed in a third market, repaired by a service partner, connected to a cloud account in a fourth jurisdiction, and moved again after resale. A direct carrier contract can be efficient when the estate is national, stable and high-volume. It becomes less convenient when the product needs to work across many markets with uneven radio coverage, different roaming practices and different device lifecycles.

Eseye's pitch is that a customer should not need to solve those boundaries alone. Multi-IMSI and eUICC allow a device to move between operator profiles without changing physical SIMs. A platform account can hold lifecycle state, usage information, support cases and billing. Support staff can help distinguish a device problem from a connectivity problem. Carrier relationships can provide fallback options. Cloud integration can reduce the number of steps needed to attach device identity and telemetry to business systems.

This is why the company repeatedly uses examples such as vending, EV charging, healthcare, asset monitoring, logistics and smart buildings. These are not just vertical labels. They are cases where a disconnected endpoint changes economics. A vending machine that cannot report stock or faults loses revenue and sends field staff to the wrong problem. An EV charge point that cannot authenticate or transmit payment-state data can become a visible customer failure. A telecare device that loses connection is not just a cost issue; it becomes a trust and safety issue. A logistics tracker that cannot report across borders loses the reason it exists. These fleets often have low data use but high outage sensitivity. They are therefore good candidates for a provider whose unit of sale is continuity and operational assurance, not cheap bulk data.

The carrier boundary also explains why permanent roaming and localization are not side issues. BEREC's 2023 call for input said permanent roaming is increasingly important for many M2M and IoT use cases because devices may stay connected outside their home country for extended periods. It said regulators were examining obstacles for operators to negotiate roaming agreements, whether visited networks allow permanent roaming for those services, and what pricing schemes apply. That regulatory context is central to Eseye's thesis. If permanent roaming were always stable, cheap and accepted, fewer customers would need an orchestration provider. If every market required a fully local contract with no practical remote profile management, the cost of global device fleets would rise. Eseye's commercial opportunity sits in between: helping customers avoid, reduce or manage those constraints through local profiles, eSIM orchestration and operator federation.

Standards and timing

Eseye's SGP.32 positioning is timely because the industry is moving from earlier remote-SIM-provisioning models toward IoT-specific orchestration. GSMA's SGP.32 v1.3 page, published in May 2026, describes a technical specification for remote provisioning and management of eUICC in network-constrained and user-interface-constrained IoT devices, including architecture, interfaces and security functions. That matters because many IoT devices cannot rely on a consumer-style user flow. A sensor, meter, tracker, vending controller or medical device may have no screen, limited power, intermittent bandwidth and a long service life. The owner needs a managed way to change profiles at fleet scale.

Eseye's SGP.32 page claims support for SGP.02, SGP.22 and SGP.32 in a single orchestration framework. It describes a workflow in which devices are equipped with eSIM and an IoT Profile Assistant, profiles are requested based on policy and device needs, profiles are prepared through SM-DP+, installed on the eUICC, and then managed through their lifecycle. It also says Eseye's orchestration layer unifies SGP.02 and SGP.32 environments across global device estates. The company's own CTO commentary on the page is careful in one useful way: SGP.32 is not presented as the whole solution. It is presented as one piece of a broader framework that still requires multi-IMSI, platform support and managed choices across standards.

The standards story is good for Eseye, but it is not risk-free. SGP.32 can help normalize functions that specialized vendors previously differentiated on. If the standard lowers the cost for carriers, device makers and platforms to implement remote provisioning, Eseye has to keep proving value in orchestration, carrier reach, support, integrations and enterprise operations rather than relying on the novelty of eSIM management. The company's benefit is that it has already built public product language around multi-standard support and platform-agnostic orchestration. The risk is that customers will compare Eseye against carrier-native platforms, global MVNOs, eSIM management rivals and internal teams that can assemble the stack themselves.

The market timing therefore favors vendors that can make standards operational. A specification does not negotiate roaming terms, diagnose device firmware, design antenna placement, identify a poor local bearer, handle a support case, or give a customer one bill. Eseye's argument is that it can turn eSIM standards into a managed service. The public evidence supports that claim as an offer. It does not prove that the service is always superior to alternatives in every market. That is the buyer's diligence question.

Revenue and pricing logic

Eseye's public pricing page does not publish a simple tariff card. It directs prospects to book a meeting or send a pricing request. That is consistent with a managed enterprise IoT model. Pricing likely depends on device count, data volume, countries, profile requirements, support level, cloud integration, device assessment, certification, custom APN/VPN needs, MNO contracts, and whether the buyer is an enterprise, carrier or system integrator. The public AWS post from 2018 showed an example subscription structure for a demo solution, but it is too old and too specific to use as a current tariff. It is still useful because it shows that the managed-network cost could be packaged with monthly platform-style charges, messages and IoT analytics usage in a cloud-integrated deployment.

The revenue logic is attractive if the customer estate scales. The first stage of an IoT deployment is costly because devices must be designed, tested, certified, integrated and supported. The later stage can become recurring if the device remains in the field for years. Eseye's AnyNet+ page explicitly talks about devices staying in the field for up to 20 years. The commercial prize is therefore not just first shipment. It is the long tail of active SIMs, platform seats, support, cloud integrations, profile changes and data management over the device life.

Recurring value is not guaranteed. Some IoT projects fail before scale. Some customers begin with a managed provider and later move high-volume deployments to direct carrier contracts. Some regions may be served better by a local carrier or a specialist MVNO. Some device makers may design their own connectivity-management layer once they reach enough volume. Eseye's defense against those leakages is to make the platform and support account hard to replace: one view of SIMs, one bill, one set of APIs, a support relationship, carrier fallback, localization options and a record of device behavior across markets.

The cost base follows from that model. Eseye must pay for wholesale connectivity, maintain carrier relationships, operate platform infrastructure, support cloud and API integrations, employ technical support and device experts, maintain sales and customer-success teams, and keep up with standards such as SGP.32. It also has to absorb the cost of investigating failures that may originate outside its direct control. A G2 reviewer captured this structural issue in a market-signal way: troubleshooting can be difficult because of reliance on third-party mobile network operators, even when the team is responsive and knowledgeable. That is not a contradiction of Eseye's proposition. It is the proposition's core burden. The company is paid to reduce the friction created by a supplier base it does not fully own.

Supplier and upstream dependence

Eseye's public pages make its upstream dependence visible. The company talks about the AnyNet Federation, mobile network operator partners, regional points of presence, cloud providers, private APN, VPN tunnels, policy-based networking, direct interconnects and cloud integrations. Those are strengths only if the relationships, routing, support and commercial terms keep working. The same facts create dependence. A carrier can change roaming policy. A country can restrict permanent roaming. A network can retire 2G or 3G. A cloud provider can change APIs or pricing. A SIM or module vendor can change certification status. A customer can deploy a device with poor antenna performance, then expect the connectivity provider to fix what is really a hardware problem.

Eseye addresses some of this by starting "with the device." That phrase appears throughout its public positioning and is more than marketing. IoT connectivity failures often originate before deployment: antenna placement, radio module choice, firmware reconnect behavior, power management, network scan logic, SIM profile handling, certificate management, and enclosure design. A provider that can test devices, advise on certification and support pre-deployment validation can reduce future support costs. The company sells free SIM trials, device assessment, readiness assessment, certification and deployment support, which are all ways to move problems earlier in the lifecycle.

The public network-resource evidence is more modest than the commercial network claims. RIPE data shows Eseye organization records, including an LIR organization record for Eseye Limited and provider-assigned address ranges with the Eseye name in Manx Telecom-managed records. Route records for the sampled ranges point to Manx Telecom origin AS13122. PeeringDB API searches for Eseye returned no matching public network or organization record in the checks used for this article. This means the public network evidence should be graded as medium: useful proof of telecom operating surface and registry presence, not proof of a large independently peered network. Eseye's service may still be strong because its model depends on carrier and platform orchestration rather than self-owned public routing. But the distinction should be kept clear.

The MNO-facing Integra page claims a global MPLS backbone, data centers, multiple regional points of presence and 25 direct interconnects. Those are material claims because they support the argument that Eseye has more than a reseller portal. They should be read as company claims unless matched to independent network-map, ASN, facility or carrier documents. For this article, they support the product thesis and the network-dependence analysis, not a public-network-operator thesis.

Customer evidence and use cases

The strongest public customer evidence comes from visible case studies and partner pages. TELUS' own 2021 announcement says TELUS Global Connect was launched through a strategic partnership with Eseye and would provide access to 700 networks across 190 countries. TELUS said its customers would receive a global IoT connectivity management platform powered by Eseye's AnyNet Connectivity Platform, with localized IoT connections in key markets, options for AWS and Microsoft Azure integration, support from TELUS' IoT Centre of Excellence and a TELUS Ventures investment of C$26.3 million in Eseye. This is important because it is a carrier-side endorsement of the white-label and platform thesis, not just an Eseye self-description.

AWS' APN blog gives another third-party angle. It describes Eseye as an APN Advanced Technology Partner with AWS IoT Competency and explains a use case where the AnyNet Secure SIM integrates with AWS IoT, AWS IoT Analytics and device shadows for asset tracking. The specific hardware in that 2018 post is dated, and the post should not be used as evidence of current pricing or current product architecture. But it supports the continuity of Eseye's device-to-cloud positioning and confirms that major cloud integration has been part of the public offer for years.

Eseye's Costa Express case study is useful because it turns the abstract connectivity pitch into a fleet problem. The page says Costa Express vending machines use Eseye's Hera 604 IoT router and AnyNet+ SIM, handling multiple radio access types including 3G, 4G/LTE and Wi-Fi. It says the machine reports sensor and health data to help diagnose faults, reduce downtime and support international expansion. The page's customer quote states that the managed service and support for multiple cellular networks in each region help Costa deploy connected devices and deliver drinks internationally. This is exactly the kind of account where a SIM is not enough. The buyer needs machine telemetry, alerting, connectivity fallback and support.

EV charging is another relevant vertical. Eseye's support page quotes Charge Your Car on end-to-end connected-solution management and 24/7 support. The InstaVolt case study says InstaVolt selected Eseye as a connectivity partner because of near-100% connectivity in the UK and because fast charging requires reliable connectivity for customer experience. An EV charging customer does not care whether the underlying failure is a carrier issue, a router issue, a SIM profile issue or a backend issue. The visible failure is a charge point that cannot complete a session. That strengthens the logic of a managed continuity account.

Public review signals are mixed but useful. G2 lists Eseye as an IoT Connectivity Management product with a 4.4 out of 5 score from 27 reviews in the captured page. Reviewers praise global reach, multi-network SIMs, a single platform and support, while some criticize a slow or frozen platform, support response times, ticket handling, API limits, APN outages, SIM registration issues and dependence on third-party mobile operators. Trustpilot shows only one old review, from 2021, criticizing North American voice call termination and support explanations; because it is a single review and the page itself says the company has not invited reviews, it should be treated as a weak signal rather than a representative measure. Glassdoor employee reviews are generally positive in aggregate, but also contain at least one negative review about the India office. These are not proofs of service quality. They are market signals that show both customer value and operational friction.

Competition and substitutes

Eseye competes against several substitute routes, not just named rivals. The first is a direct carrier contract. A large enterprise with concentrated demand in one country may get better pricing, tighter service accountability and more direct control from a national mobile network operator. The weakness of that substitute appears when the same device fleet needs multi-country deployment, fallback across networks, local profile management, cloud integrations and a single view across markets. Direct carrier contracts are powerful when the footprint is simple and volume is high; they become work when the footprint fragments.

The second substitute is a global MVNO or managed IoT connectivity platform. These providers can also offer multi-network SIMs, management portals, APIs, private APNs and support. The competitive question becomes whether Eseye has better carrier reach, better localization, stronger device expertise, better support, more flexible contract handling, stronger platform control or better cloud integration. Buyers will also compare user experience, API limits, support tiers and actual incident handling. Public review comments suggest the platform and support experience can be a differentiator in either direction.

The third substitute is an eSIM orchestration specialist. As SGP.32 adoption increases, the market may split between connectivity providers that bundle data and orchestration, and orchestration platforms that help customers manage profiles across operators while leaving connectivity procurement more open. Eseye is trying to sit in both roles: enterprise connectivity provider, MNO white-label enabler and eSIM orchestration layer. That can be powerful if customers want one accountable partner. It can be less compelling if the customer wants to keep connectivity procurement separate from profile-management software.

The fourth substitute is in-house connectivity management. A mature device maker with enough scale may hire telecom specialists, negotiate carrier agreements, build internal SIM lifecycle tools, integrate directly with cloud providers and manage support through its own network operations function. That route can reduce vendor dependence but increases organizational complexity. It also moves the burden of permanent roaming, carrier changes, outage triage, support tooling, billing reconciliation and certification into the customer. Eseye's sales task is to show that the outsourced account is cheaper and safer than building that competence internally.

Competition therefore turns on accountability. Eseye cannot promise to own every radio and regulatory variable. It can promise to coordinate them. The more the customer values coordination, the stronger Eseye's account position becomes. The more the customer values raw carrier price or direct network ownership, the more exposed the company becomes.

Regulatory and geopolitical risk

Global IoT connectivity is a regulatory business even when it looks like a software account. Permanent roaming, local-numbering rules, lawful interception, data location, cybersecurity, sanctions, device certification, emergency-service obligations, 2G/3G sunsets and local telecom licensing can affect whether a device remains connected. BEREC's work on M2M permanent roaming and the ITU's 2023 report on roaming aspects of IoT and M2M both show that regulators treat long-lived cross-border IoT as a real policy subject rather than a simple extension of consumer roaming.

The regulatory risk has two sides. On one side, restrictions on permanent roaming make Eseye more valuable if it can provide localization, multiple profiles and a compliance-aware carrier structure. On the other side, tighter rules can make the service more expensive or less universal if local arrangements are hard to obtain. Eseye's Secure Cloud Connect page also introduces data-sovereignty and GDPR-related language through regional datacentres and policy-based networking. That supports the idea that compliance is part of the offer. It does not prove that every deployment meets every local requirement. Compliance still depends on customer use case, data flows, cloud region, operator terms and local law.

Technology sunsets are another regulatory-adjacent risk. IoT devices often remain in the field longer than consumer phones. A device installed with 2G or 3G assumptions may face carrier shutdowns before the commercial life ends. Eseye's AnyNet+ page says its SIM supports LTE/4G/3G/2G and NB-IoT and is 5G ready, but support for a technology on a SIM does not keep a retired network alive. The value lies in planning and migration. Device makers need to understand whether their module, antenna, firmware and certification are ready for the networks that will exist years later.

Geopolitical risk appears through carrier selection and data routing. A global IoT fleet may have devices in countries with different attitudes to foreign SIMs, local routing, cloud storage and telecom security. The buyer may want a single global account, but local authorities may want local compliance. Eseye's localization and eSIM orchestration claims address this tension. The public evidence supports that the company recognizes the problem. Buyers still need deployment-specific advice rather than assuming a global SIM is a universal exemption from local telecom rules.

Evidence limits

This article treats Eseye's public claims as evidence of offer and operating surface, not as audited performance. The company's pages support the existence of managed IoT connectivity, eSIM orchestration, platform accounts, cloud integration, support packages, customer case studies and a global carrier-partner model. TELUS and AWS add third-party evidence that Eseye has been used in carrier and cloud contexts. Companies House anchors the legal entity. RIPE and route data show a telecom-related registry surface but not an independent public backbone. Review sites provide buyer and employee signals, but they are not statistically complete.

The main unverified items are financial quality, exact current revenue mix, gross margin, churn, customer concentration, active device count, support incident performance, the current contractual depth of every carrier relationship, and the measured availability of the service by region. Public pages describe over 1,000 projects, 800-plus networks and 190-plus countries; TELUS' 2021 release described more than 2,000 customers at that time. Those figures are useful, but they come from company or partner marketing contexts rather than audited operating metrics.

Another limitation is that current Companies House group accounts were available as a filed PDF, but the document was image-based in the local capture used here and was not text-extractable. The filing history confirms the existence and filing date of group accounts made up to 31 December 2024, but this article does not rely on unverified extracted revenue or profit figures. A manager reviewing the piece should audit those accounts separately if the final article needs financial statements in the public narrative.

Finally, customer quotes and case studies tend to emphasize successful deployments. They are valuable because they show use cases and buying reasons, but they do not reveal failed pilots, churned accounts, support disputes or regions where the proposition was weaker. The market-signal section intentionally includes G2 and Trustpilot caveats because a managed connectivity account should be judged by its failure handling as much as by its claimed network reach.

Public evidence used for this assessment

The company identity and legal status are supported by Companies House: https://find-and-update.company-information.service.gov.uk/company/06397669. The filing-history page supports the account filing dates and recent share-allotment activity: https://find-and-update.company-information.service.gov.uk/company/06397669/filing-history.

The hosted-account and portal surface is supported by the Infinity login route and the SIM management portal route: https://infinity.anynetiot.com/ and https://siam.eseye.com/. The pages do not reveal private customer data, but they support the existence of customer-facing account access.

The customer and partner evidence includes TELUS' announcement of TELUS Global Connect with Eseye, AWS' APN article on Eseye AnyNet Secure SIM and AWS IoT, Eseye's Costa Express case study and Eseye's InstaVolt case study: https://www.telus.com/en/about/news-and-events/media-releases/telus-makes-global-iot-connectivity-seamless-with-telus-global-connect, https://aws.amazon.com/blogs/apn/coarse-location-tracking-with-eseye-anynet-secure-sim-and-aws-iot/, https://www.eseye.com/resources/case-studies/costa-express/, and https://www.eseye.com/resources/case-studies/instavolt/.

The standards and regulatory context is supported by GSMA's SGP.32 v1.3 page, BEREC's call for input on M2M permanent roaming, and ITU's 2023 report on IoT/M2M roaming: https://www.gsma.com/solutions-and-impact/technologies/esim/gsma_resources/sgp-32-v1-3/, https://www.berec.europa.eu/en/public-consultations-calls-for-inputs/call-for-input-on-machine-to-machine-communications-and-permanent-roaming, and https://www.itu.int/dms_pub/itu-t/opb/tut/T-TUT-ROAMING-2023-1-PDF-E.pdf.

The network-resource view is supported by RIPE database lookups for Eseye and sampled route records, and by a PeeringDB API search that returned no matching public network or organization record for Eseye: https://apps.db.ripe.net/db-web-ui/query?searchtext=Eseye and https://www.peeringdb.com/api/net?name_search=Eseye.

The market-signal view is supported by G2, Trustpilot and Glassdoor pages: https://www.g2.com/products/eseye/reviews, https://www.trustpilot.com/review/eseye.com, and https://www.glassdoor.com/Overview/Working-at-Eseye-EI_IE1666719.11,16.htm. These pages are treated as signals, not as audited performance data.

What would change the judgement

The strongest positive change would be independent operating data: audited recurring revenue growth, gross margin, churn, active SIM or device counts, customer concentration, support response performance, regional availability by carrier, and evidence that SGP.32 deployments are moving from roadmap to production at scale. Eseye's public claims are credible enough to support the company-research thesis, but the investment or procurement judgement would become much stronger with hard operating metrics.

The second positive change would be more third-party customer proof from current deployments. TELUS and AWS are strong historical and partner evidence, and Costa Express is a clear use case. More recent named deployments with quantified fleet size, countries, incident performance and cost outcomes would help distinguish durable platform value from marketing reach. Evidence from customers using SGP.32 orchestration in production would be especially useful because that is where the current market narrative is moving.

The strongest negative change would be evidence that carrier partners restrict permanent roaming or localization in ways Eseye cannot solve economically. A second negative change would be repeated public complaints about platform instability, slow support or unresolved APN and profile issues. For a provider selling continuity, support and failure handling are not secondary. They are the product. If customers believe the platform is hard to use or the support model is too slow, the premium over direct carrier contracts becomes harder to defend.

Another negative change would be carrier disintermediation. If major operators make global IoT localization, eSIM profile orchestration and cloud integration simple enough inside their own portals, a specialist intermediary must either win through better independence or become a white-label supplier to those carriers. Eseye's Integra offer suggests it is aware of this path. The risk is that carriers keep more margin and control for themselves.

The final watchpoint is standards commoditization. SGP.32 is good for the market because it lowers friction for constrained IoT devices. But every successful standard also changes where value accumulates. Eseye's future value depends on turning standard capabilities into a trusted managed account, not merely explaining the standard.

Bottom line

Eseye's strongest public story is that global IoT connectivity is no longer a SIM procurement problem. It is an operations problem. Device makers and enterprises need to keep fleets alive across carriers, countries, technology sunsets, cloud environments and support queues. Eseye sells that continuity through AnyNet+, Infinity, Integra, Secure Cloud Connect and support services. The category and topic assignments are therefore justified: the company has customer-facing managed platform evidence, and the use case is inherently cross-border.

The thesis should not be overstated. Eseye is not proven by public evidence to be a large self-owned network operator. The more accurate reading is that it is a managed IoT connectivity and orchestration company whose value depends on carrier federation, platform control, device expertise and support. That is still an important account. In many IoT deployments, the commercial failure is not that data was unavailable in the abstract. It is that no one owned the boundary between the device, the carrier and the cloud when the device stopped talking. Eseye's business exists because that boundary is where the money is lost.