Installing an eSIM on a phone is usually a personal decision. Choose a plan, download a profile, get online. Connecting an industrial sensor is a different proposition. That sensor may spend years inside equipment, operate without a screen and end up in a country its manufacturer never originally planned for.

Nobody wants to retrieve it just to change its mobile subscription.

This is where Aeris becomes interesting. The company operates in the less visible part of the connectivity business: helping enterprises, manufacturers and mobile operators connect devices, manage their subscriptions and keep those connections useful throughout a product’s life.

Its latest eSIM announcement puts that lifecycle question firmly at the centre.

What Aeris actually does

Aeris provides cellular IoT connectivity platforms and services. Its IoT Accelerator platform brings together subscription management, operator coordination, billing, automation and visibility across connected devices.

Think smart meters, medical equipment, industrial gateways, asset trackers and connected vehicles. These products have different data requirements, but share an uncomfortable dependency: when connectivity fails, the service built around them can fail too.

READ MORE: Aeris Expands IoT Platform with Global eSIM Orchestration and Operator Control

Aeris’s position strengthened considerably when it acquired Ericsson’s IoT Accelerator and Connected Vehicle Cloud businesses in March 2023. Ericsson confirmed the completed transaction, giving Aeris an established platform and operator relationships to build upon.

The distinction matters. Aeris works within an ecosystem of mobile operators and enterprise customers. Its proposition extends beyond supplying data: it provides infrastructure for administering connectivity across networks and markets.

The new eSIM chapter

On October 1, 2026, Aeris introduced its next-generation eSIM Orchestrator, previously called eSIM Hub. The launch adds support for GSMA’s SGP.32 specification, a Single SKU eSIM offering and an eSIM IoT Manager delivered as a managed service.

According to Aeris, IoT Accelerator now manages 110 million devices, with 44 million using eSIM. These are company-reported figures, but they indicate the scale at which the business is already operating.

The new orchestrator supports automated profile decisions driven by policies and events. Customers can use Aeris’s managed eIM or integrate alternatives from vendors including Thales, G+D, Kigen and IDEMIA.

In practical terms, an enterprise can establish rules around which operator profile a device uses and how profile operations should be handled. That is a substantial step beyond treating an embedded SIM as a component installed at the factory and forgotten.

The useful question is whether those rules work consistently when deployments become messy.

Why SGP.32 matters

An eSIM removes the need to physically replace a SIM when changing a subscription, provided the device and supporting infrastructure enable that operation. For IoT, however, removing the plastic is only the beginning.

Someone still needs to initiate downloads, enable profiles, monitor outcomes and recover devices when an operation fails.

The GSMA’s SGP.32 specification addresses remote provisioning and management for IoT devices with constrained network access or user interfaces. It introduces an architecture suited to devices that cannot rely on someone opening settings or scanning a QR code.

READ MORE: SGP.32 Goes Commercial: Soracom’s IoT eSIM Play

Aeris now supports SGP.32 alongside the older SGP.02 M2M and SGP.22 consumer specifications. That breadth matters because existing deployments do not disappear when a new standard arrives.

A manufacturer may have several generations of hardware in circulation. Replacing everything would be expensive, disruptive and often unnecessary. Managing the transition is part of the service buyers should expect.

Global hardware, local choices

Aeris’s Single SKU approach is intended to let manufacturers ship one device variant and assign appropriate local operator profiles after deployment.

Consider a company producing industrial monitoring equipment for several markets. Separate connectivity variants complicate stock allocation, testing and distribution. A common device design with remotely managed profiles offers a more flexible starting point.

That flexibility becomes more valuable over time. Devices change owners. Service requirements evolve. Network technologies are retired. Commercial agreements get renegotiated.

Still, remote profile management cannot remove every constraint. Hardware compatibility, supported radio bands, available operator profiles and commercial permissions remain decisive. A single product variant is an objective that requires careful engineering and partner coordination.

Buyers should ask what happens during a failed profile download, how a device retains a recovery path and which markets actually support the proposed configuration. “Global” needs a deployment-specific explanation.

Connectivity needs security

Aeris also offers IoT Watchtower, its network-based security service launched in February 2025. It combines visibility into device communications with policy enforcement, identifying suspicious behavior and allowing administrators to restrict traffic.

Aeris describes an agentless approach, which avoids installing additional security software on every endpoint.

For constrained equipment, that can be useful. A device sending small sensor readings may have neither the resources nor the update process to accommodate conventional endpoint tools.

But network visibility is one part of protection. Secure firmware, credentials, provisioning permissions and physical access still matter. Enterprises need someone responsible for investigating alerts and deciding how to respond.

READ MORE: eSIM Security Risks in Connected Devices Explained Clearly

Aeris’s proposition is most relevant when managing connectivity has become an operational task. A small deployment in one country may need a simpler service. Clearer public pricing and implementation detail would also make initial comparisons easier.

The commercial discussion should cover more than the data rate. Platform fees, profile operations, support, integration work and security services all affect the total cost. Buyers should also establish what they can export and how they would migrate later. An eSIM can make changing a network subscription easier; changing the platform that manages an entire deployment is a separate decision with its own consequences.

Conclusion

Aeris’s opportunity lies in making connectivity adaptable without making operations harder. Emnify’s API-based management and Soracom’s cloud integration and orchestration services show that competitors are addressing similar requirements, albeit through different platform approaches.

Reading their official documentation alongside GSMA’s standards makes the direction clear: eSIM is becoming infrastructure for managing connected products over time.

Aeris brings substantial scale and operator relationships to that contest. Its real advantage must show up in reliable profile operations, useful diagnostics and manageable costs. For enterprise buyers, the winning platform will be the one that keeps future connectivity choices practical after the hardware has shipped.