Compare Service Models
Four paths. One MVNX Link foundation.
Start with how you want to operate. Each model uses the same MVNX Link foundation with a different level of ownership, integration and support.
At a Glance
How the models differ.
Exact responsibilities, integrations and included services are confirmed during discovery.
| What to compare | MaaS | Independent MVNO | MVNE | API Access |
|---|---|---|---|---|
| Best suited for | Fast, guided MVNO launches | Operators running their own MVNO model | Scaled or multi-brand operators | Developers and custom platforms |
| Who operates it? | MVNX Link foundation | Customer-led with MVNX Link support | Customer-defined operating model | Customer-built experience |
| Connectivity | MVNX Link connectivity | MVNX Link or customer-provided | Flexible | Integration-dependent |
| Platform & billing | Included foundation | Configurable | Configurable | Integrate through APIs |
| Customer experience | Included | Customer-led or MVNX-supported | Customer-defined | Customer-built |
| Implementation | Guided | Consultative | Solution architecture | Technical integration |
Capabilities shown are directional. Final responsibilities, integrations and included services depend on the agreed engagement scope.
MaaS Implementation Options
Two ways to launch with MaaS.
Same platform. Choose the level of hands-on support.
Explore MaaSSelf-Configured
Build through a guided workspace.
Configure your business, brand, plans and launch requirements in MVNX Link.
Managed Standalone
Bring the model. We coordinate implementation.
MVNX Link manages configuration and coordinates ongoing changes with your team.
Not sure which model fits?
Tell us what you’re building. We’ll use the exploration call to understand your requirements and identify the appropriate engagement model.