Cloud Enabler / VCO Model

The Cloud Enabler / Virtual Cloud Operator (VCO) Model

In short: The Cloud Enabler / VCO model separates cloud infrastructure ownership from service delivery—Cloud Enablers own the infrastructure and locations, whitesky.cloud operates the platform, and VCOs bring cloud services to market under their own brand, inspired by the MVNE/MVNO telecom model.

The Cloud Enabler / Virtual Cloud Operator (VCO) model used by whitesky is inspired by the MVNE / MVNO model from the telecom industry and applies the same separation of responsibilities to cloud infrastructure.

In telecom, Mobile Virtual Network Enablers (MVNEs) own and operate network infrastructure, while Mobile Virtual Network Operators (MVNOs) focus on customer relationships, branding, packaging, and market differentiation—without owning physical network assets.

whitesky applies this proven model to cloud infrastructure.

From MVNE/MVNO to Cloud Enabler/VCOThe telecom model maps onto the cloud. A Mobile Virtual Network Enabler owns and operates the network; in the cloud, the Cloud Enabler, a telco, datacenter or hoster, owns the hardware and the location. A Mobile Virtual Network Operator owns brand, customers and packaging without owning a network; in the cloud, the Virtual Cloud Operator, an MSP, integrator or reseller, owns brand, customers and pricing without owning hardware. In both cases the enabler provides wholesale capacity to the operator.TelecomCloud, with whiteskyMVNEMobile Virtual Network Enablerowns and operates the networkCloud Enablertelco, datacenter or hosterowns the hardware and the locationMVNOMobile Virtual Network Operatorbrand, customers, packagingwithout owning a networkVirtual Cloud OperatorMSP, integrator or resellerbrand, customers, pricingwithout owning hardwarewholesale capacitywholesale capacity
From MVNE/MVNO to Cloud Enabler/VCOThe telecom model maps onto the cloud. A Mobile Virtual Network Enabler owns and operates the network; in the cloud, the Cloud Enabler, a telco, datacenter or hoster, owns the hardware and the location. A Mobile Virtual Network Operator owns brand, customers and packaging without owning a network; in the cloud, the Virtual Cloud Operator, an MSP, integrator or reseller, owns brand, customers and pricing without owning hardware. In both cases the enabler provides wholesale capacity to the operator.The enablerMVNEMobile Virtual Network Enablerowns and operates the networkin the cloud, this becomesCloud Enablertelco, datacenter or hosterowns the hardware and the locationThe operatorMVNOMobile Virtual Network Operatorbrand, customers, packagingwithout owning a networkin the cloud, this becomesVirtual Cloud OperatorMSP, integrator or resellerbrand, customers, pricingwithout owning hardware
Same split as in telecom: the enabler owns the hardware and the location, the operator owns the brand and the customers.

The Cloud Enabler: infrastructure ownership & platform hosting

A Cloud Enabler is responsible for building and operating the physical and foundational cloud infrastructure. This includes:

  • Procuring and installing server, storage, and network hardware
  • Deploying equipment in a datacenter or colocation facility
  • Ensuring power, redundancy, and physical security
  • Providing connectivity, peering, and upstream network access
  • Hosting the whitesky cloud platform on this infrastructure

The Cloud Enabler does not sell cloud services directly to end customers by default. Instead, it provides wholesale cloud capacity and a fully managed cloud platform.

whitesky.cloud operates the whole platform layer for the Cloud Enabler as a managed service, including:

  • platform installation
  • monitoring and lifecycle management
  • updates and upgrades
  • operational best practices

Who replaces failed hardware depends on the agreement between the Cloud Enabler and whitesky.

This allows the Cloud Enabler to focus on infrastructure reliability and scale, rather than building cloud software themselves.

The Virtual Cloud Operator (VCO): market access & service delivery

A Virtual Cloud Operator (VCO) is a reseller or service provider that brings cloud services to market using the Cloud Enabler’s infrastructure and the whitesky platform.

Each VCO receives:

  • its own fully branded cloud portal
  • isolated tenants and resources
  • independent pricing and service catalogs
  • customer and billing ownership

VCOs typically focus on:

  • customer acquisition and relationships
  • vertical-specific solutions
  • managed services and support
  • compliance, consultancy, and value-added services

They do not need to invest in datacenters, hardware, or platform engineering.

This allows smaller MSPs to launch cloud services at scale—similar to how MVNOs launch telecom offerings without owning a mobile network.

Customers page of the VCO admin portal listing a customer with contact, status active, billable yes and standard pricing
The VCO manages its own customers, with their pricing and billing status, in its own branded portal.Shown: portal.dynagrid.tech, the white-label portal of Dynagrid, a VCO running on whitesky.

Clear separation of roles (by design)

ResponsibilityCloud EnablerVirtual Cloud Operator
Hardware & datacenter✔
Network & connectivity✔
Platform operation✔ (with whitesky)
Tenant isolation & security✔
Branding & go-to-market✔
Customer contracts✔
Pricing & packaging✔
Managed services✔

This separation avoids conflicts, simplifies operations, and allows each party to focus on what they do best.

Three roles, each owning one layerCustomers buy cloud under the brand of a Virtual Cloud Operator. The VCO, an MSP, integrator or reseller, owns its brand, its customers and its pricing, with a white-label portal served by Meneja. The Cloud Enabler, a telco, datacenter or hoster, owns the hardware and the physical location, with power, network and connectivity. whitesky.cloud, delivered as a managed service today, owns the software, the cloud stack, control plane and federated billing, and manages the grid.RoleOwnsCustomersbuy cloud under the VCO's brandVirtual Cloud OperatorMSPs, integrators, resellersbrand, customers, pricingwhite-label portal, served by MenejaCloud Enablertelcos, datacenters, hostershardware and the physical locationpower, network and connectivitywhitesky.cloudmanaged service todaysoftware: cloud stack, control planeand federated billing; manages the grid
Three roles, each owning one layerCustomers buy cloud under the brand of a Virtual Cloud Operator. The VCO, an MSP, integrator or reseller, owns its brand, its customers and its pricing, with a white-label portal served by Meneja. The Cloud Enabler, a telco, datacenter or hoster, owns the hardware and the physical location, with power, network and connectivity. whitesky.cloud, delivered as a managed service today, owns the software, the cloud stack, control plane and federated billing, and manages the grid.Customersbuy under the VCO's brandVirtual Cloud OperatorMSPs, integrators, resellersOwns brand, customers, pricing;white-label portal, served by MenejaCloud Enablertelcos, datacenters, hostersOwns hardware and the physicallocation, power and connectivitywhitesky.cloudmanaged service todayOwns the software: cloud stack,control plane, federated billing;manages the grid
Three roles, each owning one layer: the VCO the customer relationship, the Cloud Enabler the hardware and location, whitesky.cloud the software.

Federation-ready by default

Because all Cloud Enablers run the same whitesky platform, multiple Cloud Enablers can be connected into a federated cloud network.

This allows:

  • VCOs to deploy workloads across multiple locations
  • geographic expansion without new infrastructure investments
  • resilience and capacity sharing between Cloud Enablers

A VCO keeps a single contract and billing relation with its own Cloud Enabler. The Cloud Enablers resell capacity to each other, so the VCO can still deploy in all of their locations.

The result is a distributed, sovereign cloud ecosystem, without central lock-in.

Federation-ready by defaultA VCO portal, with one identity and one bill, has a contract and billing relation only with its own Cloud Enabler, A. Cloud Enablers A, B and C resell capacity to each other on the same whitesky platform, so the VCO's workloads can run in the locations of all three while the VCO contracts and pays only its own enabler.VCO portalone identity, one billcontract and invoiceCloud Enabler Bown location and hardwareVMVMCloud Enabler Athe VCO's own enablerVMVMCloud Enabler Cown location and hardwareVMVMCloud Enablers resell capacity to each other, on the same whitesky platformThe VCO's workloads run in every location; it contracts and pays only its own enabler
Federation-ready by defaultA VCO portal, with one identity and one bill, has a contract and billing relation only with its own Cloud Enabler, A. Cloud Enablers A, B and C resell capacity to each other on the same whitesky platform, so the VCO's workloads can run in the locations of all three while the VCO contracts and pays only its own enabler.VCO portalone identity, one billcontract and invoiceCloud Enabler Athe VCO's own enablerCloud Enablers resellcapacity to each otherVMVMCloud Enabler Bown locationVMVMCloud Enabler Cown locationVMVMThe VCO's workloads run in everylocation; it contracts and paysonly its own enabler
The VCO contracts and pays only its own Cloud Enabler. The Cloud Enablers resell capacity to each other, so the VCO’s workloads can run in all of their locations.

Why this model works (especially today)

The Cloud Enabler / VCO model addresses several current market realities:

  • Rising infrastructure costs and hardware complexity
  • MSP consolidation and specialization
  • Demand for sovereign, locally operated cloud solutions
  • Vendor lock-in fatigue from hyperscalers and proprietary stacks

By separating infrastructure ownership from service delivery, whitesky enables scalable cooperation instead of forced consolidation.

Delivery model: managed service

whitesky is delivered to Cloud Enablers as a managed service, ensuring operational quality and fast time-to-market.

A software edition for self-operation is planned, at the earliest in 2027. The Cloud Enabler / VCO structure would remain the same.