The IoT connectivity market uses a set of terms that are sometimes interchangeable, sometimes meaningfully different, and frequently used in ways that obscure rather than clarify what a provider actually offers. Connectivity provider, connectivity platform, MNO, MVNO, reseller, aggregator — these labels describe genuinely distinct things, and understanding the distinctions helps when evaluating options for a real deployment.
This article maps the IoT connectivity ecosystem clearly, explains what each type of provider can and cannot offer, and gives a practical framework for understanding where any given vendor sits in the stack.
The core infrastructure layer: MNOs
At the foundation of any mobile connectivity is a Mobile Network Operator. An MNO is an organisation that holds spectrum licences, owns physical network infrastructure — radio towers, base stations, core network systems — and operates the network that devices ultimately connect to. Every SIM card that sends data is, at some point in the chain, using an MNO’s network.
In the IoT context, a true IoT MNO is one that has built its infrastructure specifically around the requirements of connected devices: bilateral roaming agreements with operators in each country where devices will operate, support for IoT-specific radio technologies such as LTE-M and NB-IoT, and connectivity management platforms designed for large device fleets rather than individual consumers.
The key characteristic of working directly with an MNO is that the infrastructure your devices connect to and the organisation you have a commercial relationship with are the same entity. When something goes wrong, the MNO can investigate and resolve it within its own systems. When you need a custom commercial arrangement — a specific APN, a non-standard data pool, a network access policy — the MNO has the authority to implement it.
MVNOs: building on top of MNO infrastructure
A Mobile Virtual Network Operator purchases access to network capacity from one or more MNOs and resells that capacity to its own customers. MVNOs range from full MVNOs — which operate some of their own core network components and have meaningful technical control over the service to light MVNOs that are closer to a branded reseller of another operator’s service.
The IoT MVNO segment includes providers that have built sophisticated connectivity management platforms and multi-operator relationships, and whose customers experience a service that is practically comparable to working with an MNO directly. The gap between an MNO and a well-capitalised full MVNO is less significant in straightforward deployments. It becomes more apparent in complex scenarios: cross-border deployments where non-steered network selection matters, network-layer security requirements, or situations where deep troubleshooting access is needed quickly.
The useful question to ask of any MVNO is: what does your commercial arrangement with your host MNO permit you to do? The answer tells you more about the operational reality than any marketing description of infrastructure type.
Connectivity platforms: software on top of the stack
A connectivity platform is a software layer that sits on top of network connectivity either an MNO’s own or obtained from one or more MVNOs or MNOs through wholesale arrangements — and provides the management, visibility, and automation capabilities that IoT teams need to operate device fleets at scale.
The connectivity platform category includes a range of products. At one end, platforms built and operated by MNOs that integrate directly with their own network core, providing a unified view of both the network and the management interface. At the other end, platforms that aggregate connectivity from multiple operators and provide a common interface across them, without owning any network infrastructure themselves.
The distinction matters for the same reasons as the MNO vs MVNO distinction: it determines what depth of network-layer visibility and control the platform can provide, and what happens when something goes wrong at the network level.
What a connectivity platform needs to provide
Regardless of the infrastructure model underneath, a connectivity platform that is fit for IoT production deployments should provide: API-first access to all management functions so that connectivity operations can be automated and integrated into existing systems; real-time SIM monitoring with session-level data; historical usage and connectivity data for trend analysis; per-SIM data caps and cost controls; bulk lifecycle management operations; and security controls at the network layer including IMEI Lock, Private APN, and data traffic filtering.
The completeness of these capabilities, and whether they are available via API or only through a GUI, is often the most useful indicator of whether a platform was built for IoT operations or adapted from a consumer connectivity tool.
Resellers: the distribution layer
A reseller purchases connectivity from an MNO, MVNO, or connectivity aggregator and sells it on, typically with a management interface and sometimes with additional service wrapping. Resellers vary considerably in the sophistication of what they offer.
At their best, resellers provide a useful channel for customers who want connectivity with service support, commercial flexibility, or integration with specific device management platforms that the underlying network provider does not directly offer. The structural limit is that a reseller has no infrastructure of their own. Their ability to resolve network-level issues, implement custom network policies, or offer non-standard commercial structures depends entirely on what their upstream provider permits.
For simple deployments with standard requirements, a reseller can be a perfectly adequate source of connectivity. For complex deployments with specific technical or commercial requirements, the question of what a reseller can actually deliver — versus what they will need to refer upstream is worth understanding before committing to a commercial arrangement.
Aggregators: multi-network but no core ownership
A connectivity aggregator is a variant of the MVNO or reseller model that specifically focuses on providing access to multiple MNO networks through a single commercial relationship. Aggregators appeal to deployments that need coverage across many countries without managing separate carrier relationships in each.
The limitation of pure aggregation is that it does not provide the same depth of control as working with a provider that has its own core network components. Network policy configuration, security controls, and troubleshooting depth are all bounded by what the underlying MNO arrangements permit. An aggregator with strong bilateral agreements and its own core network components can provide good operational capability. A thin aggregator reselling another operator’s service with minimal infrastructure of its own provides less.
Comparing connectivity providers for a deployment?
The IoT SIM Connectivity Buyer Guide 2026 includes an evaluation framework and the specific questions to ask any provider about their infrastructure model, coverage, and platform capabilities.
Download the IoT SIM Connectivity Buyer Guide 2026 →
How the layers interact in practice
A real IoT deployment touches multiple layers of this stack, even when working with a single vendor. A device connects to a physical network tower (MNO infrastructure). The connection is authenticated against a core network system (MNO or full MVNO core). Usage data is recorded and surfaced in a connectivity management platform (which may be run by the MNO, MVNO, or a third-party platform provider). Commercial billing flows through whichever entity has the direct customer relationship.
When you buy connectivity from a provider who owns all of these layers, the commercial relationship and the technical responsibility are with a single entity. When layers are separated — for example, a connectivity platform sitting on top of an MVNO’s network, which is in turn built on an MNO’s infrastructure — each layer introduces a dependency and a potential delay in resolution when issues occur.
This is not necessarily a problem. Many deployments run successfully with multi-layer provider arrangements. The key is understanding which entity owns which layer, and what that means for the depth of visibility and control available to you as a customer.
Where OV sits in the ecosystem
OV is a true IoT MNO, operating its own core network infrastructure with data centres and local packet gateways. This means OV owns the core network layer the systems that authenticate devices, route connectivity, and record usage — as well as the OV ONE connectivity management platform that customers use to manage their deployments.
The commercial relationship is with a single entity. The platform that surfaces connectivity data and management controls integrates directly with OV’s own network core rather than aggregating data from a third-party operator’s systems. Security controls such as IMEI Lock, Private APN, IoT SAFE, and geofencing are implemented natively at the network layer, not configured through a host operator’s API.
For customers evaluating where OV sits in the ecosystem: OV operates as an MNO with its own connectivity management platform, accessible to customers directly via OV ONE and to MVNOs and resellers who build their own services on OV’s infrastructure.
Frequently asked questions
What is the practical difference between a connectivity platform and an MNO?
An MNO owns the physical network infrastructure — spectrum, towers, core network systems — that devices ultimately connect to. A connectivity platform is a software layer that provides management, monitoring, and automation capabilities on top of network connectivity. An MNO can also operate its own connectivity management platform, in which case both layers are owned and operated by the same organisation. A standalone connectivity platform typically obtains network connectivity through wholesale arrangements with one or more MNOs and provides a unified interface across them. The distinction matters for troubleshooting depth, security control implementation, and what can be configured at the network layer.
Can a connectivity platform replace working directly with an MNO?
For many deployments, a well-built connectivity platform that aggregates multiple MNO connections provides a practically adequate substitute for working with a single MNO directly — particularly if the platform has its own core network components and strong bilateral network agreements. The scenarios where working with a true MNO (or a platform built by an MNO on its own core) matters most are: deployments requiring non-steered multi-network access at scale, network-layer security requirements that need to be enforced natively, and situations where deep troubleshooting access — below the platform interface — is needed quickly to resolve production incidents.
What should I ask a connectivity provider to understand where they sit in the ecosystem?
The most direct questions are: do you operate your own core network, or is your connectivity provided through a host MNO or MVNO arrangement? What level of access do you have to session-level network data for troubleshooting? How are security controls such as Private APN and IMEI Lock implemented at your own network layer or through another operator’s systems? Can you configure custom network access policies independently, or do you need to request changes from an upstream provider? These questions are more diagnostic than any self-description the provider offers.
Is a reseller appropriate for a large IoT deployment?
A reseller can be appropriate for large deployments when the deployment’s requirements are straightforward standard connectivity, established coverage territories, no unusual security or network policy requirements. The constraint is that a reseller’s ability to customise, troubleshoot at depth, and implement non-standard arrangements is bounded by what their upstream provider permits. For deployments with complex multi-country coverage requirements, stringent network-layer security needs, or a requirement for custom commercial structures, working with an MNO or well-capitalised MVNO directly typically provides more reliable outcomes than a reseller arrangement.
How does OV’s model differ from a connectivity aggregator?
OV is a true IoT MNO, not an aggregator. OV operates its own core network infrastructure rather than aggregating connectivity from multiple host operators through wholesale arrangements. This means OV can implement security controls, network access policies, and SIM management functions natively at its own network layer rather than configuring them through a third-party operator’s API. OV ONE, OV’s connectivity management platform, integrates directly with OV’s own core network, which provides deeper visibility and faster resolution capability than a platform aggregating data from external network providers.
Talk to OV about your deployment
OV is a true IoT MNO with coverage across 180+ countries and 600+ networks, and OV ONE provides full connectivity management via API and platform interface. Book a demo or request a free IoT SIM trial to see what working directly with an IoT MNO looks like.
Book a Demo | Request a Free IoT SIM Trial
