Why Colocation Contracts Cost More Than the Rack Rate Suggests

The rack rate looks reasonable. You do the math, it pencils out, and you start thinking about move-in timelines. Then the contract arrives and you realize the number you were quoted was more of a starting point than a price.

This happens constantly in colocation. Not because providers are being deceptive — though some are — but because colo pricing has a lot of moving parts, and most sales conversations only cover one of them. If you're evaluating colocation for the first time, or you're re-evaluating a current contract, here's what actually drives your total cost of ownership.

Power Is Priced Multiple Ways, and They Stack

The rack rate typically covers a power allocation — say, 2kW or 4kW per rack. What it often doesn't tell you upfront is how that power is metered and billed once you're live.

Some facilities charge a flat rate for your allocated draw. Others charge for actual consumption. Some charge for both — a base allocation fee plus overage if you exceed it. And then there's the power usage effectiveness (PUE) multiplier, which some contracts apply to your metered consumption to account for cooling and facility overhead. A PUE of 1.4 means you're effectively paying for 40% more power than your servers actually use.

Here's what that looks like in practice: a customer running 8kW of actual server load in a facility with a 1.4 PUE and $0.12/kWh power costs is billed for 11.2kW. At 720 hours a month, that's roughly $966/month just in power — before the rack fee, cross-connects, or anything else. If they were quoted a rack rate of $500/month, they're already at $1,466 before the contract is fully read.

Ask the provider to show you a sample invoice from a current customer with a similar power profile. If they won't, that tells you something.

Cross-Connects Are a Revenue Center, Not a Utility

Cross-connects — the physical cables that connect your equipment to a carrier, an internet exchange, or another customer's cage — are almost always billed separately, and the fees are almost always higher than they should be.

A typical fiber cross-connect runs $100-$300/month per connection at most facilities. If you're connecting to two carriers for redundancy plus a managed firewall in a separate cage, you're looking at $300-$900/month in cross-connect fees alone. That's before you've sent a single packet.

Installation fees compound this. Many facilities charge $200-$500 per cross-connect to physically run the cable, on top of the monthly recurring charge. If you're building out a new environment with six or eight connections, that's a meaningful upfront cost that doesn't show up in the rack rate conversation.

The providers who've been doing this a long time — the ones who built their own networks rather than reselling someone else's — tend to have more reasonable cross-connect pricing because they understand what the actual cost of a cable run is. The ones treating cross-connects as a profit center are usually resellers marking up infrastructure they don't control.

Remote Hands Isn't Free, and You'll Need It

Every facility offers remote hands — technicians who can physically interact with your equipment when you're not on-site. Every facility also charges for it, usually by the hour, and the rates vary wildly.

$150/hour is common. $250/hour exists. Some contracts include a small monthly allotment (one hour, maybe two) and charge overage rates after that. Some charge a minimum of one hour even for a five-minute task.

Think about what you actually need remote hands for: rebooting a hung server, swapping a failed drive, reseating a cable, escorting a vendor. These are routine operational tasks. If you're running a production environment in a colo facility, you'll need remote hands at least a few times a year — probably more. Budget $1,500-$3,000 annually as a baseline and adjust based on your team's proximity to the facility and how hands-on your hardware management is.

The proximity point matters more than people admit. A facility 85 miles from your office is a different operational calculation than one 850 miles away. When you're close enough to drive out for a critical issue, remote hands becomes a convenience rather than a necessity. When you're across the country, it's your only option and the pricing leverage shifts entirely to the provider.

Contract Terms Lock In More Than the Price

Colocation contracts are typically 12-36 months, and the renewal terms deserve as much attention as the initial pricing. Auto-renewal clauses with 60-90 day cancellation windows are standard. Miss the window and you're committed for another full term at whatever rate the provider decides to charge.

Escalation clauses are the other thing to read carefully. Many contracts include annual price increases tied to CPI or a fixed percentage — 3-5% is common. On a $3,000/month contract, a 4% annual escalator means you're paying $3,120 in year two, $3,245 in year three. Over a three-year term, that's real money.

Then there's the question of what happens when you need more space. Expansion rights — the ability to add cabinets or power at your current rate — aren't guaranteed unless they're written into the contract. Facilities that are near capacity will happily add you at market rate when you need to grow, which may be significantly higher than what you signed at.

Get expansion rights in writing. Get the escalation cap in writing. Get the cancellation notice window in writing and put it in your calendar the day you sign.

Bandwidth Pricing Deserves Its Own Section

Some colo facilities include bandwidth in the rack rate. Most don't, or they include a small amount and charge heavily for overages.

The pricing models vary: 95th percentile billing, flat monthly per-Mbps rates, commit-and-overage structures. Each has implications depending on your traffic patterns. Bursty workloads get punished by 95th percentile billing. Steady high-volume workloads often do better on a flat per-Mbps rate. If you're running a CDN node or a media platform, the difference between these models can be $2,000-$5,000/month on the same actual traffic.

If the facility is also your ISP — meaning they have their own ASN, their own peering relationships, and they're not just reselling transit — you have more room to negotiate and the pricing is usually cleaner. They know what their bandwidth actually costs because they're buying it at the wholesale level. Resellers are marking up someone else's capacity and have less flexibility.

This is one of the places where operator-owned infrastructure makes a real difference. We've been running BGP routing tables and managing peering relationships since the ISP days — we know what transit actually costs and we price accordingly. There's no markup on a markup.

What a Realistic TCO Calculation Looks Like

Take a single cabinet deployment as an example. You've been quoted $800/month for the rack.

Here's what the full picture might look like:

Rack fee (4kW allocation):     $800/month
Power overage (6kW actual):    $240/month
PUE adjustment (1.35):         $108/month
Cross-connects (3x @ $150):    $450/month
Bandwidth (500Mbps commit):    $400/month
Remote hands (avg 2hr/month):  $300/month

Total:                       $2,298/month

That's nearly three times the quoted rack rate. Not because anyone lied — every one of those line items is legitimate. But the rack rate conversation covered one of seven cost drivers.

The question to ask any colo provider isn't "what's your rack rate?" It's "can you show me the total monthly cost for a deployment with these specific parameters?" If they can't or won't answer that question with a detailed breakdown, you haven't found the right provider yet.

What to Ask Before You Sign

A few specific questions that will tell you a lot about a provider:

• What's your PUE and how is it applied to billing?
• What are your cross-connect installation and monthly recurring fees?
• What's included in the remote hands rate and what's the minimum billing increment?
• Is bandwidth included, and if so, what's the model and overage rate?
• What are the escalation terms and what's the cancellation notice window?
• Do I have expansion rights at current rates, and for how long?

A provider who answers these questions clearly and completely, without hedging, is a provider who's confident in their pricing. Vague answers or "we'll work that out in the contract" are flags.

Idaho data center options are more limited than the coasts, which means some providers here have historically been able to get away with opaque pricing simply because there weren't many alternatives. That's changing. If you're evaluating colocation in the Treasure Valley or anywhere in the Pacific Northwest, you have more leverage than you might think — use it.

---

If you're putting together a real TCO analysis for a colocation deployment in Idaho, we'll walk through it line by line with you — power draw, connectivity requirements, remote hands expectations, all of it. That's a conversation we've had hundreds of times and we'd rather have it before you sign somewhere else than after. Start that conversation with us at /#contact.