Understanding Colocation Pricing: Per-kW vs Per-Rack — Updated for 2026 (20) — Updated for 2026 (20)

July 26, 2026 · By Data Hall Insights Team

Colocation pricing rarely lines up cleanly across providers, because the headline rate is only one line in a bill shaped by cross-connects, power draw, remote hands, and renewal terms.

The economics of data center capacity have changed faster in the last two years than in the previous decade. Anyone evaluating their options today is working in a genuinely different market.

Why it matters now

Power has overtaken floor space as the binding constraint in most primary markets. Vacancy rates have fallen to record lows, and the practical effect is that capacity — particularly high-density capacity — increasingly needs to be reserved well ahead of when you actually need it.

What used to be a commodity is now a strategic asset class. When supply is tight, the question stops being simply how much it costs and becomes whether you can secure it at all, on terms that let you grow.

A practical way to evaluate

Model the whole cost, not the monthly line. Setup fees, cross-connects, bandwidth, growth headroom, and exit terms all belong in the comparison. The cheapest rack rate is rarely the cheapest deployment.

Start with requirements, not providers. Pin down your power per rack, total committed capacity, connectivity needs, and the compliance regimes you answer to. That single page of clarity will shape every conversation that follows.

Where buyers get it wrong

The most expensive mistake is optimising for the number everyone sees — the monthly rack rate — while ignoring the numbers nobody asks about until the invoice arrives: cross-connects, remote hands, power overage, and renewal escalators.

Underestimating growth is more common than overestimating it. Teams that lock in exactly what they need today frequently find themselves negotiating from a weaker position twelve months later, once the facility has less spare capacity to offer.

What good looks like in practice

The strongest operators are transparent by default — uptime history, incident reports, and maintenance schedules are available without a special request. That openness is itself a signal worth weighing.

Good facilities make the boring things boring: predictable billing, clear escalation paths, and remote-hands requests that get done on the timeline promised, not the timeline hoped for.

A short checklist before you sign

  • Ask for real uptime history, not just the design tier
  • Write down your power, space, and connectivity needs before you talk to anyone
  • Map the network ecosystem: carriers, internet exchanges, and cloud on-ramps
  • Leave headroom for growth, including higher-density racks down the line
  • Ask what happens operationally when a single system fails, not just what the tier rating implies

The bottom line

None of this is complicated, but it does reward diligence. The organisations that treat infrastructure procurement as a discipline rather than a purchase consistently end up with better facilities, better terms, and fewer surprises.

← Back to Insights