Data Centre Business Models
Executive Summary
Key Takeaways
- ✓ Wholesale colocation, retail colocation, hyperscale build-to-suit, enterprise/captive, and managed services each tie revenue to a different underlying mechanism, and require a genuinely different financial model architecture rather than a single template adapted with different rates.
- ✓ Retail colocation revenue is diversified across many smaller tenants billed per rack or per kW; hyperscale build-to-suit revenue is typically a single long-dated contracted cash flow from one anchor tenant, inverting the tenant concentration profile.
- ✓ Enterprise/captive data centres are frequently modelled as an internal cost centre with chargeback rather than an external revenue-generating asset, which changes the model's objective from revenue maximisation to cost efficiency and internal capital allocation.
- ✓ An operator running multiple business models simultaneously should model each revenue stream's mechanism separately, since blending them obscures which business line is actually driving performance and risk.
Objective¶
This guide sets out the distinct data centre business models within Data Centre Financial Modelling, and how the financial model architecture appropriate to each differs.
Wholesale and Retail Colocation¶
Wholesale colocation leases large, dedicated space or power blocks (typically 250kW and above, or a full suite/cage) to a relatively small number of tenants under multi-year contracts. Retail colocation leases smaller units, individual racks or partial-rack space, to a larger, more diversified tenant base, typically billed per rack or per kW of committed power. See Colocation Financial Models for the shared revenue mechanics underlying both.
Hyperscale Build-to-Suit¶
A facility developed and leased to a single large cloud or technology tenant under a long-dated (often ten-plus year) contract, typically structured around a committed capacity delivery schedule. Revenue is a single, long-dated contracted cash flow, concentrating counterparty credit risk in one tenant rather than diversifying it across many, an inversion of the retail colocation risk profile. See Hyperscale Data Centre Models.
Enterprise and Captive Data Centres¶
Facilities an organisation builds and operates for its own internal IT use rather than leasing to external tenants. These are typically modelled as an internal cost centre with chargeback to business units, where the objective is cost efficiency and internal capital allocation rather than external revenue maximisation. See Enterprise Data Centre Models.
Managed Services¶
Some operators layer IT infrastructure management, monitoring, and hands-on remote technical support on top of the physical facility lease, generating an additional service fee revenue stream distinct from, and typically higher-margin per unit than, the underlying space and power lease revenue. A model should separate managed services fee revenue from core colocation revenue given their different margin profiles and cost drivers.
Modelling Multi-Model Operators¶
Many operators run more than one business model simultaneously, for example a wholesale colocation portfolio alongside a hyperscale build-to-suit development pipeline. Each revenue stream's mechanism should be modelled separately rather than blended into one composite revenue assumption, since blending obscures the operator's actual risk exposure across arrangements that respond to genuinely different drivers.
Common Construction Pitfalls¶
Retail-style per-tenant churn assumptions applied to a hyperscale anchor tenant. A hyperscale build-to-suit facility's revenue risk is concentrated counterparty credit risk, not diversified tenant churn, and modelling it with a retail churn rate misrepresents the actual risk.
Blended multi-model revenue. Combining wholesale, retail, hyperscale, and managed services revenue into a single growth assumption conceals which business line is actually driving performance.
Enterprise/captive facilities modelled as revenue-generating assets. Projecting external market rate revenue for a facility with no third-party tenants overstates the asset's actual economic contribution.
Recommended Practices¶
- Identify each revenue stream's underlying business model before selecting a modelling approach.
- Model hyperscale build-to-suit revenue through contracted cash flow and counterparty credit risk, not diversified tenant churn.
- Model enterprise/captive facilities as an internal cost centre with chargeback, not an external revenue asset.
- Keep each business model's revenue stream separable in a multi-model operator's consolidated model.
Continue Reading¶
Related Pillars¶
Related Technical Guides¶
Related Industries¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
What are the main data centre business models?
Wholesale colocation (large, dedicated space or power blocks leased to a small number of tenants), retail colocation (smaller space or rack units leased to many tenants), hyperscale build-to-suit (a facility developed and leased to a single large cloud or technology tenant under a long-dated contract), enterprise/captive (a facility an organisation builds and operates for its own internal use), and managed services (the operator also provides IT infrastructure management on top of the physical facility).
Why does the business model matter to financial model architecture?
Because each model ties revenue, contract tenor, and tenant concentration to a fundamentally different driver, and a model built for one mechanism will misrepresent revenue and risk if applied to an operator actually running a different one.
How does hyperscale build-to-suit differ from retail colocation in revenue structure?
Hyperscale build-to-suit revenue is typically a single, long-dated contracted cash flow from one anchor tenant, concentrating counterparty credit risk. Retail colocation revenue is diversified across many smaller tenants billed per rack or per kW, trading concentration risk for greater churn and utilisation risk.
How should an enterprise/captive data centre be modelled differently from a commercial operator?
As an internal cost centre with chargeback to business units, where the modelling objective is cost efficiency and internal capital allocation rather than external revenue maximisation, since there is no third-party tenant revenue to project.
How should a model handle an operator running multiple business models at once?
By modelling each revenue stream's mechanism separately, wholesale and retail colocation revenue, hyperscale contracted revenue, and managed services fees, rather than blending them into one composite revenue assumption that obscures the operator's actual risk exposure across the different arrangements.
References
Related Articles
Data Centre Financial Modelling
Data centre financial modelling is the discipline of modelling a data centre operator's revenue, cost, and capital structure from its capacity-denominated drivers, power, space, and cooling capacity, rack density, and tenant contract structure, rather than the generic market-price and headcount-growth drivers used in most corporate models, or the pure occupancy-and-lease-term drivers of conventional commercial real estate. This page is the hub for the Knowledge Centre's data centre financial modelling content: how colocation, hyperscale, and enterprise business models each require a distinct model architecture, how rack revenue and occupancy are decomposed into their separable underlying drivers, and how capacity planning and financial KPIs tie the model together, as this domain expands to cover operations, revenue, investment, and governance practice across the sector.
Colocation Financial Models
Colocation financial models project revenue from a diversified base of tenants leasing space and power in defined units, per rack or per kW of committed capacity, rather than a single anchor contract. This guide sets out how colocation revenue is decomposed into space/power revenue, cross-connect and ancillary fees, and how occupancy, pricing, and churn assumptions should be modelled as separable drivers rather than a single blended revenue-per-tenant figure.
Hyperscale Data Centre Models
Hyperscale data centre models finance a facility developed and leased to a single large cloud or technology tenant under a long-dated contract, structured around phased, capacity-denominated capex drawdown rather than a single completion event. This guide sets out how to model phased delivery, contracted revenue recognition, and the concentrated counterparty and power availability risks distinctive to this business model.
Enterprise Data Centre Models
Enterprise, or captive, data centres are facilities an organisation builds and operates for its own internal IT use rather than leasing to external tenants. This guide sets out how to model this business model as an internal cost centre with chargeback to business units, and how to structure the build-versus- colocate-versus-cloud capital allocation decision that increasingly frames enterprise data centre investment.
Financial Model Audit for Data Centres
Data centre financial models sit between real estate and infrastructure modelling conventions: phased, capacity-driven capex drawdown funds build-to-suit or colocation facilities, while power procurement and pass-through mechanics, and long-dated tenant or hyperscale offtake agreements, determine the revenue and cost structure. Power availability and cost pass-through in particular is a mechanic that does not appear in standard commercial real estate models. This page sets out the modelling risks specific to data centres, the audit findings that recur in build-to-suit and colocation financings, and what lenders typically expect before extending development or acquisition debt.