Colocation vs. Hyperscale Financial Models
Executive Summary
Key Takeaways
- ✓ Colocation models are driven by diversified multi-tenant occupancy, pricing, and churn; hyperscale models are driven by a single anchor tenant's contracted, take-or-pay revenue, requiring genuinely different revenue recognition and risk assessment approaches.
- ✓ Colocation revenue risk is statistically diversified tenant churn and utilisation risk; hyperscale revenue risk is concentrated single-counterparty credit and early-termination risk, an inverted risk profile between the two.
- ✓ Capacity delivery in colocation is typically incremental and portfolio-managed against observed leasing velocity; capacity delivery in hyperscale is typically a small number of large, contractually defined tranches.
- ✓ An operator running both business models should model each with its own architecture rather than a single consolidated occupancy-and-rate assumption that would misrepresent both segments' actual economics.
Overview¶
Colocation and hyperscale build-to-suit financial models both fall within Data Centre Financial Modelling, but differ fundamentally in tenant concentration, revenue mechanism, and capacity delivery structure, extending the models covered in Colocation Financial Models and Hyperscale Data Centre Models.
Side-by-Side Comparison¶
| Dimension | Colocation | Hyperscale Build-to-Suit |
|---|---|---|
| Tenant base | Diversified, many tenants | Concentrated, typically one anchor tenant |
| Revenue mechanism | Per-rack/per-kW billing, occupancy-driven | Single long-dated take-or-pay contracted cash flow |
| Primary revenue risk | Diversified tenant churn and utilisation | Concentrated counterparty credit and early termination |
| Capacity delivery | Incremental, portfolio-managed | Small number of large, contractually defined tranches |
| Occupancy tracking granularity | High (by tenant, density tier) | Lower (single or few tenants) |
| Contract tenor | Typically shorter, more variable | Typically long-dated (ten-plus years) |
Why the Two Require Different Architectures¶
A colocation model's revenue is a function of diversified occupancy, pricing, and churn across many tenants; a hyperscale model's revenue is a function of a single contracted offtake agreement's terms and the anchor tenant's credit quality. Applying a colocation-style diversified churn assumption to a hyperscale facility, or vice versa, misrepresents the actual risk driver each business model carries.
Modelling a Multi-Model Operator¶
An operator running both colocation and hyperscale segments should model each with its own architecture rather than a single consolidated occupancy-and-rate assumption, consistent with the multi-model discipline described in Data Centre Business Models, since blending the two would misrepresent both segments' genuinely different economics and risk profiles.
Continue Reading¶
Related Technical Guides¶
Related Pillars¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
What is the primary revenue mechanism in each model?
Colocation revenue is diversified across many tenants, billed per rack or per kW of committed capacity with associated churn risk. Hyperscale revenue is typically a single long-dated, take-or-pay contracted cash flow from one anchor tenant, protecting revenue regardless of the tenant's actual utilisation pace.
How does tenant concentration risk differ between the two?
Colocation carries diversified, statistically modelled tenant churn risk across many smaller tenants. Hyperscale carries concentrated single-counterparty credit and early-termination risk in one anchor tenant, an inverted risk profile requiring a fundamentally different downside scenario approach.
How does capacity delivery differ between colocation and hyperscale developments?
Colocation capacity is typically delivered incrementally and managed as a portfolio against observed leasing velocity across many tenants. Hyperscale capacity is typically delivered in a small number of large, contractually defined tranches tied to a single tenant's offtake schedule and often subject to contractual delivery date obligations.
Which model requires more granular occupancy and churn tracking?
Colocation, since its revenue depends on tracking occupancy, pricing, and churn across a diversified, potentially large tenant base by density tier. Hyperscale requires less granular occupancy tracking but more rigorous single-counterparty credit monitoring given its concentrated exposure.
How should an operator running both business models structure its consolidated model?
By modelling each segment with its own architecture, diversified occupancy-and-churn for colocation, contracted-cash-flow-and-counterparty-risk for hyperscale, rather than a single consolidated occupancy-and-rate assumption that would misrepresent both segments' genuinely different economics.
Related Articles
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.
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.
Data Centre Business Models
Data centre operators run under several structurally different business models, wholesale colocation, retail colocation, hyperscale build-to-suit, enterprise/captive, and managed services, each of which ties revenue, contract tenor, and capital intensity to a different mechanism. This guide sets out how each business model's revenue and cost mechanism differs and, correspondingly, how the financial model architecture appropriate to each differs, since applying a retail colocation-style model to a hyperscale build-to-suit facility, or vice versa, misrepresents the operator's actual revenue and risk exposure.