Colocation pricing can feel oddly inconsistent. Two facilities in the same metro can quote wildly different numbers, and sometimes the difference isn’t the building—it’s the revenue model behind the quote.
If you’re searching for a straightforward explanation of colocation pricing per kW vs per rack, start here: the pricing model is less about how the contract is “named” and more about what the provider is optimizing for (space utilization vs power utilization).
This comparison breaks down per‑kW vs per‑rack pricing, how colocation MRC vs NRC typically shows up on quotes, what utilization does to your effective rate, and how wholesale vs retail colocation pricing behaves at different deal sizes. All pricing in this post is illustrative benchmark ranges, not a quote.
Key Takeaway: If you can’t restate a colo quote as “$/kW of committed capacity (plus adders),” you can’t compare it.
Quick comparison matrix (colocation pricing per kW vs per rack)
Dimension | Per rack / cabinet pricing | Per‑kW pricing |
|---|---|---|
What you’re really buying | A space “container” (rack/cabinet) with some bundled power | A power capacity commitment (kW) with space as a wrapper |
Best fit | Smaller footprints; stable low/medium-density loads; easier budgeting | Medium-to-large footprints; dense compute; buyers who want price aligned to capacity |
Common billing shape | One MRC line item (rack package) + adders | MRC as (committed kW × $/kW) + adders |
Utilization risk | Often hidden: you can under-use the included power and still pay full MRC | Explicit: under-utilization means higher effective $/used‑kW |
Overage risk | Can be punitive if you exceed included kW/amps | Usually defined (extra kW blocks, metered kWh, or step-ups) |
Negotiation levers | Included kW, included cross-connects, remote hands hours, install waivers | $/kW, volume tiers, term, step-up schedule, power factor / metering details |
Definitions you’ll see in quotes
MRC (Monthly Recurring Charge): the predictable monthly bill (space/power/ports/managed services).
NRC (Non‑Recurring Charge): one-time fees (install, cross-connect setup, shipping/handling, build-out).
kW (kilowatt): power capacity. In colo, you usually commit to a maximum capacity (kW) even if energy is later metered.
kWh (kilowatt-hour): energy consumed over time. Some models bill energy (kWh) on top of capacity commitments.
Cross-connect: a physical connection (fiber/copper) inside the data center to a carrier, cloud on-ramp, or another tenant. These recurring charges are sometimes discussed under colocation cross connect fees.
Blended rate: shorthand for “all-in effective price” after you normalize MRC + recurring adders into $/kW.
Where the money is in colo (data center colocation pricing models)
Colo economics are constrained by two hard ceilings:
Power capacity (how much electrical + cooling the facility can deliver)
Sellable space (racks/cabinets/cages)
In many modern builds, power is the scarcer resource long before floor space is. That’s why you’ll often see pricing that “wants” to be expressed as $/kW of committed capacity, even if the quote is packaged “per rack.”
Typical recurring revenue components:
Space: cabinet/rack/cage
Power: committed kW, circuits, redundancy level (A/B feeds)
Interconnection: cross-connect MRCs
Services: remote hands, monitoring, managed firewalls, etc.
Benchmark ranges by region (illustrative; deal-size sensitive)
Two caveats before you use any benchmark:
Benchmarks swing with deal size, term length, metro supply, and density.
“Per‑kW” numbers can mean different things (included vs pass-through power, metered vs flat-rate, and what’s bundled).
Indicative retail vs wholesale $/kW/month (capacity commitment)
The table below uses public benchmark reporting and should be treated as directional. Brightlio’s analysis of wholesale asking rates in primary North American markets cited roughly $195.94/kW/month for 250–500 kW requirements (H2 2025) and noted much higher pricing in Singapore in some scenarios; see Brightlio’s colocation pricing overview. Umbrex also summarizes market-level ranges and emphasizes the deal-size effect; see Umbrex’s data center economics primer.
Region (example) | Retail / small footprints (indicative) | Wholesale (≈250–500kW+, indicative) | What usually drives the spread |
|---|---|---|---|
North America (primary metros) | ~$200–$350/kW/mo | ~$160–$220/kW/mo | tight capacity, interconnection value, term, density |
North America (secondary metros) | ~$150–$280/kW/mo | ~$120–$190/kW/mo | cheaper land/power, more expansion headroom |
Europe (select metros) | ~$200–$380/kW/mo | ~$150–$260/kW/mo | power cost volatility, tax/regulatory structure |
APAC (select metros) | ~$250–$500+/kW/mo | ~$200–$350+/kW/mo | land constraints, power pricing, import/logistics, demand |
⚠️ Warning: Don’t use a $/kW benchmark unless you confirm what’s included (power pass-through, cooling, redundancy, cross-connects, remote hands).
Per-rack packaged pricing (why it’s hard to compare)
Per-rack pricing varies so much because the “rack” often bundles a hidden power allowance.
As one public example set (provider-specific, not market-wide), Brightlio notes packaged rack pricing examples and RU pricing ranges on its colocation pricing page.
A practical way to normalize a per‑rack quote:
Ask: What kW is included in the rack MRC?
Then compute: Normalized $/kW = rack MRC ÷ included kW
Example normalization (illustrative):
Packaged rack MRC | Included kW | Normalized $/kW/month |
|---|---|---|
$1,200/mo | 4 kW | $300/kW/mo |
$1,200/mo | 6 kW | $200/kW/mo |
$1,200/mo | 8 kW | $150/kW/mo |
MRC vs NRC breakdown (what’s usually recurring vs one-time)
Every provider has its own quote format, but most line items map cleanly into recurring vs one-time.
Quote line item | Usually MRC | Usually NRC | Notes |
|---|---|---|---|
Cabinet / rack / cage | ✓ |
| May bundle power and a port |
Power capacity (committed kW) | ✓ |
| Sometimes shown as circuit MRCs |
Metered energy (kWh) | ✓ |
| Often appears as pass-through or index-based |
Cross-connect (monthly) | ✓ |
| Often per connection |
Cross-connect install |
| ✓ | One-time setup is common |
Remote hands / smart hands | ✓ / usage |
| Can be hourly or bundled |
Shipping/receiving |
| ✓ | Especially for first installs |
Build-out / cage construction |
| ✓ | Larger footprints |
Security deposit |
| ✓ | Sometimes refundable |
Practical quote hygiene:
If the quote includes a “rack” line, ask whether it includes power, PDUs, or a port.
If power is “metered,” confirm whether there is still a capacity commit (often yes).
If cross-connects matter to your design, treat them as a first-class part of your TCO model. Umbrex notes cross-connects as a meaningful revenue stream and summarizes typical charges in its primer.
Utilization sensitivities (the yield math)
The most common mistake in comparing pricing models is ignoring utilization.
When you buy committed capacity, your effective cost depends on how much of that capacity you actually use.
A simple normalization:
Effective $/used‑kW ≈ (Monthly recurring charges tied to capacity) ÷ (Average used kW)
Scenario: 4 kW committed, $220/kW/month, different utilization
Assumptions (illustrative):
Commit: 4 kW
Rate: $220/kW/mo
Capacity MRC: 4 × $220 = $880/mo
Utilization (avg used kW ÷ committed kW) | Avg used kW | Effective $/used‑kW |
|---|---|---|
40% | 1.6 kW | $550/used‑kW |
60% | 2.4 kW | $367/used‑kW |
80% | 3.2 kW | $275/used‑kW |
95% | 3.8 kW | $232/used‑kW |
What this means operationally:
If your deployments are spiky (staging environments, DR, bursty workloads), a strict per‑kW commit can look expensive on an “effective” basis.
If you’re running consistently dense compute, per‑kW pricing tends to align more cleanly with what constrains the facility.
Wholesale vs retail scenarios (three quote archetypes)
These aren’t hard rules, but they’re useful mental models when you sanity-check a quote.
1) Retail: 1–5 racks
Common characteristics:
Per-rack or small kW blocks
Higher $/kW because the provider has more overhead per customer
Bundling is common (cabinet + a power cap + a port)
What to negotiate:
Included power (kW) per rack
Included cross-connect(s)
NRC waivers for installs
2) Mid-market: 20–100 kW
Common characteristics:
Transition zone where pricing may “flip” from rack to kW
More room for structured adders and service catalogs
What to negotiate:
Volume tiers for $/kW
Step-up schedule if you’ll expand
Clear overage terms (extra kW blocks vs metered kWh)
3) Wholesale: 250–500 kW+
Common characteristics:
Explicit per‑kW pricing, longer terms
More sophisticated power and interconnection terms
Tighter attention to utilization and growth commitments
What to negotiate:
Ramp plan (e.g., 250 kW now, 500 kW in 12 months)
Metering method and pass-through rules
SLA clarity and maintenance windows
How to choose the right model for your project
Use these questions to pick a model (or at least force quote comparability):
Is power your binding constraint or is space?
If you’re above ~6–8 kW per rack, you’ll likely want a quote that makes power explicit.
How variable is your utilization?
If you expect low utilization early, negotiate a step-up schedule or smaller initial commits.
Do you need predictable chargeback for client projects?
SIs and distributors often prefer quote structures that can be passed through cleanly.
How important is interconnection?
If you need many cross-connects, treat them as a core part of the model—not an afterthought.
Is your density likely to change over the term?
If you might move from 4 kW to 12 kW racks (AI/HPC, consolidation), avoid contracts that punish density transitions.
Neutral benchmark table example (Coolnetpower)
Coolnetpower isn’t used here as a price claim—only as a neutral example of how you might structure a benchmark comparison table for an internal quote pack.
Relevant solution pages (architecture context):
Example: benchmark-ready quote sheet layout (illustrative ranges)
Line item | Per rack quote might show… | Per‑kW quote might show… | Benchmark notes (illustrative) |
|---|---|---|---|
Space | Rack/cabinet MRC | Included (or a cabinet fee) | Normalize to included kW to compare |
Power capacity | Included up to X kW | Y kW × $/kW | For NA wholesale 250–500 kW, directional benchmarks have been reported in the ~$160–$220/kW/mo band (varies by metro/term) |
Cross-connects | Included 0–1, then adders | Explicit per cross-connect MRC | Cross-connect MRCs can be material; confirm per-connection pricing and install NRC |
NRCs | “Install” + “setup” | “Install” + “cross-connect install” | Treat NRCs as separate; don’t average them into $/kW without term context |
Remote hands | Hourly or bundled | Hourly or bundled | Clarify what counts as billable time and minimum increments |
Pro Tip: If you’re building a client-facing comparison pack, standardize on three normalized outputs: (1) $/committed‑kW/month, (2) $/used‑kW/month at expected utilization, and (3) all-in first-year cost (MRC×12 + NRC).
Next steps: make rack and kW quotes comparable (RFP checklist)
If you only copy one thing from this post, copy this checklist into your RFP or quote request:
Confirm committed kW and whether power is flat-rate or metered.
If pricing is per rack, confirm included kW per rack and overage terms.
List every recurring adder separately: cross-connects, ports, managed services.
List every one-time NRC separately: install, cross-connect setup, build-out.
Ask for the ramp plan if you’ll scale (and how pricing changes at each tier).
Confirm redundancy level (A/B feeds, UPS/generator design) and any SLA implications.
If you want, I can turn this into a one-page “quote normalization worksheet” you can hand to providers and use across bids.
