Launch plans and connect devices without building a core network

Data platform and IoT deals usually run on a monthly commitment. We size it with you in the quote.

Devices can use SGP.32 (IoT) eSIM alongside multi-IMSI profiles on one platform, managed by API or portal. Installed SGP.02 bases stay on their generation and cannot move to SGP.32 over the air, so the hardware cycle decides when a fleet moves: SGP.32-capable modules for new builds, existing SGP.02 units until they retire. The eIM, which selects profiles for the fleet, can be run by us, by a local operator or by you, depending on the project. SGP.32 for IoT devices covers which fleets qualify.

It replaces the core network and BSS work behind your brand: subscriber records, SIM and eSIM lifecycle, plan and speed templates, and usage reporting. You still own the product, the pricing and customer support.

Multi-IMSI works with ordinary SIMs and switches IMSI profiles as a device moves between networks; eSIM needs an eUICC and lets you change the operator profile over the air. Many fleets use both: multi-IMSI on lower-cost hardware for wide coverage, eSIM where the device is designed for it. Multi-IMSI vs eUICC compares the two.

Monthly data per device, average and peak, how often firmware updates ship, whether the device stays local or roams, and how long it must run on a battery. The data usage estimator turns a usage profile into GB; the battery tool shows what the radio costs per report.

The IMEI/TAC, the bands the radio supports, whether it has an eUICC (EID), how firmware updates are delivered and where the device will operate. Four numbers: IMSI, ICCID, IMEI, MSISDN explains which identifier answers which question, and the rest is confirmed in the quote against the destination you name.

Number and IMSI ranges, plan templates and the API connection come first, then a pilot group of SIMs or eSIMs, then production with usage reporting in your own systems. Scale by group rather than by SIM, so plans, tariffs and reporting stay manageable as the base grows.

We do not promise a fixed lead time. Number and IMSI ranges, plan templates and the API connection come first, then a pilot group, so the timeline depends on your project. Your quote sets it out.

Decide early whether each device should stay on a roaming profile or switch to a local one, because the choice drives both cost and the rules that apply. Home routing and local breakout explains the path each takes, and the multi-IMSI explainer covers how the switch works on the SIM.