Contact us Partner portal

Choosing an IoT SIM Provider: What to Compare

Most IoT SIM offers look alike on a price list: a monthly fee, a data allowance and a list of countries. The differences that decide whether a fleet works, and what it costs to run, sit underneath. These are the questions worth asking any provider, including us.

IoT & Mobile Data

The questions that separate providers

Question Why it matters What a good answer looks like
How many networks can each SIM use, and where? A single-network SIM fails wherever that network is weak or down More than one network in each country, including all four in the UK
Who decides which network a SIM uses? Steering decides behaviour at the edge of coverage and during outages A steering policy you can set per fleet, not a fixed preference
Who runs the mobile core? The core sets addressing, policy and how fast changes happen A provider that runs its own core can change these itself, without waiting on a carrier
What addressing is available? Remote access, polling and firewalling all depend on it Static or dynamic, private or public, per fleet
How does traffic reach my systems? Devices on the open internet are exposed and hard to reach Private delivery by IPsec, cloud interconnect, MPLS or L2TP
How is data charged? Per-SIM allowances waste data on quiet devices and overcharge busy ones Allowances per SIM or pooled across the fleet
Can I manage SIMs myself? Activation, suspension and usage checks happen daily A portal and an API with the same controls
When does billing start? Fleets are shipped long before devices go live SIMs supplied inactive, charged only once active
Who answers when something breaks? IoT faults are rarely obvious Engineers who can see the core, the networks and the SIM

Coverage is about networks, not countries

A provider's country list says where a SIM can work; it does not say how well. What matters for a fixed device in a basement, a pole-mounted sensor or a vehicle crossing rural areas is how many networks the SIM can use at that spot, and what it does when the best one fails.

Ask how many networks each SIM can attach to in the countries you care about, and whether the SIM moves to another network on its own when one fails. For fixed installations, a site survey before deployment is worth more than any coverage map.

Who runs the core changes what you can ask for

Behind every IoT SIM is a mobile core: the system that authenticates the SIM, gives it an address and decides where its traffic goes. Some providers resell another operator's core; others run their own.

The difference shows when you need something specific: a fixed address, a private network into your cloud account, L2TP to your own LNS, a change of steering for one fleet. A provider that runs its own core can usually do these itself. One that resells may have to ask, if it can do them at all.

Plan the addressing before you buy

Decide early whether your systems need to reach devices, or only devices to reach your systems. Telemetry that only reports in can work on almost any SIM. Remote maintenance, polling and device management need each device reachable, which means a fixed address and a private path to it.

Changing addressing across a deployed fleet is far harder than choosing it at the start. Our guides on private APNs and on static, private or outbound access cover the trade-offs.

Cost is the fleet, not the SIM

Per-SIM prices hide the real cost. A fleet's data use is uneven: most devices send a little, a few send a lot. With per-SIM allowances you pay for unused data on the quiet ones and overage on the busy ones. A pooled allowance across the fleet usually costs less for the same use.

Count the operating cost too: how long it takes to activate, suspend or investigate a SIM, and whether that can be automated through an API. Our guide to estimating IoT data usage helps size the allowance.

How Netavo answers these questions

Question Netavo
Networks All four UK networks on one SIM, and more than one network in countries around the world
Steering Policy set for each fleet
Mobile core Our own
Addressing Static or dynamic, private or public
Private delivery IPsec, cloud interconnect into AWS or Azure, corporate MPLS WAN, or L2TP to your LNS
Data Allowances per SIM or pooled across a fleet
Management Portal and API, with activation, suspension and usage reporting
Billing SIMs supplied inactive and charged once in service

Common questions

What should I compare when choosing an IoT SIM provider?

Compare how many networks each SIM can use and how it moves between them, who runs the mobile core, the addressing and private access available, whether data can be pooled, and whether SIMs can be managed by API.

Is a multi-network IoT SIM better than a single-network SIM?

For most fleets, yes. A multi-network SIM can use another network where one is weak or unavailable, which a single-network SIM cannot.

Why does it matter who runs the mobile core?

The core sets each SIM's address, policy and traffic path. A provider running its own core can usually provide fixed addresses, private networks and custom delivery itself.

Are pooled data plans cheaper for IoT fleets?

Usually. Data use across a fleet is uneven, so a pooled allowance avoids paying for unused data on quiet devices and overage on busy ones.

Compare us against your shortlist

Tell us about the fleet, where it operates and how your systems need to reach it. We will answer each of these questions for your case.

Work with us →

Chris Byrd

CTO, Netavo Global Data Services Ltd

Chris leads Netavo's engineering: the AS208802 network, its broadband and BNG platforms, and the mobile core behind its IoT SIMs.

Chris Byrd on LinkedIn