Choosing an IoT connectivity provider comes down to twelve questions, and most of them are about what happens in year three rather than on launch day. Who covers your devices where they actually sit, whether the SIM can change networks without a truck roll, how the bill behaves when one modem misbehaves, what the management platform lets your team do without calling anyone, and what it costs to leave. Providers answer those questions very differently depending on which kind of company they are: a carrier with its own network, a managed specialist that rides many networks, or a solution provider that sells connectivity inside a finished outcome. This checklist sets out the questions, what a good answer sounds like, and which providers in our directory tend to answer each one well.
What does an IoT connectivity provider actually sell?
An IoT connectivity provider sells three things bundled together: network access for a fleet of SIMs, a platform to manage those SIMs, and a commercial model for the data they use. The access can come from the provider's own towers or from agreements with many carriers. The platform decides how much of the fleet your team can run itself. The commercial model decides whether one chatty device costs you a rounding error or a quarter's savings.
The companies in this market sort into three kinds, the same three paths our ranked guide to IoT connectivity providers uses. Carriers such as AT&T, Verizon and T-Mobile for Business sell access on their own networks with their own management platforms. Managed specialists such as KORE, Soracom, Eseye, Globalgig and Data2Go Wireless own no towers and sell multi network reach, the management layer and one point of accountability. Solution providers such as EPIC iO and For2Fi sell a working outcome, a monitored site or a branch that stays online, with the wireless connection inside it.
| Carrier direct | Managed specialist | Solution led | |
|---|---|---|---|
| What you buy | SIMs on one network, rate plans, a platform | SIMs across many networks, a platform, support | A connected outcome per site or device |
| Coverage model | One network at home, roaming abroad | Several networks per country, switchable | Whatever the solution needs |
| Pricing shape | Per SIM rate plans tiered by volume | Per SIM plus platform, often pooled | One managed fee per site or unit |
| Who owns a ticket | The carrier, for its network | The specialist, across every network | The provider, for the whole outcome |
| Fits best | Large, mostly domestic fleets | Multi network or multi country fleets | Buyers with a problem, not SIMs, to solve |
Coverage: will the devices connect where they actually sit?
Coverage is the first question because no platform or price fixes a device that cannot attach. A good provider tests against your real device locations, on the radio technology your device uses, and tells you which network each site will land on. A coverage map for handsets is not an answer; a site list run against the networks your module supports is.
1. Which networks will each device use, at each location? Ask for a coverage check against your actual address list or route, not the national map. A carrier answers for its own network and its roaming partners. A managed specialist should name the networks it holds in each country and say whether a SIM can use more than one of them. Where the answer is one network, find out what happens at the sites that network covers poorly, because those are the sites that generate the service calls.
2. Is the coverage for the radio your device actually uses? Sensors and meters often run on the low power networks, LTE-M and NB-IoT, and those networks do not reach everywhere that ordinary LTE does. AT&T, for example, documents that its LTE-M devices are deployed and managed through its Control Center platform and describes LTE-M as available on its US network and with roaming partners in select countries. Confirm coverage for the exact technology, and confirm the fallback the device takes when that technology is missing.
3. How does the provider handle countries that restrict permanent roaming? A SIM that roams indefinitely in another country is fine in many markets and unwelcome in others, where regulators or local operators expect devices to connect on local terms. Vodafone describes its Global SIM offer as converting a roaming SIM into a local one in country for exactly this reason, KORE sells local carrier SIMs for markets that require them, and Eseye positions its multi network SIM as a way to localize devices rather than roam permanently. If your devices will live outside the US, ask which countries need a local profile and who arranges it.
eSIM and network switching: can you change networks without touching the device?
The SIM decides how much leverage you keep after signing. A SIM welded to one carrier makes every future change a truck roll, while an eSIM or multi network SIM lets the network change over the air. Ask what the SIM can do today, not what the roadmap promises.
4. Can the SIM switch networks, and who controls the switch? There are two mechanisms worth telling apart. Multi IMSI SIMs hold several network identities and move between them when one is unreachable; KORE describes its OmniSIM this way, and Eseye says its AnyNet SIM rotates between profiles to find coverage. Remote SIM provisioning downloads a new operator profile over the air, which lets the fleet change carriers without a field visit. Ask whether switching happens automatically, on your instruction, or only on the provider's, and whether the profiles on the SIM are the provider's alone.
5. Does the eSIM follow the current GSMA IoT standard? The GSMA's SGP.32 specification covers remote provisioning for devices that are constrained by network or user interface, which is most IoT hardware. Eseye and Globalgig both state support for it. A provider that supports the standard makes it easier to bring in another operator's profile later; a proprietary scheme can work well and still tie the fleet to one company. Ask which approach the SIM uses and what moving to another provider would require at the device.
Pricing: how will the bill behave across a real fleet?
IoT connectivity is almost always priced per SIM per month plus a platform layer, and the shape of the plan matters more than the headline rate. Pooled data, pay per use and fixed bundles each suit different traffic. Price the fleet you will actually run, including the devices that misbehave.
6. Is the data pooled, per device, or pay per use? Pooled plans let the fleet draw from one shared allowance, so a device that sends more than expected is absorbed by the ones that send less. Data2Go Wireless describes dynamic and static pooled plans alongside cost per megabyte billing, T-Mobile lists recurring, prepaid, pooled, location and time based billing models for transportation IoT, and Soracom sells pay as you go plans with no minimums on its self serve side. Run your expected usage per device through each structure and look at the total for the month, not the per SIM figure.
7. What does a misbehaving device cost, and how fast will you know? One modem stuck in a reconnect loop can generate an overage bill that erases a quarter's savings on a per device plan. Ask what the platform does about it. Verizon says ThingSpace can flag an overly chatty device and either suspend it or change its service plan, and Globalgig lists usage anomaly detection among its SIM controls. You want alerts by threshold, automatic action you configure in advance, and an overage rate written into the contract.
8. What sits outside the per SIM number? Platform fees, activation charges, SIM hardware, static IP addresses, private network connections and inactive SIM fees can all appear on the bill separately. Ask for every line item that applies to your fleet, and ask what an inactive or suspended SIM costs per month, because fleets accumulate devices in storage, in repair and in transit. Our IoT and mobility category hub sets out how pricing behaves across this market.
Platform and security: what can your team do without calling anyone?
The management platform is where you will spend your time after launch. A good one lets your team activate, suspend and diagnose SIMs in bulk, set usage rules and plug into your own systems through an API. Security controls at the SIM level are part of the same question.
9. Can your team run the fleet from the platform and the API? Verizon describes ThingSpace Manage as letting administrators activate, suspend, restore and deactivate service, swap SIMs and monitor usage in near real time, with APIs to connect it to enterprise systems. Globalgig's Orchestra portal and Data2Go's Traverse platform describe similar activation, suspension and usage controls with API access. Ask for a demo account, run the five tasks your team will do most often, and check whether bulk actions work at the size of your fleet.
10. What security controls apply at the SIM and network level? Ask about private networking (a private APN or VPN so device traffic never crosses the public internet), static addressing where your application needs it, and controls that stop a stolen SIM being used in another device. Globalgig lists geo fencing and IMEI locking among its SIM controls and offers private networks with static public IPs. A provider that cannot describe how a lost SIM is detected and shut off has not thought about the problem your security team will raise first.
Support and the contract: what happens in year three?
IoT deployments outlive their first contract, and frequently the ownership of the provider that signed it. The last two questions are about the relationship after launch: who answers when devices drop off, and what you can take with you when the term ends.
11. Who owns the ticket, and what is included in support? On a carrier contract the carrier answers for its network; on a managed contract the specialist should answer across every network it uses. Some providers sell tiers: Globalgig, for example, describes SIM only, SIM plus hardware, and a full managed service with round the clock network operations monitoring. Ask which tier the quote assumes, what response times are written down, and whether device certification help is included, since a carrier such as AT&T keeps a catalog of certified modules through its IoT Accelerator program and a new device may need to pass it.
12. What does it cost to leave, or to change the mix? Ask for the term, the volume commitment and what happens if you fall short of it, the renewal price cap, and whether SIMs can move to another provider without being replaced. Month to month terms exist at the edges of this market; For2Fi offers month to month contracts on its wireless connectivity for sites. Write down the exit before you need it, because a fleet of ten thousand SIMs is very expensive to swap.
Matching the checklist to provider types
The twelve questions point to different providers depending on your fleet. The table below maps common situations to the kind of provider that usually answers them best, with providers from our directory as examples. It is a starting shortlist, not a ranking; the ranking and our reasoning sit in our evaluation of the best IoT connectivity providers.
| Your situation | Start with | Examples | Watch for |
|---|---|---|---|
| Large fleet, mostly in the US | Carrier direct | AT&T, Verizon, T-Mobile for Business | One network's dead zones |
| Devices shipped to many countries | Managed specialist with eSIM | Eseye, KORE, Vodafone Business | Permanent roaming rules |
| Product team building and testing | Self serve specialist | Soracom | Support tier at scale |
| Hundreds of US devices on mixed carriers | Pooled multi carrier plans | Data2Go Wireless, KORE | Inactive SIM fees |
| Mixed estate of SIMs, sites and countries | Managed aggregator | Globalgig | Which tier the quote assumes |
| A site or outcome, not a SIM fleet | Solution led | EPIC iO, For2Fi | Per site pricing at scale |
Two patterns are worth calling out. A fleet that starts domestic and later ships abroad often outgrows a single carrier, so ask the carrier about its global options, and ask a specialist the same questions, before the first international order rather than after. And site connectivity is a different purchase from device connectivity: a branch that needs wireless failover alongside its wired circuit is usually better served by a managed failover provider such as EPIC iO or For2Fi, or by a carrier's fixed wireless service like the one on our Verizon business internet pricing page, than by an IoT SIM platform.
Mistakes to avoid when choosing an IoT connectivity provider
Most expensive mistakes in this category come from buying for launch day. These are the ones that recur.
Choosing on the per SIM rate alone. The rate is one line; pooling, overage, platform and inactive SIM fees decide the bill, so compare the monthly total for your real fleet.
Testing coverage with a phone. A handset on ordinary LTE says little about a meter on NB-IoT in a basement. Test with the module and antenna you will ship, at the worst sites, not the best.
Buying 5G for sensor traffic. Most IoT devices need far less network than the marketing suggests, and the low power networks cost less and save battery. Match the radio to the device's job.
Ignoring the exit. A SIM that cannot change networks over the air turns the provider into a permanent partner. Ask how you would leave before you sign, and get the answer in the contract.
Splitting the WAN and the devices without a plan. Where devices sit behind a branch network, the SD-WAN buying guide and our map of SD-WAN companies cover the circuits and overlay those devices depend on; decide who owns the problem when a device drops because the site did.
How to run the evaluation
A clean evaluation takes a few weeks and needs a written brief more than a long vendor list. Put the brief together first, then send the same twelve questions to two or three providers of at least two kinds.
- Write the fleet down: device count now and in three years, module and radio technology, data per device per month, locations or countries, and how long the devices stay in the field.
- Shortlist across kinds: at least one carrier and one managed specialist, plus a solution provider if what you need is a site outcome rather than SIMs.
- Send the same twelve questions to each, and ask for the answers in writing alongside the quote.
- Test SIMs from the top two in real devices at your hardest locations for a few weeks.
- Compare the monthly total for the whole fleet, the platform demo, and the exit terms side by side, then negotiate.
A Technology Advisor from our team takes your written fleet brief to carriers, managed specialists and solution providers at once and pulls the quotes side by side, free. You keep the decision and sign directly with the provider you choose.
Frequently asked questions
- What should I look for in an IoT connectivity provider?
- Coverage on the radio technology your devices use at the places they actually sit, a SIM that can change networks over the air, a pricing structure that absorbs a misbehaving device, a platform your team can run without calling anyone, and contract terms that let you leave. Ask every provider the same questions in writing and compare the monthly total for your real fleet rather than the per SIM rate.
- Is a carrier or a managed IoT provider better?
- A carrier usually suits a large fleet that lives mostly in one country on a network that covers it well, because the carrier offers volume pricing and its own platform. A managed specialist usually suits fleets that need more than one network for coverage, cross borders, or want one contract across carriers. Many fleets of real size use both, so get quotes from each kind before deciding.
- Do IoT devices need eSIM?
- Not always, but it is the main protection against being stuck with one network for the life of the device. An eSIM or multi network SIM lets the operator profile change over the air, so a coverage problem or a better commercial offer does not require replacing SIMs in the field. For devices that stay deployed for years, or ship to several countries, it is worth requiring.
- How is IoT connectivity priced?
- Almost always per SIM per month plus a platform layer, with the data either pooled across the fleet, charged per device, or charged per megabyte used. Platform fees, activation, static addresses and inactive SIM charges can sit outside the per SIM number. The fair comparison is the monthly total for your actual fleet under each provider's structure, including the cost of one device using far more data than planned.
- What contract terms matter most for IoT connectivity?
- The term length and volume commitment, the penalty for falling short of that commitment, the renewal price cap, the overage rate, and whether SIMs can move to another provider without being physically replaced. IoT devices often stay in the field longer than the first contract runs, so the renewal and exit terms usually matter more than the launch price.