Salt Lake City Data Centers & Colocation — Compare 4 Facilities
Salt Lake City is a practical Mountain West colo market when you need Utah / Intermountain presence, deliverable cabinet or cage capacity, and multi-facility competition on power (kW), density, and interconnect—without defaulting to a single-building tour. DatacenterHunter currently indexes 4 facilities from 2 providers in Salt Lake City. To rent space here, define your cabinets + committed IT kW + go-live date + must-have carriers/cloud on-ramps, then collect side-by-side proposals so you compare usable power and contract terms—not brochure MRCs.
What Salt Lake City buyers typically procure
Salt Lake City attracts regional enterprise production, Mountain West hybrid-cloud edge, software and services platforms, and buyers who want Utah presence without assuming every West deal belongs in Denver or Silicon Valley. Treat Salt Lake City as a procurement geography—verify the specific building and hall that can energize your kW on your date. With 4 facilities from 2 providers, facility choice exists—but provider competition is thinner than primary metros; many commercial RFPs wisely bid Salt Lake City and Denver on the same sheet for power headroom and price tension.
| Procurement lever | What to lock in writing |
|---|---|
| Space | Cabinets, cage, or suite; adjacent expansion rights |
| Power | Usable IT kW, max kW/rack, ready-for-service date, overage rules |
| Cooling | Hall density support (air vs higher-density options) |
| Interconnect | Carriers present, cloud on-ramps, cross-connect fees/lead times |
| SLA | Power/cooling measurement, exclusions, credits, incident RCA |
| Contract | Term, escalator, renewal, early exit, remote-hands rates |
Providers and inventory snapshot (live directory)
From DatacenterHunter's Salt Lake City index (counts can change as inventory updates): 4 facilities / 2 providers. Providers represented include DataBank and Flexential (facility counts vary by operator; as indexed on DatacenterHunter). Directory signals include multiple cooling types and 4 cloud on-ramp signals across the market as indexed—confirm at the building you award.
Browse the live facility list on this page's inventory module, then filter by power and connectivity when you submit /get-started. For operator context, also see /providers.
How to shortlist Salt Lake City facilities for an RFP
1. Freeze the commercial requirement
Use the colocation RFP checklist so every bidder answers the same commercial sheet.
- Initial cabinets / U and 24-month growth
- Total IT kW and sustained kW per rack
- Redundancy expectation (what fails closed for your app, not a marketing Tier slogan)
- Hard interconnect requirements (named carriers, AWS/Azure/GCP-style on-ramps)
- Compliance evidence needed (SOC 2, ISO, PCI, HIPAA, HITRUST, or similar)
- Contract target go-live with buffer for cross-connects and hardware
2. Qualify usable power and date first
Ask every bidder:
Power-first qualification prevents winning a cheap cabinet you cannot energize. With 4 facilities across 2 providers, shortlists are focused. Freeze requirements early, qualify usable power and date per hall, and run a parallel Mountain West bid (Salt Lake City + Denver) if you need more operator diversity, cage scale, or price tension.
- Is quoted kW usable IT load in the named hall today, or contingent on utility/build milestones?
- What is the installed max sustained kW/rack with cooling already in place?
- Contractual ready-for-service date and remedies if it slips?
- How is overage billed?
3. Score interconnect like a line item
Salt Lake City deals often mix Intermountain WAN pathing, hybrid cloud, and regional user-proximity designs. Confirm building-level (not metro-level) carrier diversity, meet-me practices, cloud on-ramp presence, and cross-connect MRC/NRC. Directory signals include 4 cloud on-ramp options as indexed—confirm at the building you award. A lower space fee loses quickly if interconnect is slow or exclusive.
4. Normalize TCO across competing providers
Convert each proposal to $ / usable kW / month over the full term, including power method, cross-connects, remote hands, NRC/cage build, escalator, and renewal. Use the pricing calculator at /pricing-calculator to structure assumptions, then replace estimates with live quotes. Method detail is in the colocation pricing guide.
Ready to rent colo in Salt Lake City?
Tell us cabinets, kW, and timing. We match Salt Lake City facilities from our directory and return competing provider quotes—free for commercial buyers. For thin provider shortlists, say so on intake—we can expand the bid geography, including a parallel Denver bid.
Primary quote path: /get-started. Expert consult for cages, high-density, or multi-site: /consult.
Salt Lake City pricing: how commercial quotes are built
Expect bids to combine space (per cabinet or cage footprint), power (reserved kW and/or metered usage—method matters), cross-connects (per connection to carriers or cloud), and remote hands (included vs hourly).
A four-facility, two-provider index supports hall-level competition—but expect interconnect and power deliverability to dominate TCO, and expand to Denver when you need more operator tension. Do not invent a city-average $/kW for Salt Lake City. Do not sign on a single unnormalized MRC. Run multi-provider pricing via /get-started.
If part of the stack may stay in public cloud, clarify colo vs cloud scope before you issue the RFP.
Power, density, and cooling guidance for Intermountain halls
Salt Lake City RFPs fail most often when buyers assume Denver- or Bay Area-scale power and interconnect richness applies locally. Separate reserved IT kW from sustained kW per rack the named hall can cool today. Ask whether expansion kW is contracted in this building or only metro capable. Confirm circuit/PDU limits and overage method in writing. If you need larger cages, higher density, or broader provider competition, bid Denver in parallel from day one.
Map redundancy to your failure mode—not a marketing Tier badge. Background only: Tier 3 vs Tier 4.
SLA and contract terms Salt Lake City renters should negotiate
Parallel negotiation with finalists preserves leverage. For complex paper, use /consult.
| Term to negotiate | Why it matters for renters |
|---|---|
| Power/cooling SLA measurement | Credits only help if the metric matches how you fail |
| Maintenance exclusions | Chronic planned windows can erase uptime claims |
| Escalator floor/cap | Drives year 3-5 TCO more than month-1 MRC |
| Renewal pricing mechanic | Avoid open-ended then-current list renewals |
| Expansion rights | Adjacent kW at known commercial terms beats a mid-term re-RFP |
| Remote-hands rates | After-hours and expedited rates belong in the MSA |
| Exit / de-install | Migration overlap and cage restoration costs |
When Salt Lake City is the right rent decision
When Salt Lake City is not enough alone (deeper multi-operator West competition, or West Coast cloud gravity), still bid it as a production, DR, or edge option—and keep Denver on the same commercial sheet. Multi-market RFPs are normal.
- You need Salt Lake City / Mountain West latency or local ops presence
- You want multi-facility competition across the four indexed buildings—not a single-building walkthrough
- Hybrid designs need documented cloud on-ramps and carrier choice at the building
- You will compare Salt Lake City against Denver and other West markets for scale, power, and TCO
Buyer checklist before you request quotes
Then submit once at /get-started so providers answer the same commercial sheet.
- Cabinets + kW + density band
- Go-live window
- Must-have carriers / cloud on-ramps
- Compliance list
- Preferred term length
- Single-market vs multi-market bid (Salt Lake City + Denver recommended when the shortlist needs more provider diversity or power headroom)
Request quotes
Primary CTA: get free Salt Lake City colo quotes at /get-started. Ask for a parallel Denver bid when the two-provider shortlist is too thin. Complex deals: /consult. General questions: /contact-us.
Support Guides
Providers in Salt Lake City
Facilities in Salt Lake City
Connectivity & Carrier Ecosystem
Available Carriers
Cloud On-Ramps
Pricing Considerations for Salt Lake City
Colocation pricing in Salt Lake City depends on several factors including power density, space requirements, connectivity needs, and contract length. Typical components of a colocation bill include:
Power
Billed per kW of reserved or actual usage
Space
Per cabinet or per square foot
Cross-connects
Per connection between carriers or providers
Remote Hands
Hourly rate for on-site technical support