What Per-U Colocation Actually Costs in 2026 vs. Renting a Full Cabinet

Per-U colocation costs $30–$75 per rack unit per month in most Tier III facilities, while a full cabinet runs $400–$1,200/month depending on power density and market. The right choice depends almost entirely on how many U you're filling and whether your growth trajectory justifies locking in cabinet-level spend. Here's how the math actually breaks down.

Why the Base Rate Is Never the Whole Story

The number providers quote first — "starting at $X/U" — is the rack space charge. It's real, but it's not what you pay. By the time you add power, bandwidth, cross-connects, and remote hands, your actual invoice looks different.

Here's what a realistic per-U deployment looks like versus a full cabinet at a mid-tier facility in 2026:

At 4U, per-U wins by nearly $500/month. But watch what happens when you scale up.

At 20U, that same per-U math produces $1,000 in space charges alone — and you're now over the cabinet minimum before you add power and connectivity. At 25–30U, you're paying cabinet-equivalent rates for less physical control, less dedicated power, and shared airflow. That's the crossover point where most operators should be looking at a full cabinet.

What Changes When You Move to a Full Cabinet

A dedicated cabinet isn't just more space. The operational differences matter.

Power is cleaner. Per-U deployments typically share a power circuit with other tenants in the same cabinet or cage. You get an allocation — say, 1.5A per U at 208V — but you're not the only draw on that whip. A dedicated cabinet comes with your own 20A or 30A circuits, dual-fed from separate PDUs. If you're running anything that cares about power quality or need to actually measure your draw precisely, shared circuits create noise in that data.

Airflow is yours to manage. In a shared cabinet, you don't control blanking panel discipline for the U slots above and below yours. Someone else's poor cable management becomes your hot-aisle problem. In a dedicated cabinet, you own the thermal environment end-to-end.

Physical security is categorically different. Per-U space in a shared cabinet means the cabinet lock protects everyone's gear, not just yours. For regulated workloads — HIPAA, PCI, federal — auditors often want to see dedicated physical access controls. A locked cabinet with its own key management satisfies that requirement in a way shared space doesn't.

A Real Scenario: Healthcare SaaS Startup

A healthcare SaaS company came to us running 6U of gear at a larger regional provider — two application servers, a database server, and a small storage array. They were paying $780/month all-in. Not terrible, but the contract was 36 months and the remote hands rate was $150/hour with a two-hour minimum.

We moved them to 6U at IDACORE Boise. Space, power, and bandwidth came to $490/month on a 12-month term. Remote hands at $75/hour, no minimum. Same physical redundancy specs — N+1 UPS, N+1 cooling, SOC 2 Type II and HITRUST CSF certifications that their HIPAA compliance program actually requires.

That's $290/month in savings, a shorter commitment, and a support model where someone who knows their rack picks up the phone. Over 12 months, that's $3,480 back in their budget.

They're not filling a cabinet yet. When they get to 18–20U, we'll have a different conversation about moving to dedicated space. That's how this should work — right-size the deployment to the actual footprint, not to what a sales rep needs to hit quota.

The Hidden Cost That Kills Per-U Economics: Egress

This applies more to cloud-adjacent deployments than pure colo, but it comes up constantly. If you're pulling significant data out of your colo environment — to end users, to cloud services, to backup targets — bandwidth pricing structure matters as much as the per-U rate.

Hyperscalers charge $0.08–$0.12/GB for egress. At scale, that's not a rounding error. Colocation providers typically sell bandwidth as a committed port speed (1Gbps, 10Gbps) with either a flat monthly rate or a 95th-percentile billing model. No per-GB surprises.

At IDACORE Boise, bandwidth pricing is flat. You know what you're paying in January and in August when your traffic spikes. That predictability has real value when you're building a budget — and it's one of the reasons the "30–40% less than AWS" comparison holds up when you include egress in the hyperscaler number.

When Per-U Colocation Is the Right Answer

Don't let the cabinet math talk you into more than you need. Per-U colocation is genuinely the right choice when:

• You're running 1–15U of gear with no near-term expansion planned
• You need a physical presence for compliance, latency, or data residency reasons but don't have the volume to justify dedicated space
• You're building a disaster recovery node — a small footprint in a geographically separate facility that sits mostly idle but needs to be there
• You're testing a new market or use case before committing to a larger deployment

That last point is underused. If you're evaluating whether to build a regional presence in Boise or Coeur d'Alene, starting with 2–4U lets you validate the latency, test the support model, and understand your actual power draw before you sign a cabinet contract. We'd rather have you start small and grow than sign a 3-year cabinet deal you'll regret.

IDACORE North in Coeur d'Alene is specifically positioned for this — DR nodes and regional redundancy for companies in the Spokane corridor and eastern Washington who need a facility about 45 minutes away from their primary site. A 2U DR target costs almost nothing to maintain and gives you genuine geographic separation without a full cabinet commitment.

Frequently Asked Questions

How much does per-U colocation cost in 2026?
Per-U colocation typically runs $30–$75/U/month depending on facility tier, power included, and cross-connect costs. A 2U server in a Tier III facility with 1–2A of power usually lands between $60–$150/month all-in. Budget facilities in secondary markets like Boise run toward the lower end of that range without sacrificing redundancy.

When does renting a full cabinet make more sense than per-U colocation?
A full cabinet makes financial sense once you're consistently filling 20–25U or more, or when your density requirements exceed what shared-cabinet power circuits support. At that point, per-U rates aggregate past the cabinet minimum. You also gain dedicated power whips, independent cooling airflow, and physical security isolation that shared space can't match.

What's included in per-U colocation pricing?
It varies by provider, but standard inclusions are rack space, a power allocation (usually 1–2A at 120V or 208V per U), and physical access. Cross-connects, remote hands, IP addresses, and bandwidth are almost always add-ons. Always ask for a fully loaded quote — the base rate is rarely what you actually pay.

Is per-U colocation available with no long-term contract?
Most enterprise data centers require 12–36 month terms even for single-U deployments. IDACORE Boise offers per-U colocation starting at 1U with 12-month standard terms — shorter than the 36-month minimums common at larger providers. Some providers offer month-to-month at a significant premium, typically 20–40% above term pricing.

How does Boise colocation pricing compare to Seattle or Portland?
Boise colocation runs 30–40% less than comparable space in Seattle or Portland, driven by lower power costs (Idaho Power commercial rates around $0.055/kWh versus $0.08–0.12/kWh in the Pacific Northwest coastal markets) and lower real estate overhead. You get the same carrier diversity and redundancy specs at materially lower operating cost, with sub-5ms latency to Treasure Valley businesses.

If you want a fully loaded quote — space, power, bandwidth, cross-connects, the real number — talk to us about your specific deployment at IDACORE Boise or IDACORE North. We'll tell you whether per-U or a dedicated cabinet makes more sense for your footprint, and we won't push you toward more than you need.