Wholesale MVNO Solutions: Infrastructure, Pricing and Deployment

Wholesale MVNO Solutions: Infrastructure, Pricing and Deployment

 

Wholesale MVNO solutions have an awkward first impression: the platform looks simple and the invoice does not. Voice is the part of an MVNO that breaks budgets. Data launches on a hosted core network and a few API calls. Voice requires an IMS core, subscriber signaling, media handling, lawful intercept, emergency calling and an interconnect agreement with at least one carrier, and every one of those items carries a separate cost line and a separate failure mode. This guide covers what a wholesale MVNO solution has to deliver in 2026, how the pricing models shape your margin, and the questions that separate platforms built for voice from platforms built for data.

If you have not worked with IMS before, the background in mobile virtual network operators will help frame the rest of this article, since the terms get reused loosely across the industry.

What Wholesale MVNO Solutions Actually Mean

An MVNO resells mobile service without owning a radio access network. The host operator owns the spectrum and the access network, and the MVNO owns the customer relationship, the brand and the retail price. A wholesale MVNO arrangement is simply the version where the MVNO buys its network capacity, signaling and connectivity at wholesale rates and builds its own margin on top.

In practice three operating models show up on the market, and the difference matters more than any software feature:

• Full MVNO. Own HLR and HSS, own the SIM profile, control provisioning end to end. Highest control, longest timeline, highest regulatory load.
• Hosted MVNO. The host operates HLR, HSS and the core network, and the MVNO manages branding, tariff and distribution through an API. Fastest to launch, lowest control, per-subscriber economics.
• MVNE or MVNA. An intermediary provides the platform plus compliance and network aggregation, and the MVNO resells again. Useful when you have no host operator relationship of your own.

The commercial question is where your margin actually sits. On a hosted model your margin lives in the spread between the wholesale per-subscriber fee and your retail ARPU. On a full MVNO model your margin also includes the difference between your own termination cost and your retail call price, which means interconnect quality becomes a profit lever rather than a technical detail. Several MVNO operators we have worked with found this out late, because they modeled the ARPU without modeling per-minute termination.

The Six Systems You Are Actually Buying

Vendor pages describe a single product. Underneath, an MVNO platform is six systems that have to work together. Ask any vendor to walk you through all six, because most demos only cover two.

1. Subscriber data (HLR and HSS)

The HLR is the authoritative record of who each SIM is and what it is entitled to. The HSS holds the subscriber profile that the radio network consults during registration and call setup. In a hosted model these are the host operator’s systems and you consume them through APIs. In a full MVNO you run them, which means also running the provisioning chain that keeps them in sync with your billing and CRM systems.

2. An IMS core for voice

The IP Multimedia Subsystem handles SIP registration, session setup, policy control and the routing of voice calls. This is the component that separates a data MVNO from a voice MVNO. Our cloud IMS platform page covers the architecture in detail, including why operators keep this in the cloud rather than in their own data center.

3. Connectivity and media handling

Signaling and media are separate problems. Signaling is low bandwidth and latency tolerant. Media is bandwidth heavy and latency sensitive. The platform needs an SBC or equivalent media anchor to terminate RTP, handle codec negotiation (Opus, AMR-WB, AMR-NB, G.711) and bridge between the IP side and the legacy TDM side when a call lands on a network that has not migrated. Operators moving to VoLTE and VoWiFi should also confirm early whether the media path stays in the IMS or hands off to a separate interconnect.

4. Charging, rating and billing

Prepaid requires real-time online charging or at least near real-time balance updates, because a call must be allowed or cut based on the current balance. Postpaid requires CDR collection, rating and reconciliation against the interconnect settlement file. Both require tariff models that can change mid-month without a platform migration. If your plans include bundles, add-ons and promotional rates, ask to see them modeled live rather than described in a slide.

5. Provisioning and self-care

This covers SIM activation, MSISDN assignment, plan changes, number porting requests and top-ups. Self-care means the customer can do most of this without contacting you, because support load scales with subscribers while your team does not.

6. BSS, OSS and integrations

Billing to the finance ledger, CRM sync, distributor stock, campaign management and reporting. A REST API with documented rate limits and webhooks for asynchronous events is the minimum you should insist on. Vendors who describe integration only as “we have an API” usually mean a thin wrapper with no webhook support, which forces your platform into polling every few minutes.

Voice Is Where MVNOs Fail

Most failed MVNO launches we have reviewed were not platform failures. The platform worked. The voice service did not pass the quality bar customers expect, and once a customer hears one echo or dropped call they move to the host operator’s own brand, which sits one tap away on the same network.

VoLTE and VoWiFi change the math

An MVNO that only offers CSFB or an OTT app is not offering phone service to most customers. VoLTE keeps the call on the IMS, and VoWiFi extends it onto untrusted WiFi. Both depend on the IMS core and on policy control, which is why an IMS platform is no longer optional for a serious MVNO launch. Deployment options for hosted and dedicated IMS are covered in the platform section below.

Interconnect and termination

Outbound calls from your subscribers have to land on someone else’s network. That requires either a direct interconnect agreement or a carrier willing to carry the traffic. Rates come in two shapes: a flat interconnect port charge, or a per-minute termination rate, sometimes a combination. Route quality, Answer Seizure Ratio and CLI transparency all move the effective price, which is the same reasoning behind our VoIP termination cost breakdown. Apply it to the MVNO unit economics and the cost per minute lands directly in your gross margin.

Pricing Models for Wholesale MVNO Solutions

Five pricing structures show up in 2026 proposals. They are not mutually exclusive, and most MVNOs end up on a blend.

Model	What you pay for	How it shapes your margin
Per active subscriber	A monthly fee per live SIM, often tiered by band	Predictable cost, flat margin per subscriber regardless of usage. Punishes heavy data users.
Per voice minute	Wholesale network charge per originated or terminated minute	Variable cost. Margin depends on your tariff and your own termination rate.
Per MB or per GB	Data consumed, with fair use and throttling rules	Variable cost. Needs real-time metering to prevent bill shock.
Platform license	One-off or annual fee for the IMS core and BSS licenses	Fixed cost that only works above a certain subscriber count.
Revenue share	A percentage of billed revenue instead of a unit fee	Zero fixed cost, but your upside is capped and reporting must be audited.

The decision rule is simple. If you are pre-revenue and modeling a base case, avoid revenue share, because it hides your unit cost from you until you have revenue to share. If you are pre-revenue and modeling a downside case, avoid per-subscriber fees, because they bite before your first paying customer.

For the arithmetic behind each of these, read our MVNO wholesale pricing models guide, which covers wholesale network charges, retail tariff design and the margin maths for voice bundles.

Questions to Ask Before You Sign

These are the questions that expose platform gaps early. Ask them in writing and get the answers in the contract or the service description.

• Uptime commitment. What is the SLA on the IMS core, and are service credits the only remedy? A voice MVNO with a 99.5% target is effectively unusable during business hours.
• Number porting. Can you bring numbers in, and can you port out? Operators cannot be locked in, and regulators ask about portability in most markets.
• Regulatory split. Who owns emergency calling, lawful intercept and data retention duties, and are the costs passed through or absorbed?
• Roaming treatment. When a subscriber is abroad, do you get roaming revenue, or is the traffic handed to the visited network and billed to you as outbound?
• Rate limits. What is the documented API throughput, and what happens when you exceed it? Throttling during a marketing campaign is a bad look.
• Fraud controls. Does the platform detect IRSD abuse, SMS pumping and call forwarding fraud, or do you build it? Fraud losses on wholesale voice are typically a fraud team’s first test of a new operator.
• Exit plan. If you leave, how do you export subscribers, CDRs and tariff definitions, and for how long do you keep the data?

Realistic Build Timelines

Published launch timelines are optimistic because they exclude regulatory work. Ranges we would put in a board deck:

• API-based data MVNO: 2 to 4 months. Integration, SIM stock, tariff setup, a basic portal. Requires an existing host operator with an API.
• Voice MVNO on a hosted core: 4 to 9 months. Adds IMS integration, media testing, interconnect, emergency calling and interop testing with the host network.
• Full MVNO with own HLR, HSS and PLMN: 9 to 18 months. Adds network code assignment, number assignment, type approval, roaming agreements and extensive interop certification.

Interconnect and number assignment dominate these ranges more than software does. Start those conversations in month one, even while the platform is still being configured. The how to start an MVNO guide covers the sequencing in more detail.

How to Compare MVNO Solutions

A structured comparison prevents the demo from deciding the outcome. Score each vendor from one to five on these eight criteria, weight them for your launch, and total the results.

Criterion	What good looks like
Voice readiness	IMS core in production, VoLTE tested on real devices, documented codec support
Wholesale rate structure	Published per-minute and per-subscriber rates, with volume tiers you can see before signing
Interconnect quality	Per-destination ASR figures, CLI transparency policy, published route tiers
Billing accuracy	Rate change without a migration, CDR reconciliation against carrier settlement
API and integration	Documented endpoints, webhooks, sandbox, published rate limits
Compliance support	Platform covers the technical parts of emergency calling, intercept and retention duties
Support model	Named engineer for escalations, defined response times, not only a ticket portal
Exit terms	Full data export in an open format, documented timelines

Frequently Asked Questions

What is a wholesale MVNO solution?

It is a platform and network arrangement that lets an operator sell mobile service using someone else’s radio access network, bought at wholesale per-minute and per-subscriber rates so the MVNO can add its own retail margin. The platform supplies subscriber management, an IMS core for voice, charging and billing, and the APIs to connect it all.

Do I need an IMS core to launch an MVNO?

For a data-only MVNO, no. A hosted core network can carry data with far less infrastructure. For an MVNO that expects to offer phone calls, VoLTE and VoWiFi, yes, because those services run on the IMS and there is no shortcut around the signaling.

How does wholesale MVNO pricing compare to retail?

Wholesale rates are the carrier’s own cost base plus a thin margin, usually quoted per subscriber, per minute or per megabyte. Retail rates sit far higher because they include the host operator’s brand, distribution, support and margin. The gap between the two is the MVNO’s gross margin, and it narrows quickly if you underprice termination or overshoot your support and marketing costs.

How long does it take to launch a voice MVNO?

Four to nine months on a hosted core, and nine to eighteen months for a full MVNO with your own HLR, HSS and network code. The software is rarely the delay. Number assignment, interconnect agreements and interop certification consume most of the calendar.

What is the biggest cost after the platform fee?

Per-minute termination, once voice is in the mix. Data costs scale with consumption and is easier to meter. Voice costs scale with your own success, and low ASR routes mean you pay for minutes that never completed a call.

Can a wholesale MVNO platform be multi-tenant?

Most commercial platforms are, which lets you launch several brands on one IMS core and one commercial agreement. Dedicated deployment is also available where a regulator or the host operator requires physical separation. Confirm the isolation model for tariffs and reporting before you commit.

Next Steps

The fastest way to test a vendor is to ask for live per-minute rates on your top five destinations, then measure ASR and CLI on a trial trunk before you sign anything. That single test tells you more about the commercial relationship than any slide deck.

Request current wholesale route rates and a trial trunk