Water usage is the metric that gets far less attention than PUE, yet it matters enormously in water-stressed regions where a facility’s cooling design has real community impact.
There is a quiet shift happening in how organisations think about where their infrastructure lives. What was once a purely technical decision now sits squarely on the boardroom agenda, and for good reason.
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.
The factors that actually move the needle
Headline pricing is the least reliable basis for comparison. Two facilities quoting similar rates can differ enormously once you account for power redundancy, cross-connect fees, remote-hands rates, and the small print around escalations and renewals.
Tier classification tells you what a facility was designed to do, not how well it is run. A well-operated Tier III site routinely outperforms a poorly managed Tier IV one on the metric that matters: real-world availability.
A practical way to evaluate
Then shortlist on objective data and validate with your own eyes. Marketplace intelligence is excellent for narrowing the field quickly, but a site visit and a couple of reference calls will tell you things no datasheet can.
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.
What good looks like in practice
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.
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.
A short checklist before you sign
- Clarify remote-hands response times and what is included versus billed separately
- Confirm the certifications your industry and customers actually require
- Total the full cost of ownership, including the fees that hide in the small print
- Leave headroom for growth, including higher-density racks down the line
- Request recent incident reports, not just a summary uptime percentage
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.