The model decides who owns the subscriber, the data and the margin. Most organisations choose it after the platform. Choose it first.
Reviewed by Alexander Donskoy, Sales Director, Avante · Last reviewed 2026-09
The model sets the cost structure, the time to market, the integration effort and how much room you have to change course later. Three of the five are rungs on the same ladder: each adds a layer of the operator to what you own, and the top two share a platform. The other two are that same stack turned outwards and run for other operators rather than for your own base. The comparison and the five-question selector below turn the shape into a decision.
01
Brand, distribution and the customer relationship. The host or an enabler runs SIM management, rating, billing and interconnect, so the product is limited to what their shelf and pricing tools allow.
02
Adds the product catalogue, charging, billing, CRM and the subscriber data, integrated with the host network. Four to six months once host and legal readiness are confirmed.
03
Adds HLR/HSS, packet core, own numbering, interconnect and roaming. The same Avante BSS stays underneath, so moving up is an extension rather than a second launch.
Turned outwards, for other operators
Terminology in this market is not standardised. This is how we use the terms on this site: one column per model, and the bands show who runs which layer of the stack.
The host or a third-party MVNE runs SIM management, HLR/HSS, rating, billing and interconnect. You own the brand, distribution and the customer relationship — and, in the light variant, care and tariff presentation. The product is limited to what their shelf allows.
Your own product catalogue, charging, billing, CRM, self-care and partner management, integrated with the host through provisioning, charging and mediation interfaces. Subscriber data and commercial logic are yours; in some markets the numbering range and the SIMs are too.
Adds the network layer: own HLR/HSS or subscriber data management, own packet core or gateways, own numbering, own interconnect and roaming agreements. The host provides spectrum, radio access and capacity only. The most control, and the most operational responsibility.
An infrastructure layer rather than an MVNO: one multi-tenant platform providing BSS/OSS, SIM management, interconnect and operations to several MVNOs at once, between the host and its partners. For specialist enablers, and for MNO wholesale teams scaling a portfolio.
A wholesale intermediary that buys host capacity in bulk under one agreement and re-wholesales it to smaller MVNOs, usually running them on an MVNE platform. It needs tiered wholesale rating and settlement with every tenant.
*Avante planning assumptions from delivered projects; the clock starts once the host agreement and legal framework are confirmed.
| Dimension | Reseller / Light | Medium (own BSS) | Full MVNO | MVNE | MVNA |
|---|---|---|---|---|---|
| Brand, marketing, distribution | you | you | you | your tenants | your tenants |
| Customer care | host / enabler (light: you) | you | you | you, per tenant | you or tenants |
| Product catalogue and pricing logic | host / enabler | you | you | you, per tenant | you, wholesale tiers |
| Online charging and billing | host / enabler | you | you | you, multi-tenant | you, wholesale + retail |
| Subscriber data and CRM | host / enabler | you | you | you and tenants | you and tenants |
| SIM / eSIM issuance and inventory | host / enabler | you (in most markets) | you | you, per tenant | you, per tenant |
| HLR/HSS, subscriber data management | host | host (via interface) | you | host or you | host or you |
| Packet core, gateways | host | host | you or partner | host or you | host or you |
| Numbering range | host | some markets | you | per tenant / yours | yours or per tenant |
| Interconnect and roaming agreements | host | host | you | you | you |
| Wholesale agreement with the host | via enabler or host | you | you | you | you, in bulk |
| Time to commercial launch* | weeks – 3 months | 4–6 months | 8–10 months | 6–12 months | 6–12 months |
| Upfront investment | low | medium | high | high | high |
| Independence from the host | low | medium | full | medium | medium |
| Long-term optionality | lower | high (Full on the same BSS) | high | high | high |
A light MVNO on an enabler's platform rarely needs its own BSS, and we will say so. Where Avante fits: when the enabler's tools cannot deliver your offer (loyalty integration, real-time pricing, your own data) and you are ready to move to Medium. We migrate the base in one window and keep history and active plans.
Product catalogue, OCS, convergent billing, CRM and agent workspace, self-care, PRM, loyalty, BPM, provisioning and mediation interfaces to the host, MNP, KYC and payment integrations, regulatory reporting. Four to six months after host and legal readiness; managed service in year one if you have no BSS team.
We add HLR/HSS and subscriber data management, packet core and gateways through partners, own numbering, interconnect settlement and roaming clearing, all on the same platform and data model. There is no second subscriber migration and no re-platforming. A delivered reference moved Medium → Full → multi-host on one stack.
Tenant onboarding, per-tenant catalogues, branding and self-care, shared or dedicated charging, wholesale rating between you and the host, settlement with each tenant, tenant APIs and reporting. Three MVNE platforms delivered.
Bulk wholesale agreement modelled once; tiered re-wholesale pricing per tenant; sub-tenant settlement, revenue share and regulatory reporting per operator.
"We can always upgrade to Full later" is true in principle. In practice, when the light MVNO's subscriber base, billing records, SIM inventory, number ranges and catalogue sit inside the enabler's infrastructure, moving them is a migration project on the scale of the original launch: service continuity, billing history, number management, porting windows.
The way to keep the option genuinely open is to hold those assets on your own BSS from the Medium stage. On Avante, Full adds network elements and interfaces to the platform you already run; it does not replace it. That is the difference between an upgrade and a second launch.
Work backwards from the product. A standard SIM with branded packaging and basic bundles is a light MVNO. Real-time balance integration with a financial account, individual-level pricing, or loyalty rules on purchase events need your own catalogue and charging engine, which means Medium at least.
Full is an organisational decision as much as a platform one. It needs engineers who understand HLR/HSS, numbering, roaming and interconnect. Some of that can be outsourced (our managed service covers the BSS), but network operations need an owner.
A Medium launch on a platform already in production is a four to six month project; Full with custom network integration is typically twice that. When the mobile product is tied to a bank's app or a retailer's loyalty platform, the cost of delay is a digital product that moves on without it.
A light MVNO owns the brand and the customer relationship while the host or an enabler runs billing, SIM, HLR/HSS and interconnect. A full MVNO runs all of those itself, with its own core elements, numbering, interconnect and roaming, and buys only spectrum and radio access from the host. Medium sits between the two: own BSS and commercial logic, host network.
Roughly. Thin usually means light or reseller; thick, enhanced and medium are used for operators with their own BSS and, in some definitions, some core elements. Model names vary by market and regulator (Nigeria, for example, licenses five tiers); what matters is who owns billing, data, SIM, numbering and core, whatever the label says.
Only if the platform was built for it. Platforms designed for reselling typically cannot extend to own HLR/HSS, own charging or additional network integrations. On Avante, Medium and Full share one BSS, so the extension is a project on the same platform rather than a migration to a new one.
Timeline and cost, in that order. Underestimate the control you need and you face a capability gap after launch, then a migration at an inconvenient time. Overestimate it and you spend a year building infrastructure for capabilities you will not use while a competitor launches in four months.
It needs the same functions with multi-tenancy on top: tenant isolation, per-tenant catalogues and branding, shared or dedicated charging, wholesale rating and settlement per tenant. Avante MVNx Suite runs both from one architecture, which is why an MNO can start with a few bilateral MVNO partners and move to platform-based enablement without replacing the stack.
Only if you intend to buy capacity in bulk and re-wholesale it to other operators. For a single brand, the question is Medium versus Full; for an enabler, whether tenants contract the host directly or through you.
Thirty minutes with our MVNO architecture team on your control requirements, timeline and operating capacity. You leave with a written model recommendation and the scope it implies.
