Aeris Adds SGP.32 IoT eSIM Support as Satellite Fallback Reaches 3GPP Standards

Multi-bearer connectivity gets closer to single-SKU global deployments

Aeris launched its eSIM Orchestrator with SGP.32 IoT eSIM specification support across 30 mobile network operators, enabling remote profile management for global IoT devices through a single hardware design. The platform supports SGP.02 M2M, SGP.22 consumer eSIM, and the newer SGP.32 IoT standard, which is designed for remote provisioning rather than relying on older M2M or consumer models.

At the same time, floLIVE and Skylo Technologies announced integrated cellular-and-satellite IoT service for Brazil using 3GPP Release 17 NB-IoT waveforms over satellite, reportedly without dedicated satellite terminals or hardware redesigns. The service uses standard 4G/5G IoT modems with software-enabled satellite fallback.

The strategic pattern: connectivity management is shifting toward remotely reconfigurable profiles and multi-bearer architectures that fail over between terrestrial cellular and satellite without field replacement.

SGP.32 reduces regional inventory and carrier lock-in costs

Aeris competes with Eseye, KORE, Wireless Logic, floLIVE, 1GLOBAL, and Transatel, plus direct operator-managed eSIM platforms. SGP.32 matters because it treats IoT devices as remotely manageable endpoints rather than forcing them into consumer or legacy M2M provisioning workflows.

Global OEMs can ship one hardware SKU and change operator profiles remotely, reducing regional inventory, field replacement, and carrier lock-in costs. A manufacturer deploying asset trackers across Brazil, Germany, and India can switch carriers per country without stocking separate SIM versions or dispatching technicians.

The limitation: Aeris disclosed the 30-operator footprint but provided no pricing, deployment volume, measured profile-switching time, or customer count. Procurement teams should compare the operator list with actual deployment countries, test profile-switching workflows, and clarify orchestration fees, minimum commitments, support for private networks, and exit portability. The concrete evidence is standards support and integration breadth—not demonstrated cost savings.

Satellite fallback hits 3GPP standards but lacks battery and pricing data

The floLIVE and Skylo announcement targets Brazil initially. The approach competes with terrestrial-only NB-IoT and LTE-M deployments, private 5G for managed industrial sites, and satellite providers requiring dedicated terminals. Its differentiator is software-enabled satellite fallback through existing cellular device designs.

Enterprises deploying trackers, utility sensors, agricultural equipment, environmental monitors, and logistics assets in areas with intermittent cellular coverage could reduce hardware SKU complexity and avoid separate satellite terminals. A fleet-tracking provider operating in remote regions could use the same device for urban São Paulo and rural Amazonas, failing over to satellite when terrestrial networks drop.

The risk: no quantified battery-life impact, satellite availability percentage, device certification list, or recurring connectivity price. Buyers should verify actual satellite latency, power consumption, roaming terms, service-level commitments, and whether all target devices support the required Release 17 modem features. The standards-based architecture is credible; the commercial business case is unproven.

LoRaWAN automates provisioning as deployment base reaches 150 million devices

The LoRa Alliance reported 150 million deployed LoRaWAN devices, up 25 million in nine months, and released specifications TS014 and TS018 to automate device setup and provisioning. The specifications are intended to reduce manual provisioning work and improve deployment automation.

LoRaWAN competes with NB-IoT and LTE-M for low-power wide-area deployments; private 5G competes for higher-performance industrial connectivity. The deployment figure strengthens LoRaWAN's case for large sensor estates where battery life, low bandwidth, and broad-area coverage matter more than throughput. Automated provisioning could lower installation labor and operational expense for utilities, smart buildings, agriculture, and environmental monitoring.

Buyers should assess whether vendor platforms support TS014/TS018 natively or require custom integration. The announcement does not quantify installation-hour savings, certification costs, device failure rates, or the geographic distribution of the 150 million devices. The headline adoption number should not be treated as proof of local ecosystem depth.

What to watch

Evaluate SGP.32 support in global IoT connectivity-management procurements now. Ask satellite-IoT vendors for Release 17 device compatibility, pricing, battery data, and service-level terms before committing budget.

The Thread Group reportedly approved an expansion toward sub-GHz frequencies for commercial and industrial IoT, which would put Thread closer to use cases traditionally served by sub-GHz proprietary mesh, Zigbee variants, Wi-SUN, and LoRaWAN. However, the available report provides no final specification number, certification schedule, supported frequency bands, vendor chipset list, range benchmark, or enterprise deployment count. Track it as a standards roadmap item, not a purchasing signal.

The main competitive shift is connectivity moving toward multi-bearer architectures—terrestrial cellular plus satellite—and remotely managed eSIM profiles, while LoRaWAN addresses deployment labor through provisioning automation. The gap remains pricing, battery impact, and measured performance data.