Frontier Grid · governed large-load access

Large loads do not connect on announced capacity.

Frontier Grid tracks the rules, caps, queues, financial gates, and physical dependencies that determine whether a large load can actually get onto the system at the required scale and date.

Governed large-load access

The rules that determine whether large loads can actually get onto the system.

A public view of governed access mechanisms across U.S. RTOs, ERCOT, Brazil, and Alberta. The values below come from human-reviewed durable records rather than staging proposals or inferred capacity.

Open Compute Intelligence
Cases tracked
9
FERC §206 dockets
6
Latest evidence review
Aug 26, 2026
CaseStageRequestedConnectableCapNext gateChecked
PJM
EL26-67
filed
change: yes
Nov 16, 2026Aug 26, 2026
SPP
EL26-68
filed
change: yes
Nov 20, 2026Aug 26, 2026
NYISO
EL26-69
filed
change: yes
Nov 16, 2026Aug 26, 2026
MISO
EL26-70
filed
change: yes
Nov 16, 2026Aug 26, 2026
CAISO
EL26-71
filed
change: yes
Nov 16, 2026Aug 26, 2026
ISO-NE
EL26-72
filed
change: yes
Nov 16, 2026Aug 26, 2026
ERCOT
US-ERCOT-BATCH-ZERO
approved
change: yes
438,000 MWAug 31, 2026Aug 26, 2026
ONS
BR-PNAST-2026-S1
announced
change: no
Sep 28, 2026Aug 26, 2026
AESO
CA-AB-AESO-INTERIM
approved
change: no
1,200 MW1,200 MWAug 26, 2026

“—” means unresolved or not published; it does not mean zero.

7 of 9 records currently carry material_change=yes.

Compute as application

Compute is where governed access becomes most visible.

Governed large-load access is a continuing Frontier Grid practice. Compute is its clearest application because a project can have demand, capital, land, and announced generation while still failing at the access mechanism itself.

Project work follows the full path from grid and interconnection through fuel-backed power, physical deployment, utility obligations, financial gates, equipment, and capital sequencing.

Deployment lens

Power availability is only the beginning of the decision.

The relevant question is whether every critical dependency can support the planned load, operating profile, target date, and downside case.

Grid and interconnection

Queue timing, transmission, substations, deliverability, utility obligations, and the gap between announced power and executable service.

Fuel-backed power

Generation configuration, implied fuel demand, physical gas delivery, transportation rights, contracts, competing demand, and stress economics.

Physical deployment

Cooling, water, land, equipment, permitting, reliability, construction timing, and the local dependencies that can still govern first power.

Commercial and capital sequencing

Where utility commitments, construction, financing, customer demand, financial gates, and target operating dates fail to align.

Compute intelligence environment

Research, briefs, signals, and private access remain available.

The portal remains the compute research environment. It tracks market and node-level changes; project work applies the same evidence and dependency model to a specific large-load decision.

Public portal layer

Intelligence Preview

Selected nodes, signal summaries, constraint framing, and the public boundary of the compute research system.

Explore preview
Free sample brief

PJM and the 2026 Compute Constraint Stack

A source-backed sample of the Frontier Grid lens across interconnection, utility structure, and physical deliverability.

View PJM brief
Private brief

Missouri Compute Infrastructure Constraint Stack

Analysis of large-load tariff structure, financeability, contractual flexibility, and unresolved delivery risk.

View Missouri brief
Recurring research

Monthly Infrastructure Constraint Dispatch

Ongoing coverage of node-level signals, reversals, utility structures, and deployment-relevant constraints.

View Monthly Dispatch
Project application

Evaluating a data center, power strategy, or large-load corridor?

Bring the planned load, geography, target date, proposed power path, fuel assumptions, physical requirements, and the gates that remain unresolved.