What a Colocation Quote Actually Includes (And What It Doesn't)

Most colocation quotes look clean on paper. A monthly rate, a power allocation, maybe a cross-connect fee listed separately. You sign, you ship your gear, and then three months later you're staring at an invoice that doesn't match what you expected.

This isn't always bad faith. Some of it is genuinely how the industry prices services — components that providers treat as separate line items because they are separate infrastructure costs. But some of it is deliberate opacity, and knowing the difference before you sign saves you real money and a lot of frustration.

I've been on both sides of this. We've run our own network infrastructure for 30 years, including operating an ISP with our own ASN and BGP peering at the Seattle Internet Exchange. We've negotiated colocation agreements as customers, and we offer colocation ourselves. So let me walk you through what a quote actually covers, where the gaps typically are, and what questions you should be asking.

---

What the Base Rate Usually Covers

A standard colocation quote is built around three core components: space, power, and cooling. When a provider quotes you a monthly rate for a half-rack or full rack, they're typically including all three of these as a bundle — but the way they're bundled matters.

Space is the simplest. You're renting physical rack units (U) or a full rack, sometimes a cage if you're larger. This part is almost always clearly stated.

Power is where it gets complicated. Most quotes specify a power allocation — say, 20A at 120V, or a certain number of kilowatts. What they don't always make clear is whether that's allocated power or metered power. Allocated means you pay the same rate regardless of actual draw. Metered means you pay for what you use, often with a base rate and then a per-kWh overage. If you're running dense compute, those overages add up fast.

Cooling is almost never broken out separately — it's baked into the per-kW or per-rack rate. But it's worth understanding how your provider handles high-density deployments. If you're running GPU servers or anything that generates serious heat, make sure the cage or row you're in can actually handle the thermal load. Some facilities charge premium rates for high-density zones. Others just... don't have them, which you'll find out the hard way.

---

The Line Items That Don't Show Up in the Headline Rate

Here's where most surprises live.

Cross-connects. If you need to connect to a carrier, a cloud on-ramp, or another tenant in the facility, you'll pay for a cross-connect. These are physical fiber or copper runs inside the data center. Expect $100–$300/month per cross-connect at most facilities, plus a one-time installation fee. If you need three or four of these, that's a meaningful number that wasn't in your headline quote.

Remote hands. You can't always be on-site. When you need someone at the facility to physically touch your gear — reboot a server, reseat a cable, swap a drive — you're paying for remote hands. Rates vary wildly: some providers include a few hours per month, others charge $100–$200/hour with a one-hour minimum. If you're running lean on staff and relying on remote hands regularly, get this number before you commit.

IP addressing. Basic connectivity is often included, but additional IP blocks usually aren't. If you need a /27 or larger, expect to negotiate that separately. IPv4 addresses have real market value right now — providers aren't giving them away.

Bandwidth and transit. This is the one that catches people most often. Some providers include a flat bandwidth commitment (say, 10Mbps or 100Mbps burstable). Others charge on 95th percentile billing, which means your monthly bandwidth cost is based on your peak usage for the month, excluding the top 5% of samples. If you have traffic spikes — even predictable ones — 95th percentile billing can dramatically change your cost model.

At IDACORE, we use flat pricing with no egress surprises. I mention this not as a sales pitch but because it's a genuine differentiator — the "we'll figure out bandwidth later" approach in colocation quotes is where a lot of Idaho companies have gotten burned by providers in larger markets.

Setup and installation fees. One-time fees for provisioning your space, running cables, or initial remote hands assistance are common. They're usually disclosed, but not always. Ask explicitly.

---

The Compliance and Security Layer

If you're in healthcare, finance, or any regulated industry, your colocation needs go beyond the physical. And this is where quotes get really thin.

A data center can be physically secure — badge access, cameras, man-traps — without being HIPAA-capable. HIPAA compliance in a colocation context requires a Business Associate Agreement (BAA) from your provider, documented security controls, audit logging, and a facility that can support your compliance posture. Most commodity colo providers won't sign a BAA. Some don't even know what you're asking for.

SOC 2 Type II certification is another one to watch. A facility might claim they're "SOC 2 compliant" when they mean they've done a readiness assessment, or that they're in the process of certification. There's a real difference between a certified facility and one that's working toward it. Ask for the actual report, not a marketing claim.

We're transparent about where we are on this: IDACORE's infrastructure is built to support HIPAA and SOC 2 requirements, and we're actively working through formal certification. We'll tell you exactly what we have and what's in progress. What we won't do is claim certifications we don't have.

For Idaho healthcare organizations specifically — hospitals, clinics, health tech companies in the Treasure Valley — data residency is often a compliance requirement, not just a preference. Your data staying in Idaho isn't just a selling point; for some organizations it's a legal necessity. That's worth confirming explicitly in any colocation agreement.

---

A Real Scenario: What the Numbers Look Like

A regional healthcare IT company came to us after running colocation at a facility in the Pacific Northwest. Their headline rate was competitive — about $800/month for a full rack. But when we looked at their actual invoices, the real number was closer to $1,400/month once you added cross-connects to their cloud provider, 95th percentile bandwidth overages from their backup jobs, and remote hands charges for after-hours support.

We quoted them a full rack at IDACORE with flat bandwidth included, two cross-connects to their existing carriers, and a remote hands package that covered their typical usage. Total: $1,050/month. Same hardware, same connectivity profile, more predictable billing.

The other thing that changed: latency. Their applications were hitting their Oregon-based colo at 20–35ms from Boise. From our Weiser facility, they're under 5ms to the Boise metro. For their clinical applications, that difference was noticeable to end users.

---

Questions to Ask Before You Sign

Don't treat a colocation quote as a final number. Treat it as a starting point for a conversation. Here's what I'd ask every provider:

• Is power allocated or metered? What are the overage rates?
• How is bandwidth billed — flat, burstable, or 95th percentile?
• What's the per-hour rate for remote hands, and is there a monthly minimum?
• What does a cross-connect cost, and what carriers are already in the facility?
• Will you sign a BAA? Do you have SOC 2 Type II certification?
• What's the process if I need to scale — add a half-rack, add power?
• What's the SLA for power uptime, and what's the actual remediation if you miss it?

That last one matters more than people realize. A 99.9% uptime SLA sounds good until you read the fine print and discover that the remedy is a credit equal to one day's service fee. That's not a real guarantee; it's a legal formality.

---

What Transparent Pricing Actually Looks Like

A quote you can trust is one that gives you the all-in number, not the headline rate. It should tell you what's included in bandwidth, how power overages work, what remote hands costs, and what compliance documentation is available.

It should also come from someone who can answer technical questions directly — not route you through a sales process to get a straight answer about 95th percentile billing or BGP options.

If you're evaluating colocation for an Idaho-based operation and want to compare what you're currently paying (or being quoted) against what a local, operator-run facility actually costs, talk to our team about a line-by-line quote comparison. Bring your current invoice. We'll tell you exactly what the same setup costs here, and where the differences are.