Every MVNO is, underneath the brand, a buyer. Whatever the proposition looks like to its customers, somewhere beneath it sits a wholesale arrangement with one or more network operators, and the shape of that arrangement quietly determines most of what the MVNO can and cannot do: its margins, its coverage map, its provisioning speed, even which customer problems its support team can actually solve.
For consumer MVNOs the sourcing landscape is well documented. For IoT MVNOs, businesses building connectivity propositions for devices rather than people, the same landscape applies but the priorities invert. Voice bundles and handset subsidies stop mattering; multi-country coverage, SIM lifecycle automation, low-volume data economics and platform APIs become the entire game. This piece sets out the sourcing models available and the trade-offs each carries for an IoT proposition.
The three sourcing routes
Direct host operator agreement. The MVNO contracts directly with a mobile network operator for wholesale access to its network. This is the classic full MVNO route, and it comes in gradations: at the lighter end the MVNO rebrands the host’s service, while a full MVNO operates its own core network elements, issues its own SIMs and controls its own routing, buying little more than radio access from the host.
The trade-off is depth against weight. Direct agreements offer the best unit economics at scale and the most control, but they demand serious volume commitments, long negotiations, technical integration into operator systems and, for full MVNOs, real network engineering capability. They also bind the MVNO’s coverage to the host’s footprint, which for international IoT propositions means stacking multiple agreements or accepting the host’s roaming terms.
MVNE or enabler platforms. A Mobile Virtual Network Enabler sits between the operator and the MVNO, providing the technical machinery, provisioning, billing mediation, SIM management, sometimes core network functions, as a platform. The MVNO brings brand and customers; the enabler brings the plumbing.
This route compresses time to market dramatically and converts capital expenditure into a platform fee, which is why most new MVNOs start here. The costs are a permanent intermediary margin, dependence on the enabler’s roadmap, and a layer between the MVNO and the network that can slow diagnostics and limit differentiation. Two MVNOs on the same enabler can struggle to offer genuinely different products.
Aggregators and resale. At the lightest end, an MVNO-in-name resells an existing IoT connectivity provider’s service under wholesale terms, often with white-label options. Fastest of all to launch and lowest in commitment, with economics and capabilities that mirror whatever the upstream provider offers. For some propositions, particularly those where connectivity is an ingredient in a wider product rather than the product itself, this is the rational permanent choice rather than a stepping stone.
What changes when the MVNO is an IoT MVNO
The sourcing checklist for an IoT proposition differs from the consumer one in ways that reshape which route wins.
Coverage is multi-country by default. Devices ship internationally and stay deployed for years. A sourcing arrangement built on one national network’s footprint forces the roaming question immediately: on whose agreements, at what rates, and with what behaviour in markets that restrict permanent roaming. Wholesale partners with structurally global reach, such as access across 180+ countries and 600+ networks under one agreement, remove an entire category of contract stacking.
The unit economics are inverted. Consumer wholesale optimises for gigabytes per subscriber. IoT estates often run thousands of devices consuming megabytes each, which makes per-SIM platform fees, dormancy terms and pooled data mechanics far more consequential than headline per-GB rates. Wholesale terms designed for consumer volumes can be quietly ruinous for sensor-class deployments.
Automation is not optional. Provisioning ten thousand SIMs, suspending a customer’s estate for non-payment, or rotating devices through test, live and retired states cannot run through portals and spreadsheets. The wholesale layer must expose its full feature set through documented APIs, because the IoT MVNO’s own platform will be built on top of them. This is frequently the deciding criterion in practice, and the one hardest to retrofit.
Network behaviour is a product feature. For devices in the field, multi-network access through Multi-IMSI technology and non-steered network selection, attaching to the strongest available network rather than a fixed list, translates directly into the reliability statistics the MVNO’s customers experience. An IoT MVNO inherits the network behaviour of its wholesale layer, whatever its brand promises.
Choosing a route: a short decision framework
Three questions sort most cases.
Is connectivity your product or your ingredient? If connectivity itself is the proposition, with your own tariffs, your own platform and connectivity margins as the business model, the direct or MVNE routes justify their weight. If connectivity enables a wider product, a fleet platform, a safety service, a payments offering, wholesale resale from a capable provider usually delivers everything needed at a fraction of the operational load.
Where will your devices physically be? Single-market propositions can reasonably anchor on one host network. Anything international should weight global reach under a single agreement heavily, because every additional wholesale relationship multiplies integration, billing and support complexity.
What must you control to differentiate? List the capabilities your proposition genuinely depends on, network steering policy, private networking, billing granularity, provisioning speed, and trace each one to the layer that controls it under each sourcing model. Differentiation you cannot reach contractually does not exist.
A pattern worth naming: many successful IoT connectivity businesses run a hybrid, sourcing global wholesale access from one structural partner while holding a direct agreement in their single largest market. The complexity is real, but it concentrates negotiating effort where the volume justifies it.
Where an MNO partner fits
OV operates as a true IoT Mobile Network Operator, with direct integration into our own MNO core rather than reselling access from further up a chain. For MVNOs and wholesale partners, that position carries practical consequences: operator-level visibility and control over connections, coverage across 180+ countries and 600+ networks on a single agreement, and the OV ONE platform, built entirely in-house, with every feature exposed through documented APIs so partners can build their own propositions on top of it.
If you are building or rethinking an IoT MVNO proposition, the For MVNOs page sets out the partnership model, and our team will work through the sourcing economics against your real deployment profile.
Frequently asked questions
What is an IoT MVNO?
An IoT MVNO is a business that sells cellular connectivity for devices under its own brand without owning the radio networks involved, sourcing access wholesale from one or more operators or enablers. Compared with consumer MVNOs, the proposition centres on device estates: multi-country coverage, SIM lifecycle automation and data plans shaped for machines rather than people.
What is the difference between an MVNE and a host operator?
A host operator owns and runs the mobile network the MVNO’s traffic ultimately uses. An MVNE is an intermediary platform providing the technical and operational machinery, provisioning, billing, SIM management, that lets an MVNO operate without building those systems itself. Many MVNOs use both: a host for network access and an enabler for operations.
How much volume does a direct operator agreement require?
There is no universal threshold, but direct wholesale agreements are structured around volume commitments and meaningful integration effort, which is why they typically suit propositions with proven scale or strong funding. Enabler and resale routes exist precisely to make smaller and earlier-stage propositions viable.
Can an IoT MVNO offer global coverage from a single agreement?
Yes, by partnering with a wholesale provider whose own footprint is structurally global. OV provides access across 180+ countries and 600+ networks under one agreement, which lets a partner’s proposition follow its customers internationally without stacking per-country wholesale contracts.
