Last Update: 08/01/2026 at 12:01 PM EST

Morning Briefing: Data Centers

Thursday, July 30, 2026

July 30, 2026

Paducah’s $100 Billion AI Campus Plan Still Has a Power Gate

Yesterday clarified the two speeds of the data-center buildout. At one speed, federal agencies and major investors are assembling industrial land, power development and enormous capital into new AI campuses. At the other, utilities, courts, regulators and residents are forcing projects to prove that their power access, permits and local commitments are real rather than assumed.

That distinction matters because announced scale is becoming less informative than delivery readiness. Paducah produced the day’s largest project move, but developments from Virginia to Massachusetts and Kansas showed that power terms, environmental compliance and public process increasingly determine whether a campus advances on schedule.

The US Department of Energy selected NextEra Energy and Brookfield for a planned data-center campus and power plant at the former Paducah Gaseous Diffusion Plant in Kentucky. Reuters reported a proposed investment exceeding $100 billion, while other reporting placed the campus target above 1.2 GW of compute capacity. This is genuine site-selection progress, but not a completed build: the proposed power-service agreement still requires approval from the Kentucky Public Service Commission.

Federal scrutiny of xAI’s self-supplied power strategy intensified. Representative Frank Pallone requested turbine inventories, emissions and permit records, power and water data, environmental analyses and government communications for the Colossus campuses in Tennessee and Mississippi. Reuters reported that 59 turbines had been installed at Colossus 2 without federal permits. The request turns a long-running neighborhood and environmental dispute into a broader test of how quickly deployed onsite generation is documented and regulated.

Several local actions showed that permitting risk now arises both from new rules and from procedural details. Montgomery County, Maryland, approved an 18-month halt on new data-center permits. Lexington officials placed DartPoints’ proposed redevelopment of a former Lexmark facility on hold because required approvals had not been secured before the city’s moratorium began. In Frederick County, meanwhile, Maryland’s highest court explained why a referendum challenge to a 2,615-acre data-center zoning overlay could not proceed, citing both the county charter and legally deficient petition maps.

Project-specific opposition continued to move into formal review and litigation. More than 100 people attended Compass Datacenters’ open house for a proposed Shawnee County, Kansas, facility after the company filed for a conditional-use permit. In Lowell, Massachusetts, residents sued over MassDEP’s approval of a Markley Group expansion that would increase the facility’s backup diesel generators from seven to 27. These are not equivalent outcomes, but both show why community engagement is becoming an execution requirement rather than a communications exercise.

Key Points

  • Power adjacency is becoming a more important site filter than land availability alone. Paducah pairs a federal industrial site with a planned power project, while reporting yesterday revisited two Pennsylvania locations where Amazon interest faded because required electricity could not be secured with sufficient certainty.
  • The debate over who pays for grid expansion is moving toward specific financial mechanisms. A House bill would require state regulators to consider making large-load customers cover the full incremental cost of generation, transmission and distribution upgrades. Amazon separately asked Virginia regulators to allow hyperscalers to fund project-specific transmission through contributions in aid of construction, shifting more stranded-asset risk away from other customers.
  • Public engagement is being judged by the quality of disclosed information, not simply whether an event occurred. Some attendees at Compass Datacenters’ Kansas open house criticized its poster-based format and the lack of a formal presentation. That response suggests developers gain little schedule protection from outreach that leaves basic questions about load, environmental effects and project timing unresolved.
  • Local resistance is becoming more legally sophisticated. Moratoriums, permit appeals, lawsuits and referendum disputes now sit alongside public meetings and protests. For developers, that means a favorable zoning vote can advance a project without settling the procedural, environmental or political risks that follow.

Implications

The Paducah selection strengthens the case for former federal and industrial sites that can combine large parcels with a credible energy-development plan. It also reinforces a harder lesson: even exceptional capital commitments do not substitute for an approved utility-service pathway.

Developers using natural-gas turbines to shorten grid timelines should expect emissions records, permit status, water consumption and community exposure to receive scrutiny comparable to the data-center buildings themselves. Onsite generation can accelerate power delivery, but it also enlarges the project’s regulatory footprint.

Developer-funded transmission could become a practical compromise between faster large-load connections and ratepayer protection. It would raise upfront project costs, but could reduce resistance created by the risk that unused infrastructure is left with ordinary customers if a campus is delayed, downsized or abandoned.

Permitting schedules increasingly depend on process quality. Complete applications, clear maps, timely approvals, accessible project details and meaningful participation can now be as consequential as the underlying zoning designation.

Watchpoints

Watch

Whether the Kentucky Public Service Commission approves, modifies or delays the power-service agreement for the planned Paducah campus.

Watch

How xAI and SpaceX respond to the congressional records request, particularly on the number, operating status and federal permit treatment of the Colossus turbines.

Watch

Whether Shawnee County advances Compass Datacenters’ conditional-use application and requires more specific disclosures on electricity demand, environmental effects and community protections.

Watch

Whether the Lowell lawsuit pauses Markley Group’s expansion or changes MassDEP’s treatment of the additional diesel generators and resident participation.

Watch

Whether Virginia regulators accept a developer-funded transmission mechanism and how it interacts with Dominion Energy Virginia’s evolving large-load cost estimates.

Watch

How jurisdictions emerging from temporary moratoriums translate their reviews into permanent rules on siting, power, water, noise and infrastructure funding.

Fallout

Three long-running subjects moved meaningfully yesterday: the effort to secure power at campus scale, the shift from broad ratepayer-protection promises to concrete cost mechanisms, and the expansion of local opposition into permits, moratoriums and litigation. Paducah showed that very large projects can still advance, but the rest of the day explained why site selection is only the beginning.

Power Access and Grid-Cost Responsibility

Power availability remains the decisive delivery constraint for large AI campuses. The policy question increasingly attached to that constraint is whether developers, utilities or existing customers should finance the generation and network upgrades needed to serve them.

Fresh developments

The Paducah selection paired a major federal site with a planned power plant and more than 1.2 GW of targeted compute capacity, but utility service remains subject to Kentucky regulatory approval. In Virginia, Amazon proposed directly funding project-specific transmission through contributions in aid of construction. A House proposal would separately direct state regulators to consider requiring large-load customers to recover the full incremental cost of supporting grid infrastructure.

Why we noticed

These developments move the discussion from a general principle—that data centers should pay their own way—toward mechanisms that could change project underwriting. More developer funding may increase initial capital needs, but an approved and clearly allocated power pathway can be more valuable than cheaper land with uncertain service.

Watch for:

  • Kentucky’s decision on the Paducah power-service agreement.
  • Virginia’s treatment of developer-funded transmission and stranded-asset risk.
  • Whether H.R. 9340 advances and how state commissions would apply its proposed standard.

Permitting, Moratoriums and Local Control

Communities are using temporary pauses, conditional-use reviews, lawsuits and appeals to rewrite development rules while individual projects continue to seek approvals. Outcomes remain highly dependent on jurisdiction and project stage.

Fresh developments

Montgomery County imposed an 18-month permitting halt, Lexington’s moratorium caught a redevelopment that lacked required prior approvals, and Maryland’s highest court clarified why Frederick County’s data-center zoning overlay was insulated from referendum. Elsewhere, Compass Datacenters entered county review in Kansas while Lowell residents challenged an air permit for a major generator expansion.

Why we noticed

The day demonstrated that local control is not expressed through one tool. A moratorium can stop new applications, an incomplete filing can strand a project at the deadline, a charter can foreclose a referendum, and an environmental lawsuit can reopen an approval already issued. Development teams therefore need legal and procedural readiness alongside land and engineering readiness.

Watch for:

  • Permanent standards adopted as current moratoriums expire.
  • The next Shawnee County decision on Compass Datacenters’ conditional-use permit.
  • Whether the Lowell court grants relief that affects the Markley expansion.

Onsite Power and Environmental Accountability

Developers are increasingly considering dedicated generation as a way around slow or uncertain grid connections. The approach can shorten the power timeline, but it transfers risk into air permits, fuel supply, noise, water use and neighborhood exposure.

Fresh developments

Representative Pallone’s request for extensive xAI records elevated questions surrounding the Colossus campuses from local complaints and permit disputes to congressional oversight. The request covers turbine inventories, emissions, federal permits, power and water consumption, environmental reviews and communications with government agencies.

Why we noticed

The breadth of the request is revealing. Regulators and lawmakers are no longer treating onsite generation as an auxiliary feature of a computing facility; they are examining it as major energy infrastructure. That makes permit documentation and environmental controls part of the core delivery plan, especially where turbines are deployed before conventional grid service is available.

Watch for:

  • xAI’s documentation of turbine status and federal permit compliance.
  • Any site visit or further congressional action following the company’s response.
  • Whether scrutiny changes the timing or configuration of Colossus power operations.

Final Thought

The buildout is not simply slowing; it is becoming conditional. The projects best positioned to move will be those that convert ambition into approved power, complete permits and credible local commitments before construction asks everyone else to take those elements on faith.