Governing a hybrid estate across on-premises, colocation, and cloud requires decisions about workload placement that are as much organisational as technical.
Ask ten infrastructure leaders how they choose a data center and you will get ten different answers. Yet beneath the variety, the same handful of questions tend to decide the outcome.
Why it matters now
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.
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.
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.
Connectivity richness is frequently underweighted. A carrier-neutral facility with a dense ecosystem of networks and direct cloud on-ramps can save more over a contract term than a modest difference in the rack rate ever will.
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.
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.
Where buyers get it wrong
Treating tier level as a proxy for reliability is a common shortcut that backfires. Design tier describes redundancy on paper; actual uptime depends on maintenance discipline, staffing, and how the facility has behaved under real incidents.
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.
A short checklist before you sign
- Ask what happens operationally when a single system fails, not just what the tier rating implies
- Clarify remote-hands response times and what is included versus billed separately
- Write down your power, space, and connectivity needs before you talk to anyone
- Request recent incident reports, not just a summary uptime percentage
- Ask for real uptime history, not just the design tier
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.