Where the data centers want to go, what the grid can actually carry, and how the queue is moving. Each region rolls up live capacity factor, queue position depth, fuel-mix exposure, and per-market headroom — the same data every site-selection deal needs.
255 GW of data center requests in Oncor territory alone — 8x system peak. Severe dilution expected under Batch Zero. South Texas and the Plains offer unconstrained alternatives.
Northern Virginia hosts 70%+ of US hyperscale capacity. PJM Cycle 1 launches 2026 with reformed interconnection. Ohio, Indiana, and West Virginia emerge as overflow markets with lower capacity prices.
MISO South and SPP absorb developers priced out of Texas and PJM. Abundant wind + gas, low land costs, and growing transmission capacity make these the next frontier.
California grid constraints and wildfire risk push developers to Phoenix, Las Vegas, and Reno. Solar abundance but transmission bottlenecks define the Western corridor.
Georgia, Tennessee, and the Carolinas offer nuclear baseload, low rates, and aggressive incentives. TVA and Southern Company actively court hyperscale with dedicated power programs.
DC Hub grid intelligence is the live operational picture of every U.S. interconnection
across the seven major ISOs and balancing authorities — PJM, ERCOT, CAISO, MISO,
NYISO, ISO-NE, and SPP. For each region we surface three things that matter to
anyone underwriting a data center build: interconnect queue depth (how
many GW of new generation and load are waiting on grid studies), capacity
factor and fuel mix (where the marginal MWh actually comes from), and
real-time headroom (the gap between current load and firm capacity, which
governs whether a hyperscale tenant can land 200 MW in the next study cycle).
The same per-ISO signals flow into the Data Center Power Index
(DCPI), the daily 0–100 score that ranks 200+ U.S. markets on whether
they're BUILD, CAUTION, AVOID, or LOW_SIGNAL. If
you're going site-by-site, jump to a specific market on the
markets index — every market page links back to its
serving ISO so the energy-intelligence and site-selection views stay in sync.
For agents, the same data is exposed as JSON at /api/v1/grid-intelligence
and through the DC Hub MCP server.