When deploying IoT devices across multiple countries, one of the most important connectivity decisions is whether to use roaming or local connectivity. The choice affects connectivity costs, latency and routing performance, operational complexity, reliability and resilience, and long-term deployment flexibility. Understanding the trade-offs helps IoT teams design architectures that align with deployment scale, geography, and commercial requirements.
Understanding Roaming vs Local Connectivity
Roaming architecture
A device uses a SIM from a single “home” operator. For example, a Vodafone UK SIM deployed in Germany connects to Deutsche Telekom through a roaming agreement.
Data routing. A device in Germany using a Vodafone UK SIM, sending data to a backend hosted in London, routes:
- Device to Deutsche Telekom Germany (visited network)
- Deutsche Telekom to Vodafone UK (home operator)
- Vodafone UK to the enterprise backend in London
Even though the device is physically in Germany, traffic routes through the home operator before reaching the application backend.
Local connectivity architecture
Devices use local operator connectivity in each deployment country, for example a Deutsche Telekom profile in Germany, Orange in France and Vodafone UK in the UK.
Data routing. A device in Germany with a Deutsche Telekom profile sending data to a London backend routes:
- Device to Deutsche Telekom Germany
- Deutsche Telekom to the internet to the enterprise backend in London
Traffic routes directly from the local operator to the destination without transiting a foreign home network.
Cost Comparison
Roaming data costs
Roaming introduces additional wholesale and retail charging layers. The home operator pays the visited network for usage, then applies margin before charging the enterprise customer.
Indicative wholesale roaming rates (illustrative industry ranges, not OV rates):
| Region | Indicative wholesale rate |
| Europe | £0.05 to £0.20/MB |
| North America | £0.10 to £0.40/MB |
| Asia-Pacific | £0.15 to £0.60/MB |
| Africa | £0.30 to £1.50/MB |
| Middle East | £0.20 to £1.00/MB |
Retail roaming pricing commonly carries a markup over wholesale. As an illustration, a £0.20/MB wholesale rate might reach the enterprise at around £0.40/MB.
Illustrative deployment cost. For 10,000 devices in Africa using 20 MB per month each, at roughly £0.80/MB, roaming costs about £160,000/month, or £1,920,000/year.
Local connectivity costs
With local connectivity, devices operate as domestic subscribers rather than roaming devices.
Indicative local data rates (illustrative industry ranges):
| Region | Indicative local rate |
| Europe | £0.03 to £0.10/MB |
| North America | £0.05 to £0.15/MB |
| Asia-Pacific | £0.05 to £0.20/MB |
| Africa | £0.10 to £0.40/MB |
| Middle East | £0.08 to £0.30/MB |
The same 10,000-device African deployment at roughly £0.20/MB costs about £40,000/month, or £480,000/year, an illustrative reduction of around 75% versus roaming.
Regional cost variability
In Europe, roaming regulation has reduced wholesale costs, often to around £0.05 to £0.10/MB, so roaming can be commercially acceptable compared with local provisioning. In Africa, the Middle East and parts of Asia, roaming costs are often substantially higher, due to limited competition, lack of roaming regulation and higher wholesale settlement pricing, and can run several times the cost of local connectivity.
Illustrative example, Nigeria. For 10,000 devices using 50 MB per month, a roaming model might cost on the order of £6M/year against roughly £900,000/year local, an indicative saving of around £5.1M/year.
eSIM ROI
eSIM allows remote provisioning of local operator profiles without replacing physical SIMs. Against an illustrative hardware premium of around £3 per device (£30,000 across 10,000 devices) and local-connectivity savings of the order shown above, payback can be very fast for large-scale global deployments.
Performance
Latency
Roaming adds routing steps through the home operator. A device in Kenya on a UK-based roaming SIM routes via Safaricom to Vodafone UK to the backend, with total latency typically around 100 to 160 ms. With local connectivity the same device routes directly, typically 80 to 120 ms, an improvement of roughly 20 to 40 ms.
Latency matters most for payment processing, real-time telematics, interactive command and control, and live video. It matters less for periodic sensor readings, batch uploads and non-real-time monitoring.
Throughput
Roaming traffic may be subject to policy restrictions or throttling, with throughput typically in the 1 to 5 Mbps range, which is generally sufficient for standard IoT workloads. Local subscribers typically receive full network capability, around 10 to 100 Mbps on LTE and 100+ Mbps on 5G. High-throughput applications such as video surveillance, dashcams, firmware updates and edge AI uploads usually benefit from local connectivity.
Reliability and Resilience
Roaming dependencies
Roaming depends on several systems operating correctly: visited network availability, home network availability, active roaming agreements and international interconnect availability. Failure modes include a home-network outage (the visited network is available but devices cannot authenticate), termination of a roaming agreement, and international link failure (authentication traffic cannot reach the home operator). Each adds a point of failure.
Local connectivity
Local connectivity has a simpler dependency model, typically just local network availability, which means fewer architectural dependencies and reduced operational risk.
Multi-network resilience
Some roaming solutions provide multiple operator identities, so if one roaming relationship fails another may still function. With eSIM, local connectivity can hold multiple local profiles in a country (for example MTN, Airtel and Glo in Nigeria), so devices can switch locally if one operator has issues. This combines local routing efficiency, lower cost, local resilience and operational flexibility.
Operational Complexity
Roaming
Roaming deployments are operationally simple: a single operator and billing relationship, one SIM SKU globally, simplified logistics and minimal provisioning overhead. That suits small deployments, limited country coverage, short lifecycles, and teams without dedicated connectivity resource.
Local connectivity
Traditional local SIM strategies add complexity: multiple operator contracts, regional procurement coordination, country-specific provisioning and inventory management.
How eSIM changes the model
eSIM reduces that complexity through one hardware SKU globally, remote profile provisioning, dynamic operator selection and easier scaling. The trade-off is that teams still need a connectivity management strategy and operational governance.
Hybrid Connectivity Models
Many large deployments use hybrid architectures: roaming where regulated pricing makes it viable (such as Europe), and local profiles where roaming costs are substantially higher (such as Africa and the Middle East). This balances simpler operations in low-cost roaming regions against lower costs in high-cost regions.
Decision Framework
Roaming tends to fit when the deployment is under about 5,000 devices, spans fewer than ten countries, uses low data volumes, is concentrated in Europe or North America, prioritises operational simplicity, or has a relatively short lifecycle.
Local connectivity tends to fit when the deployment exceeds about 10,000 devices, spans many countries, uses moderate or high data volumes, includes Africa or the Middle East, depends on latency and routing performance, runs for 5 to 10 years or more, or has eSIM provisioning available.
A hybrid model tends to fit
