A separate integration per partner works for three MVNOs. At ten it is the constraint, and an MVNE architecture is what removes it.
Reviewed by Alexander Donskoy, Sales Director, Avante · Last reviewed 2026-09
Avante MVNx Suite is the platform architecture: delivered three times for enablers, and available to MNO wholesale teams and aggregators. What separates the two is not the software. It is whether the tenth partner costs what the third one did.
Bilateral
Host network
One MVNE platform
MVNE platform — one integration to the host
Host network
Each MVNO has its own interconnect, its own operational interface into your OSS and its own escalation path. Fine for a handful of partners. Beyond that the operating cost grows in step with the partner count, and so does the queue for your engineering team.
SIM management, catalogue, charging, billing, interconnect and operational support run centrally, with tenant isolation. Onboarding becomes a configuration exercise, and wholesale revenue can grow without the operating cost growing with it.
You hold the bulk wholesale agreement with the host and re-wholesale capacity to smaller operators on your platform, with tiered pricing and settlement per tenant. In practice it is the enablement layer with a wholesale business on top.
The real choice for a wholesale team is between managing each partnership as a direct relationship and running an enablement function on shared infrastructure. That is what separates operators with three MVNO partners from those with twenty. On the platform you can offer partners a light or medium model on your terms and keep the network interfaces under your control, while each partner still gets its own catalogue, branding, self-care and data. If a partner later wants its own BSS, the migration is planned rather than improvised, because it is the same Avante stack.
A new operator is a configuration job: brand, catalogue template, numbering block, SIM/eSIM inventory, channels, users and roles. It is cloned from a template and adjusted rather than built.
Each tenant owns its plans, bundles, promotions and reward rules within limits you set, plus white-label self-care, an app and its own customer communications.
Real-time OCS and convergent billing per tenant on shared infrastructure, or dedicated instances where a tenant's security or regulatory model requires it.
Usage is rated against your host agreement and against each tenant's wholesale tariff. Settlement, revenue share and reconciliation with every tenant and with the host run automatically.
Tenants connect their own systems through the same open API. They also get a tenant portal for products, subscribers, orders and reports, and a seller portal for their dealers.
Number portability, KYC and SIM registration, statutory reporting and lawful-interception hand-off handled per operator under one operating model.
Data isolation between tenants, role-based access and a full audit trail. Banks, public bodies and regulators ask about this first.
An MVNA buys capacity from the host in bulk under one agreement and re-wholesales it to several smaller operators (brands, communities, regional players) that would not get host terms on their own. On Avante the MVNA runs on the enablement platform above, with the wholesale business modelled on top:
Enablers compete on what their tenants can sell. Standard enablement platforms tend to leave out the following; Avante includes them:
Sponsored billing, where a company pays an agreed part of an employee's usage and the rest is billed to the individual. Limits by employee and group, allocated accounts and reporting, private APN. Delivered for Brilliantel's B2B and B2G MVNO in South Africa.
Purchase events, points and partner offers configured as reward rules in the product catalogue, so a retail or bank tenant can run its loyalty proposition without custom development.
When a tenant needs more control than enablement allows, it moves to a Medium MVNO on the same Avante stack. That is a planned migration, not a re-platforming.
3
MVNE platform deployments
15
live MVNOs on Avante
multi-host
one BSS across several host networks
150M+
subscriber load proven in testing
LANCK Telecom
Europe and Africa
Multi-market BSS rollout covering MVNO launches, charging and billing, and interconnect management across several European and African markets, on one operational backbone.
Brilliantel
South Africa
Enterprise-focused MVNO with billing models for B2B and B2G that standard MVNE setups do not provide, delivered under an OPEX-based model.
VENTAmobile
EU
Platform stack for an operator offering sponsored roaming, multi-IMSI, M2M and eSIM to partners and enterprises.
An MVNE provides the platform and operations that MVNOs run on: BSS/OSS, SIM management, interconnect, support. An MVNA is a wholesale intermediary. It buys capacity from the host in bulk and re-sells it to smaller MVNOs, usually on an MVNE platform. Many enablers do both; on Avante the MVNA layer is the wholesale and settlement business modelled on top of the enablement platform.
No. Avante supplies and, if you wish, operates the BSS/OSS for your enablement business. The network, the host agreements and the tenant relationships are yours.
The platform is multi-tenant by design, with subscriber load proven at 150M+ in testing. In practice the limit is set by your host capacity and your operations model rather than by the BSS.
From a tenant template. Brand, catalogue, numbering, SIM/eSIM inventory, channels and users are configured, the tenant's own systems connect through the Avante API, and the tenant goes through pilot and launch on your standard process. It is configuration and testing work rather than a development project.
Contractually, the licensed operator, which is your tenant. Technically, tenant data is isolated on the platform with role-based access and an audit trail. You see the wholesale and settlement view; the tenant sees its subscribers.
Yes. A digital sub-brand is a tenant like any other, with its own catalogue and channels, running on the same charging and billing as the partner MVNOs.
The same interfaces as a single MVNO (provisioning, online charging, mediation, SMSC/USSD, SIM/eSIM, MNP, settlement), connected once and shared by all tenants. For an MNO running its own enablement, these are internal interfaces.
A working session with our MVNE architecture team covers your partner pipeline, your host interfaces and your operating model. You leave with a tenant onboarding process you can quote to partners.
