MNO vs. MVNO: What’s the Difference, and Which One Does Your IoT Deployment Need?

TL;DR

• An MNO owns the physical network (spectrum, towers, core), while an MVNO leases that capacity and adds the software layer devices actually need, like provisioning, billing, and cloud integration.
• Neither model is universally “better” than the other for IoT. The right choice depends on how many regions or countries you’re in, how predictable your device volumes are, and whether you have telecom expertise on staff.
• A newer category, the MVNE, lets operators and enterprises run their own MVNO on someone else’s cloud-native core, a decision layer above the one most IoT teams are making today.

---

Say your IoT deployment needs connectivity across a dozen countries. On paper, that sounds like a coverage problem. In practice, it’s a dozen separate carrier relationships, and each one comes with its own contract to negotiate, its own pricing structure, its own SLA, and its own account team to manage.

That list ramps up fast. Someone on your team now owns credit checks, tax and regulatory compliance in every market, renewal negotiations on staggered timelines, and a support escalation path that looks different in each country. Even the MNOs that do offer good support won’t offer it consistently across the whole footprint, because you’re a different-sized customer to each of them.

This is where MVNOs step in, and it’s why the MNO versus MVNO decision deserves more thought than most teams give it upfront. There’s also a third term worth knowing, MVNE, which matters if you ever end up on the other side of that table, building the network rather than just buying access to it.

---

What is an MNO?

A Mobile Network Operator owns the licensed spectrum, the physical radio access network (the towers and base stations), and the core network that authenticates devices and routes their traffic. Think AT&T, Verizon, T-Mobile, NTT Docomo, or Vodafone.

Owning the network means carrying real infrastructure obligations. An MNO holds a spectrum license from a regulator, builds and maintains physical radio equipment, and operates the core systems, like the Home Subscriber Server and packet gateway, that keep every connected device authenticated and routed correctly. That’s a significant fixed cost, and it’s also where an MNO’s negotiating leverage comes from.

---

What is an MVNO?

A Mobile Virtual Network Operator doesn’t own spectrum or towers. Instead, it buys wholesale network capacity from one or more MNOs and builds its own layer on top: SIM management, billing, customer support, and, for IoT-focused MVNOs, software tooling that a carrier typically doesn’t provide.

Soracom operates as an MVNO, aggregating access across multiple underlying carriers rather than being tied to a single network. That’s worth mentioning not as a sales pitch, but because it’s useful context for everything below: this is a model we operate inside of every day, not just a category we’re describing from the outside.

---

Breaking down who actually does what

The cleanest way to compare these two models isn’t to argue over labels. It’s to break “cellular service” into the functions it’s actually made of, then see who handles each one.

Function	MNO	MVNO
Spectrum license and physical radio access network	Owns it	Doesn’t own it, uses it under contract
Core network (authentication, session management, SMS routing)	Operates it directly	Relies on the MNO’s core, or increasingly, a cloud-native alternative
SIM and eSIM provisioning, lifecycle management	Limited, built for consumer plans	Core value-add, especially for IoT-specific tooling
Multi-carrier failover and roaming	Single network, unless bilateral agreements exist	Aggregates several MNOs into one relationship
Billing and usage-based pricing	Built around consumer phone plans	Designed for per-device, usage-based IoT patterns
Cloud integration, remote access, protocol translation	Not typically offered	Common value-add layer

The pattern is consistent. An MNO’s job stops at the network. An MVNO’s job starts where the network output needs to become something a fleet of connected devices can actually use.

---

When a direct MNO relationship makes sense

Going straight to a carrier is the right call in a specific set of situations, and it’s worth naming them honestly rather than treating this as a foregone conclusion.

• Device volume is extremely high, predictable, and concentrated in a single country.
• You already have in-house telecom expertise managing carrier relationships and contracts.
• A regulatory or contractual requirement mandates a direct carrier relationship.
• You’re willing to trade flexibility for the negotiating leverage of a large, direct enterprise agreement.

---

When an MVNO makes more sense

For most IoT deployments, especially ones that cross borders or scale unevenly, an MVNO fits the shape of the problem better.

• Devices are deployed across multiple countries where no single MNO’s footprint covers everything.
• You need multi-carrier redundancy without managing a separate contract per network.
• Device volumes are hard to forecast, common in pilot-to-scale IoT projects.
• You want SIM management, usage-based billing, and cloud integration out of the box instead of building it.
• Getting to market quickly matters more than negotiating the lowest possible per-megabyte rate.

Lamplight Logistics is a good illustration of what this looks like in practice. The company ships real-time location tracking gateways worldwide and relies on Soracom Air, a Virtual Private Gateway, and remote diagnostics tools like Napter and Peek to get devices online without per-country carrier setup. As CEO Kurt Nehrenz put it, “I feel comfortable having a giant box of gateways shipped to God-knows-where, knowing that as soon as they get plugged in, they’re going to work.” That’s the practical payoff of the MVNO model: the network relationship is handled, so the team can focus on the device and the dat

---

A third term: what is an MVNE, and why it matters now

Everything above assumes you’re buying connectivity for your devices. But some organizations are on the other side of that transaction, they want to become the one offering mobile service, without building a carrier-grade network from the ground up. That’s what a Mobile Virtual Network Enabler, or MVNE, provides: the technical and operational backend, including core network infrastructure and provisioning systems, that lets another company operate as an MVNO without building it themselves.

This category became more concrete in July 2026, when Soracom announced an MVNE business, opening up the cloud-native core network it has run since 2014, including HSS, packet gateway and user plane functions, SMSC, and IMS core, to other mobile network operators, MVNOs, and enterprises that want to run their own MVNO. The idea is to let an operator launch mobile services on infrastructure that’s already proven in production, rather than building and maintaining that core themselves. Soracom’s own subsidiary, Misora Connect, runs a live MVNO in Japan on this same core, which is a more concrete proof point than an abstract capability claim.

If you’ve read this far and realized you’re not choosing between an MNO and an MVNO but evaluating whether to build or rent the network layer entirely, that’s a related, and now more accessible, decision.

---

How to decide

Before your next connectivity conversation, it’s worth answering a few questions honestly.

How many countries are your devices actually in, and does one carrier’s footprint cover that? How predictable is your device volume over the next 12 months? Do you have staff who manage carrier contracts as part of their job today, or would that be new? And, underneath all of it, are you buying connectivity for a fleet of devices, or trying to offer mobile service to someone else?

There’s no universally right answer, and that’s the point. If you want to talk through which model fits your specific deployment, Soracom’s team is a reasonable place to start that conversation.

---

Whether you’re weighing a direct carrier relationship, evaluating MVNOs for a multi-country rollout, or exploring what an MVNE could do for your own network plans, Soracom’s team can help you think it through. Contact us to talk through what fits your specific deployment.