When deploying IoT devices across multiple countries, one of the most important connectivity decisions is whether to use roaming or local connectivity.
This choice affects:
- connectivity costs
- latency and routing performance
- operational complexity
- reliability and resilience
- long-term deployment flexibility
Understanding the trade-offs helps IoT builders design architectures that align with deployment scale, geography, and commercial requirements.
Understanding Roaming vs Local Connectivity
Roaming Architecture
How It Works
A device uses a SIM from a single “home” operator.
Example:
A Vodafone UK SIM deployed in Germany connects to Deutsche Telekom through a roaming agreement.
Data Routing Example
A device in Germany using a Vodafone UK SIM sends data to a backend hosted in London.
Roaming path:
- Device → Deutsche Telekom Germany (visited network)
- Deutsche Telekom → Vodafone UK (home operator)
- Vodafone UK → Enterprise backend in London
Key Point
Even though the device is physically in Germany, traffic routes through the home operator before reaching the application backend.
Local Connectivity Architecture
How It Works
Devices use local operator connectivity in each deployment country.
Example:
- Germany: Deutsche Telekom SIM or eSIM profile
- France: Orange France profile
- UK: Vodafone UK profile
Data Routing Example
A device in Germany with a Deutsche Telekom profile sends data directly to a London backend.
Local path:
- Device → Deutsche Telekom Germany
- Deutsche Telekom → Internet → Enterprise backend in London
Key Point
Traffic routes directly from the local operator to the destination without transiting through 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.
Typical Wholesale Roaming Rates
| Region | Typical Wholesale Rate |
|---|---|
| Europe | £0.05-£0.20/MB |
| North America | £0.10-£0.40/MB |
| Asia-Pacific | £0.15-£0.60/MB |
| Africa | £0.30-£1.50/MB |
| Middle East | £0.20-£1.00/MB |
Typical Enterprise Roaming Pricing
Retail roaming pricing commonly includes a 50-200% markup over wholesale rates.
Example:
- Wholesale rate: £0.20/MB
- Enterprise rate: £0.40/MB
Example Deployment Cost
10,000 devices in Africa
20 MB per month per device
Roaming cost calculation:
20 MB × 10,000 × £0.80/MB = £160,000/month
Annual cost:
£1,920,000/year
Local Connectivity Costs
With local connectivity, devices operate as domestic subscribers rather than roaming devices.
Typical Local Data Rates
| Region | Typical Local Rate |
|---|---|
| Europe | £0.03-£0.10/MB |
| North America | £0.05-£0.15/MB |
| Asia-Pacific | £0.05-£0.20/MB |
| Africa | £0.10-£0.40/MB |
| Middle East | £0.08-£0.30/MB |
Same Deployment with Local Connectivity
10,000 devices in Africa
20 MB per month per device
20 MB × 10,000 × £0.20/MB = £40,000/month
Annual cost:
£480,000/year
Annual Savings
£1,440,000/year
A 75% reduction versus roaming.
Regional Cost Variability
Regions Where Roaming Is Commercially Viable
Europe
EU roaming regulation has significantly reduced wholesale roaming costs.
Typical rates often sit between:
£0.05-£0.10/MB
Result
For many European deployments, roaming can be commercially acceptable compared with local provisioning.
Regions Where Local Connectivity Is Usually Preferred
Africa, Middle East, and Parts of Asia
Roaming costs are often substantially higher due to:
- limited competition
- lack of roaming regulation
- higher wholesale settlement pricing
Roaming can be 3-10× more expensive than local connectivity.
Example: Nigeria
10,000 devices
50 MB per month per device
| Connectivity Model | Cost |
|---|---|
| Roaming | £6,000,000/year |
| Local | £900,000/year |
Annual Savings
£5,100,000/year
eSIM ROI Example
eSIM allows remote provisioning of local operator profiles without replacing physical SIMs.
Example
eSIM hardware premium
£3 per device × 10,000 devices = £30,000
Annual savings from local connectivity
£5,100,000
Payback Period
Approximately 2 days.
For large-scale global deployments, eSIM economics can become compelling very quickly.
Performance Comparison
Latency
Roaming Latency
Roaming adds additional routing steps through the home operator.
Example
Device in Kenya with UK-based roaming SIM.
Routing path:
- Device → Safaricom Kenya
- Safaricom → Vodafone UK
- Vodafone UK → Backend
Typical Latency
| Component | Latency |
|---|---|
| Kenya to UK roaming link | 80-120 ms |
| UK internal routing | 20-40 ms |
| Total | 100-160 ms |
Local Connectivity Latency
With local connectivity, traffic routes directly from the local operator.
Typical Latency
| Component | Latency |
|---|---|
| Kenya to UK direct internet routing | 80-120 ms |
| Total | 80-120 ms |
Typical Improvement
20-40 ms lower latency.
When Latency Matters
Latency is particularly important for:
- payment processing
- real-time telematics
- interactive command and control systems
- live video applications
Latency is less important for:
- periodic sensor readings
- batch uploads
- non-real-time environmental monitoring
Throughput Comparison
Roaming Throughput
Roaming traffic may be subject to policy restrictions or throttling.
Typical throughput:
1-5 Mbps
This is generally sufficient for standard IoT workloads.
Local Connectivity Throughput
Local subscribers typically receive full network capability.
Typical throughput:
- LTE: 10-100 Mbps
- 5G: 100+ Mbps
Best Fit
High-throughput applications such as:
- video surveillance
- dashcams
- firmware updates
- edge AI uploads
usually benefit from local connectivity.
Reliability and Resilience
Roaming Reliability Dependencies
Roaming depends on multiple systems operating correctly:
- Visited network availability
- Home network availability
- Active roaming agreements
- International interconnect availability
Potential Failure Modes
Home Network Failure
The visited network may still be available, but devices cannot authenticate.
Roaming Agreement Termination
The visited operator may stop accepting roaming registrations.
International Link Failure
Authentication traffic cannot reach the home operator.
Result
Roaming introduces multiple dependency layers and additional points of failure.
Local Connectivity Reliability
Local connectivity has a simpler dependency model.
Required Components
- Local network availability
That is typically the only dependency.
Result
Fewer architectural dependencies and reduced operational risk.
Multi-Network Resilience
Roaming with Multi-Network SIMs
Some roaming solutions provide multiple operator identities or roaming relationships.
Example:
- Vodafone UK
- AT&T USA
- Telstra Australia
If one roaming relationship fails, another may still function.
Local Connectivity with eSIM
eSIM enables multiple local operator profiles within each country.
Example:
- MTN Nigeria
- Airtel Nigeria
- Glo Nigeria
If one operator experiences issues, devices can switch locally.
Result
This approach combines:
- local routing efficiency
- lower costs
- local resilience
- operational flexibility
Operational Complexity
Roaming Advantages
Roaming deployments are operationally simple.
Benefits
- single operator relationship
- single billing relationship
- one SIM SKU globally
- simplified logistics
- minimal provisioning overhead
Best Fit
- small deployments
- limited country coverage
- short deployment lifecycles
- organisations without dedicated connectivity teams
Local Connectivity Challenges
Traditional local SIM strategies introduce operational complexity.
Challenges
- multiple operator contracts
- regional procurement coordination
- country-specific provisioning
- inventory management
How eSIM Changes the Model
eSIM significantly reduces local connectivity complexity.
Benefits
- one hardware SKU globally
- remote profile provisioning
- dynamic operator selection
- easier deployment scaling
Trade-Off
Enterprises still need a connectivity management strategy and operational governance.
Hybrid Connectivity Models
Many large deployments use hybrid architectures.
Example Strategy
Europe
Use roaming where regulated pricing makes roaming commercially viable.
Africa and Middle East
Use local profiles where roaming costs are substantially higher.
Benefits
- simplified operations in low-cost roaming regions
- lower costs in high-cost roaming regions
- balanced operational model
Decision Framework
Choose Roaming When
- deployment is under 5,000 devices
- operating in fewer than 10 countries
- data usage is low
- deployment is concentrated in Europe or North America
- operational simplicity is the priority
- lifecycle is relatively short
Choose Local Connectivity When
- deployment exceeds 10,000 devices
- operating across many countries
- data usage is moderate or high
- deployment includes Africa or Middle East regions
- latency and routing performance matter
- deployment lifecycle exceeds 5-10 years
- eSIM provisioning is available
Choose a Hybrid Model When
- deployment regions have mixed roaming economics
- rollout is phased over time
- operational flexibility is important
- resilience and cost optimisation both matter
Real-World Examples: Smart Meter Deployment
200,000 devices across Europe and Africa
Initial roaming model
Annual cost:
£5,400,000
Migrated to local eSIM provisioning
Annual cost:
£1,200,000
Savings
£4,200,000/year
Payback on eSIM investment occurred in under two months.
Global Asset Tracking Deployment
15,000 trackers across 40 countries
Hybrid approach
- roaming in Europe and North America
- local connectivity in Asia, Africa, and Middle East
Savings
£3,636,000/year versus a pure roaming strategy.
Vehicle Telematics Deployment
5,000 vehicles across UK and France
EU roaming costs remained commercially acceptable.
Decision
Roaming was retained because:
- deployment geography was limited
- operational simplicity outweighed optimisation gains
- roaming economics were manageable
How OV Supports Global IoT Connectivity
OV supports roaming, local, and hybrid connectivity architectures depending on deployment requirements.
Global Connectivity Infrastructure
- coverage across 180+ countries
- access to 600+ networks
- multi-network resilience
- Multi-IMSI connectivity architecture
OV ONE Platform
OV ONE gives teams visibility and control across global IoT deployments through a single platform with API-first integration workflows.
eSIM and Remote Provisioning
OV supports eUICC and SGP.32-ready architectures for remote profile provisioning and flexible global deployment models.
Performance and Control
OV supports:
- local breakout architectures where appropriate
- multi-network resilience
- per-country connectivity optimisation
- real-time monitoring and SIM lifecycle management through OV ONE
For global IoT deployments, the best architecture is rarely universal. The right decision depends on deployment geography, scale, data consumption, operational maturity, and lifecycle expectations. The most effective strategies balance cost, performance, reliability, and operational simplicity based on the realities of the deployment environment.
