Fleet-wide eSIM control at any scale
Managing eSIM connectivity across a large IoT fleet is an operational problem, not just a technical one. Individual profile operations that are trivial for a handful of devices become a full-time job when you have tens of thousands of endpoints across multiple operators and regions.
eSIM IoT Manager is built around fleet-first operations. Every action that can be applied to one device can be applied to your entire fleet, to a filtered segment, or to any custom group you define.
Fleet organisation
Devices in eSIM IoT Manager are organised into groups that map to how your business actually operates:
- By region or country – for multi-jurisdiction deployments with different operator and compliance requirements
- By project or customer – for teams managing eSIM on behalf of multiple end customers
- By device type – different operational policies for sensors vs gateways vs trackers
- By RSP standard – separate management contexts for SGP.02, SGP.22, and SGP.32 devices where required
- By operator – manage the commercial relationship with each network alongside the technical profile operations
Bulk operations
Fleet operations in eSIM IoT Manager run in bulk by default. Select a device group, define the action, set any guardrails, and execute. The platform handles batching, rate limiting, and error handling automatically.
Operations available at fleet level include profile activation and switching, network policy updates, connectivity suspension and reactivation, lifecycle state transitions, and alert rule changes.
Fleet health monitoring
The fleet dashboard surfaces health signals across your entire estate in real time. At-a-glance metrics include devices with active connectivity, devices with stale last-seen timestamps, devices in failed provisioning state, and devices approaching profile expiry. Filterable by any group dimension.
Policy-based automation for fleet operations
Rather than manually managing each connectivity event, eSIM IoT Manager allows you to define fleet-wide policies that run automatically:
- If a device has no connectivity for N hours, trigger an automatic network switch to the fallback profile
- If a device enters a new geographic region, evaluate whether a local operator profile would reduce data costs
- If a profile is within 30 days of expiry, raise an alert and queue a renewal operation
- If a bulk operation produces more than X% failures, pause and alert before continuing