Boise Data Centers & Colocation
Boise is an Idaho / Mountain West commercial colo market when you need Boise, Idaho presence, deliverable cabinet or cage capacity, and local ops proximity—but as indexed today it is a single-facility, single-provider city with limited in-metro competition, so commercial buyers should plan parallel bids to nearby enriched hubs for real price and interconnect tension. DatacenterHunter currently indexes 1 facility from 1 provider in Boise. 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 (Boise plus sibling markets) so you compare usable power and contract terms—not brochure MRCs.
What Boise buyers typically procure
Boise attracts Treasure Valley enterprise production, healthcare and media platforms, regional SaaS and hybrid designs that need Boise presence without defaulting every bid to Salt Lake City or Denver—yet the live index is a single-facility, single-provider market (the thinnest primary-metro inventory tier on DatacenterHunter). Treat Boise as a procurement geography—verify the specific building and hall that can energize your kW on your date. Because DatacenterHunter indexes one provider across 1 facility, you do not get in-city multi-provider competition or multi-building choice inside Boise—parallel hub bids are required for commercial tension. Do not run a single-operator tour as your only bid path: expand to Salt Lake City or Denver (and siblings) on the same commercial sheet.
| 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 Boise index (counts can change as inventory updates): 1 facility / 1 provider. Provider represented: ValorC3 (1 facility as indexed on DatacenterHunter). Directory signals include multiple cooling types and Various cloud on-ramp signals as indexed—confirm at the building you award (do not treat Various as a counted inventory figure).
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 Boise facilities for an RFP
1. Freeze the commercial requirement
Before any sales call, write:
Use the colocation RFP checklist so every bidder—across cities—answers the same commercial sheet—especially compliance evidence common to healthcare, financial, and regulated buyers.
- 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, etc.)
- Contract target go-live with buffer for cross-connects and hardware
- Explicit multi-market flag: Boise + Salt Lake City + Denver
2. Qualify usable power and date first
Ask every Boise (and parallel hub) bidder:
Power-first qualification prevents winning a cheap cabinet you cannot energize. Only 1 facility under one operator means no in-city hall-to-hall alternative—without a second provider in-city, usable power and contract terms need Salt Lake City / Denver / Phoenix tension to stay commercial. Expand geography from day one.
- 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
Boise deals often mix local user proximity, regional WAN pathing, and hybrid cloud. Confirm building-level (not metro- or provider-nationwide) carrier diversity, meet-me practices, cloud on-ramp presence, and cross-connect MRC/NRC. Directory on-ramp signals are Various as indexed—not a substitute for a named building LOA plan. Do not assume larger hub markets' carrier richness equals every Boise hall.
4. Normalize TCO across competing providers (expand geography)
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 spanning Boise + Salt Lake City / Denver / Phoenix. Method detail is in the colocation pricing guide.
Ready to rent colo in Boise (or nearby hubs)?
Tell us cabinets, kW, and timing. We match Boise facilities from our directory and—when single-provider competition requires it—expand to Salt Lake City / Denver / Phoenix for competing provider quotes—free for commercial buyers.
Primary quote path: /get-started. Expert consult for cages, high-density, or multi-site: /consult.
Boise 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 single-provider city index means brochure MRCs are especially misleading—normalize TCO against at least one nearby multi-provider hub before you award. Do not invent a city-average $/kW for Boise. Do not sign on a single unnormalized MRC. Run multi-provider (multi-market) 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 Idaho / Mountain West halls
Boise RFPs fail most often when buyers assume larger-hub power and interconnect availability applies to every local hall. 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 deeper cloud gravity or broader competition, bid Salt Lake City or 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 Boise renters should negotiate
Parallel negotiation with Salt Lake City / Denver / Phoenix finalists preserves leverage even when Boise is the preferred geography. 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 re-RFP mid-term |
| Remote-hands rates | After-hours and expedited rates belong in the MSA |
| Exit / de-install | Migration overlap and cage restoration costs |
| Expansion / multi-market options | With one facility, adjacent kW rights and parallel-hub bids matter more |
When Boise is the right rent decision
When Boise is not enough alone (only 1 facility under one operator, or deeper multi-provider competition elsewhere), still bid it as a production, DR, or edge option—multi-market RFPs are normal. Compare sibling markets: Salt Lake City, Denver, Phoenix, Las Vegas, Albuquerque, and San Jose.
- You need Boise, Idaho / Treasure Valley / Mountain West latency or local ops presence
- You accept a single-facility, single-provider city and will still bid Salt Lake City or Denver for competition
- Hybrid designs need documented cloud on-ramps and carrier choice at the building
- You will compare Boise against Salt Lake City / Denver / Phoenix for scale, interconnect, 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
- Multi-market bid required — Boise + Salt Lake City + Denver (single-provider city)
Support Guides
Providers in Boise
Facilities in Boise
Pricing Considerations for Boise
Colocation pricing in Boise 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