Compute
Virginia sits at the center of the global compute economy. This page is a strategic placeholder while direct data-center signals — planning-commission approvals, SCC large-load filings, and Dominion IRP commentary — are ingested to replace the residential-broadband proxy currently feeding the score.
Compute is the new electricity
Compute has become a strategic resource. Artificial intelligence, cloud services, financial infrastructure, and increasingly the industrial base all depend on where — and how fast — new data-center capacity can be brought online.
Virginia already houses the densest hyperscale footprint on Earth. The next decade will be decided less by whether new campuses can be built and more by whether the power, water, fiber, and public consent to build them can be assembled in the same jurisdiction, at the same time.
Four questions frame the Compute pillar as we ingest direct signals:
- Where is compute capacity located today?
- How quickly can it expand — in months, not years?
- What infrastructure (power, water, fiber, workforce) supports it?
- Who controls access — hyperscalers, colocation operators, sovereign clouds?
Virginia's compute corridors
The densest concentration of hyperscale capacity on the planet. Dark-fiber depth and cloud on-ramps remain unmatched.
Constraint —Transmission congestion, substation queues out to 2028+, and rising community friction on new by-right approvals.
PW Digital Gateway and Innovation Park expansions position the county as Ashburn's overflow valve — same fiber ring, cheaper land.
Constraint —Zoning battles, Manassas Battlefield adjacency, and the same PJM interconnection bottleneck as Loudoun.
Meta and QTS anchor a second-mile campus corridor served by MAREA/BRUSA subsea cable landings at Virginia Beach.
Constraint —Requires new 500-kV build-out and workforce depth beyond current utility contractor pipeline.
Site-ready industrial parks with rail, river water, and proximity to the Richmond fiber core — attractive for AI training clusters.
Constraint —Water-cooling permit path and BESS siting policy still being written at the county level.
Cheap land, developer optionality, and rail spurs create a Richmond-to-Fredericksburg AI corridor if power and water follow.
Constraint —No hyperscale anchor yet; power delivery timeline is the gating question.
Signals we are wiring into the score
| Signal | State | Note |
|---|---|---|
| PJM interconnection queue | Constrained | Multi-year backlog for new large loads across DOM zone |
| Dominion large-load ATA filings | Elevated | Public docket disclosure now required for >100 MW customers |
| SCC IRP proceedings | Active | 2024 Integrated Resource Plan reshaped by data-center demand curve |
| County by-right zoning reviews | Tightening | Loudoun, PW, Fauquier revisiting overlay districts |
| Fiber & subsea cable capacity | Advantaged | MAREA, BRUSA, Dunant landings via Virginia Beach |
| Workforce (critical facilities techs) | Tight | Community-college programs scaling but demand outpacing supply |
Interim scoring approach
Until per-county compute inventories are ingested, the Compute pillar uses ACS household broadband subscription rate (S2802) as a residential connectivity proxy. That signal measures consumer adoption, not hyperscale capacity — it is a placeholder, not the target metric.
The next release replaces the proxy with direct signals: county planning-commission approvals (Loudoun, Prince William, Henrico, Fairfax, Chesterfield, Spotsylvania, Stafford), SCC large-load filings, and Dominion IRP data-center demand disclosures.
Read the scoring formula in /methodology#compute.