Skip to content
DataCentersExposed
County data-center profile

St. Louis County, Missouri

DataCentersExposed tracks 4 AI data centers in St. Louis County, Missouri — 2 operating and 1 in the pipeline, drawing 12 MW of reported power demand, led by Prime Data Centers. Its transparent data-center risk score is 0/100.

Sources: Methodology, Coverage scorecard

Facilities
4
Operating
2
Pipeline
1

Reporting by · Updated May 29, 2026

Risk breakdown
7Low
  • Project exposure · 12
  • Power demand · 0
  • Water draw · n/a
  • Land footprint · n/a
Overview

What's happening in St. Louis County

Facilities here with disclosed capacity draw 12 MW from the local grid. Data-center load on this scale is the single biggest driver of recent capacity-market price increases — costs that flow through to every ratepayer in the service territory, not just the operators.

Prime Data Centers has the largest presence in St. Louis County. We resolve project codenames and shell LLCs back to the corporate parent wherever the public record allows, so the table below names who is actually behind each site.

Below: every tracked facility in the county, the active state legislation that names it or its county, and local news. Commissioner vote records arrive in a later release; the placeholders show where that accountability data will land.

4 facilities

Every tracked facility

FacilityOperatorStatusMW
Tierpoint Data Center
St. Louis
Proposed
Netrality Data Centers
Saint Louis
Prime Data CentersOperating12
1831 Chestnut Condominium Data Center
St Louis
Operating
Genome Data Center
Saint Louis
Prime Data CentersMapped (unverified)
Accountability

County commissioners

How the St. Louis County board votes on each data-center matter — the rezonings, the abatements, the water permits — is built from public-meeting minutes and roll-call records. Know of a vote we should be tracking? Tell us.

Methodology & sources

The risk score weights project exposure (40%), power demand (30%), water draw (15%), and land footprint (15%). Water and land are not yet measured for our facilities, so those arcs render as "not yet measured" and the weights are renormalized over the factors we can source today — when the data lands, the score updates.

Every row carries a confidence level (high / medium / low) and a source URL. Spot an error? Tell us.