An MVNO sells mobile service under its own brand on another operator’s radio network. An MVNE supplies the platform and the operational services it runs on; an MVNA buys wholesale capacity in bulk and resells it to several MVNOs. The difference between the two is which capacity contract they hold, not which software they run. Of the 2,138 MVNOs GSMA Intelligence counted worldwide in August 2025, only 96 are Full MVNOs and 265 are operator sub-brands; everyone else sits on somebody else’s platform.
GSMA Intelligence counted 2,138 MVNOs worldwide in August 2025, with another 283 announced and waiting to launch (analysis published November 2025). Only 96 of those are Full MVNOs and 265 are operator sub-brands. Everything in between, well over 1,700 operators, runs on somebody else’s platform under somebody else’s wholesale contract. That somebody is usually an MVNE, an MVNA, or an MNO wholesale team that has quietly become one of the two. The acronyms get used loosely, including in hosts’ own sales decks, so it is worth being precise about who holds which asset and which contract.
Three definitions, from the sources people actually cite
Juniper Research (January 2026) defines an MVNO as “a mobile service provider that leases wholesale capacity from mobile network operators, without owning its own network infrastructure”. That covers a supermarket brand on a reseller deal and a Full MVNO with its own core; the definition says nothing about how much of the stack the operator runs. Model names (Reseller or Light, Medium, Full) fill that gap, and we cover them in detail on the operating-models page and in the earlier post on Full MVNO, Light MVNO and MVNE models.
An MVNE, per Wikipedia’s entry on mobile virtual network enablers, “provides network infrastructure and related services, such as BSS and OSS, to an MVNO”. The enabler is not a mobile brand. It sells platform and operations: SIM management, product catalogue, charging, billing, CRM, provisioning into the host, interconnect, often customer-care tooling and regulatory reporting. Its customers are MVNOs, and its revenue is a platform fee, a per-subscriber charge, or a share of margin.
An MVNA, from the same source, is “a wholesale intermediary between MNO and smaller MVNOs” that “holds a large wholesale agreement with the MNO, then re-wholesales airtime to smaller MVNOs”. The aggregator’s asset is a contract, not a platform. It buys capacity at volume prices a brand with 20,000 subscribers would never be offered and sells it on with a margin. Most MVNAs also run an enablement platform, because you cannot re-wholesale usage you cannot rate, but aggregation itself is a commercial role. That distinction matters later.
The chain from spectrum to subscriber
Read from the top, the value chain has four layers. The MNO holds the licence, the spectrum, the radio network and the core, and sells capacity wholesale. The MVNA, where one exists, buys that capacity in bulk and slices it. The MVNE provides the systems an operator needs to turn capacity into a product: catalogue, charging, billing, SIM logistics, provisioning, interconnect. The MVNO owns the brand, the proposition and the subscriber.
In practice the layers collapse into fewer companies. A Full MVNO occupies the bottom two itself, running its own BSS and some of the core. An MVNE that signs the wholesale contract occupies the middle two, and is then also an MVNA. An MNO that launches an enablement platform for its partners occupies the top three, leaving them only the brand. Nigeria’s regulator recognised this when it split MVNO licensing into five tiers, with a Tier 4 “Virtual Aggregator/Enabler” licence at NGN 150 million and a Tier 5 “Unified Virtual Operator” at NGN 250 million (NCC framework as summarised by the International Bar Association, June 2022). One regulator, at least, treats the enabler or aggregator as a role distinct from the operator.
Who owns what: MNO, MVNA, MVNE and the three MVNO models
The table below sets out the assets and contracts that define each role. It reflects the model names used on this site; other markets use thin, thick or enhanced, and the labels matter less than the rows.
| Asset or contract | MNO (host) | MVNA | MVNE | Light MVNO | Medium MVNO (own BSS) | Full MVNO |
|---|---|---|---|---|---|---|
| Brand and marketing | own retail brand, sub-brands | none to end users, or a small one | none to end users | yours | yours | yours |
| Subscriber relationship (contract, care, data) | its own base | none; tenants hold it | none; tenants hold it | yours (care often via enabler) | yours | yours |
| BSS: catalogue, charging, billing, CRM | own | multi-tenant BSS, own or rented from an MVNE | owns and operates a multi-tenant BSS | enabler’s or host’s | yours | yours |
| HLR/HSS and core elements | own | host’s, occasionally own | host’s, occasionally own | host’s | host’s, via provisioning and charging interfaces | yours (or via partners) |
| Numbering and SIM | own ranges and SIM | per tenant, or one pooled range | per tenant, or issued from its own pool | host’s | own SIM in most markets, own numbering in some | own ranges, own SIM and eSIM |
| Wholesale agreement with the MNO | sells wholesale | holds one bulk agreement | none; each MVNO contracts the host directly | via enabler or aggregator | yours | yours |
| Settlement | with each wholesale counterparty | with the host on one side, each tenant on the other | platform fees to tenants; usage settlement sits between MVNO and host | pays the enabler or aggregator | with the host | with the host, plus interconnect and roaming partners |
Two rows carry most of the weight. The wholesale-agreement row separates MVNA from MVNE: an aggregator is the host’s counterparty, an enabler is not. The BSS row separates Light from Medium: the moment the MVNO runs its own catalogue and charging, it stops needing an enabler for anything except, possibly, network-side services. These two rows also explain why the same company can appear in three columns depending on which contract you are looking at.
MVNA vs MVNE: the difference is the contract, not the software
Ask an enabler and an aggregator to show you their platforms and you will struggle to tell them apart. Both run tenant onboarding, per-tenant catalogues, shared charging, settlement engines. The difference shows up in the finance and legal departments.
The enabler earns a service fee and carries little volume risk. If a tenant’s subscribers stop using data, the enabler’s invoice to that tenant barely moves. The aggregator has signed minimum commitments with the host, often with take-or-pay clauses, and has extended credit to tenants smaller than itself. Its margin is the gap between the host’s bulk price and its re-wholesale price lists, and it needs two rating passes on every usage record: once at host rates to reconcile the wholesale bill, once at each tenant’s tariff to invoice them. An enabler that only rates at the tenant’s retail tariff has a simpler settlement problem and a smaller balance-sheet exposure.
This is why “does an MVNA need its own BSS” is the wrong question. It needs the enabler’s BSS plus wholesale rating against the host contract, tiered re-wholesale pricing per tenant, sub-tenant settlement with revenue share and minimum commitments, and margin reporting per tenant, product and period. Those are billing functions. The rest is a contract.
When an MVNE becomes an MVNA
Enablers slide into aggregation more often than they plan it. It starts with a prospective tenant too small to get host terms on its own: a regional brand, a community operator, a fintech with a pilot. The enabler already knows the host, so it offers to hold the wholesale agreement and pass capacity through. One tenant becomes four. Then the host’s wholesale team decides it would rather have one counterparty than ten and starts steering new MVNOs towards the enabler, which now carries volume commitments, credit risk and, in markets like Nigeria, a licence category it never applied for.
Three things change. Settlement has to handle the two-sided rating described above and expose margin per tenant, so the aggregator can see which price lists are underwater. The regulatory position changes: the aggregator reports on the wholesale relationship while each tenant still reports as the licensed operator it is, so the BSS must produce both views. And the tenant lifecycle becomes commercially sensitive. A tenant that outgrows aggregation wants to move its base and numbering to its own BSS and contract the host directly, and an aggregator that cannot offer that path cleanly loses its best tenants at the worst moment.
Our view: an enabler should decide deliberately whether it wants the aggregation business, and price it as a wholesale business with a cost of capital rather than as an add-on to platform fees. If the answer is yes, wholesale rating and per-tenant settlement belong in the BSS scope from the start. Retrofitting them onto a platform built for retail charging is a project on the scale of the original deployment.
When an MNO wholesale team needs an MVNE platform
The other direction is at least as common. An MNO signs its first two or three MVNO partners bilaterally: each gets its own interconnect, its own operational interface into the host’s OSS, its own escalation path. That works. Around the eighth or tenth partner it stops working, because onboarding cost does not fall with volume. Every new partner means new configuration, testing and procedures for an engineering team that also has a network to run.
South Africa shows the pattern. TechCentral (June 2025) counted 23 MVNOs in the country, with Cell C hosting 13 and MTN 9. Cell C had built an MVNE platform; Vodacom launched one in 2024, Huge NXTGN in 2025, and Telkom announced one. TechCabal (August 2026) put Cell C at 5.7 million MVNO subscribers, up 27% year on year and roughly 80 to 85% of the South African MVNO market. Wholesale had become a business line with its own growth rate, and a business line needs a platform, not a queue.
The signals are fairly consistent. Onboarding a new partner takes longer than six months even when commercial terms were agreed in week two. Partners ask for Light or Medium arrangements the host cannot configure without engineering work. The consumer business wants a digital sub-brand and the only way to launch it is as another bilateral partner. Finance cannot produce a per-partner margin view without a spreadsheet. Any two of those, and an enablement platform pays for itself in avoided engineering time before it earns a rand of new wholesale revenue.
Bilateral and platform are not exclusive. An MNO can run an MVNE platform for its Light and Medium partners and still sign a Full MVNO bilaterally, because the Full MVNO brings its own BSS and needs only network interfaces.
Where Avante fits
Avante is a BSS vendor, not an enabler or an aggregator. It does not hold wholesale agreements or run a network. Avante MVNx Suite is the multi-tenant BSS that an MVNE, an MVNA or an MNO wholesale team runs to onboard tenants, rate usage against the host contract and against each tenant’s tariff, and settle on both sides. Three MVNE platforms have been delivered on it, alongside 15 live MVNOs, and the same stack serves a Medium or Full MVNO that wants its own BSS, so a tenant that outgrows enablement moves without re-platforming. LANCK Telecom runs it across several European and African markets, and Brilliantel in South Africa uses it for B2B and B2G billing models that standard enablement setups do not offer. Details are on the MVNE and MVNA platform page.
Frequently asked questions
What is an MVNE and what does it do for an MVNO?
An MVNE (mobile virtual network enabler) supplies the systems and operations an MVNO needs but does not want to build: SIM management, product catalogue, online charging, billing, CRM, provisioning into the host network, interconnect and often customer-care tooling. The MVNO keeps the brand and the subscriber relationship. Enablers are paid through platform fees, per-subscriber charges or a margin share, and one enabler typically serves several MVNOs on a shared, multi-tenant platform.
What is the difference between an MVNA and an MVNE?
The contract with the host. An MVNE provides platform and operations but does not sign the wholesale agreement; each MVNO contracts the MNO directly. An MVNA (mobile virtual network aggregator) holds one bulk wholesale agreement and re-wholesales capacity to smaller MVNOs under its own price lists. Most aggregators also run an enablement platform, so one company can be both. What separates the roles is who carries the volume commitment and the credit risk.
Does an MVNA need its own BSS?
It needs the enabler’s multi-tenant BSS plus wholesale functions: rating usage at host rates to reconcile the bulk bill, tiered re-wholesale pricing per tenant, settlement with each tenant including revenue share and minimum commitments, and margin reporting per tenant and product. Some aggregators rent the platform from an MVNE and add the contract on top; larger ones run their own. Either way, the second rating pass is what makes it an aggregator’s BSS.
Can an MVNO contract the MNO directly and skip the enabler?
Yes, and Medium and Full MVNOs usually do. A Medium MVNO runs its own BSS and connects to the host through provisioning, charging and mediation interfaces; a Full MVNO adds its own HLR/HSS, numbering and interconnect. Scale and product decide it: hosts set minimum volumes for direct wholesale, so a small brand with a standard offer is better served on an enabler or through an aggregator. An MVNO whose pricing logic is the product tends to need its own BSS regardless; the launch process page sets out what that path involves.
How does an MNO become an MVNE?
By replacing bilateral integrations with a shared enablement platform: tenant onboarding from templates, per-tenant catalogues and branding, shared or dedicated charging and billing, wholesale rating between platform and host network, settlement per tenant, and tenant APIs. Network interfaces are connected once and shared. Operators tend to make the move somewhere between five and ten partners, when onboarding cost stops falling and the engineering queue becomes the constraint on wholesale growth.