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

July 17, 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.

Behind every application your customers touch sits a physical building full of power, cooling, and fibre. The choices made about that building quietly shape performance, cost, and risk.

Where buyers get it wrong

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.

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.

Planning for what comes next

Whatever you commit to today, leave yourself room to grow. The right partner offers a clear path from a single rack to a private suite, and from standard density to liquid-cooled high-density halls, without forcing a migration.

Term length is a lever worth pulling thoughtfully. Longer commitments unlock materially better rates and, increasingly, priority access to scarce capacity — but only commit ahead if you are confident in the trajectory.

Why it matters now

The market has split in two. Standard enterprise workloads still run comfortably at three to five kilowatts a rack, while accelerated-compute deployments are pushing twenty, fifty, even a hundred kilowatts. Those two worlds are priced and provisioned very differently, and conflating them is a common and expensive mistake.

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 good looks like in practice

The best partnerships look less like a vendor relationship and more like a shared roadmap — regular capacity reviews, early visibility into expansion options, and a provider that flags risk before it becomes your problem.

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

  • Write down your power, space, and connectivity needs before you talk to anyone
  • Ask for real uptime history, not just the design tier
  • Map the network ecosystem: carriers, internet exchanges, and cloud on-ramps
  • Read the exit and renewal terms as carefully as the price
  • Ask what happens operationally when a single system fails, not just what the tier rating implies

The bottom line

The teams that get this right are rarely the ones with the most resources — they are the ones who asked better questions earlier in the process.

← Back to Insights