St. Louis Data Centers & Colocation
St. Louis is a Midwest / Central US colo market when you need St. Louis, Missouri presence, deliverable cabinet or cage capacity, and local ops proximity—but as indexed today it is a 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 2 facilities from 1 provider in St. Louis. 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 (St. Louis plus sibling markets) so you compare usable power and contract terms—not brochure MRCs.
What St. Louis buyers typically procure
St. Louis attracts Midwest enterprise production, healthcare and financial platforms, manufacturing and logistics workloads that need St. Louis / Missouri presence, and buyers who want Central US ops without flying every change window to Chicago—yet the live index is a single-provider, two-facility market. Treat St. Louis as a procurement geography—verify the specific building and hall that can energize your kW on your date. Because DatacenterHunter indexes one provider across 2 facilities, you may get hall-to-hall choice inside that operator—but you do not get in-city multi-provider competition. Do not run a single-operator tour as your only bid path: expand to Chicago or Kansas City (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 St. Louis index (counts can change as inventory updates): 2 facilities / 1 provider. Provider represented: TierPoint (2 facilities as indexed on DatacenterHunter). Directory signals include multiple cooling types and 1 cloud on-ramp signal as indexed—confirm building-level presence, LOA timelines, and fees before 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 St. Louis 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: St. Louis + Chicago + Kansas City
2. Qualify usable power and date first
Ask every St. Louis (and parallel hub) bidder:
Power-first qualification prevents winning a cheap cabinet you cannot energize. 2 facilities under one operator can still offer hall-to-hall choice—but without a second provider in-city, usable power and contract terms need Chicago or Kansas City 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
St. Louis 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. The directory shows 1 cloud on-ramp signal as indexed—that is not a substitute for a named building LOA plan. Do not assume Chicago, Kansas City, or Memphis carrier richness equals every St. Louis 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 St. Louis + Chicago / Kansas City / Memphis. Method detail is in the colocation pricing guide.
Ready to rent colo in St. Louis (or nearby hubs)?
Tell us cabinets, kW, and timing. We match St. Louis facilities from our directory and—when single-provider competition requires it—expand to Chicago / Kansas City / Memphis for competing provider quotes—free for commercial buyers.
Primary quote path: /get-started. Expert consult for cages, high-density, or multi-site: /consult.
St. Louis 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 St. Louis. 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 Midwest / Central US halls
St. Louis 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 Chicago or Kansas City 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 St. Louis renters should negotiate
Parallel negotiation with Chicago or Kansas City finalists preserves leverage even when St. Louis 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 |
| Multi-building options | With one operator, hall choice and expansion paths matter more |
When St. Louis is the right rent decision
When St. Louis is not enough alone (only 2 facilities 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: Chicago, Kansas City, Memphis, Louisville, Indianapolis, and Cincinnati.
- You need St. Louis, Missouri / Midwest latency or local ops presence
- You accept a single-provider city and will still bid Chicago or Kansas City for competition
- Hybrid designs need documented cloud on-ramps and carrier choice at the building
- You will compare St. Louis against Chicago / Kansas City / Memphis 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 — St. Louis + Chicago + Kansas City (single-provider city)
Support Guides
Providers in St. Louis
Facilities in St. Louis
Connectivity & Carrier Ecosystem
Cloud On-Ramps
Pricing Considerations for St. Louis
Colocation pricing in St. Louis 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