Frontier Grid infrastructure deployment intelligence

Know whether infrastructure can actually support the project.

Frontier Grid helps development, investment, and operating teams test whether power, fuel, water, and other physical dependencies can support a project at the required scale and timing — before capital is committed.

Water coverage begins in the St. Johns–Flagler corridor. Fuel-backed power work follows the specific project, assets, and delivery corridor.

Current operating frame

Infrastructure Deployment Readiness

project-specific
DecisionAdvance / investigate / deprioritize
ScaleSite / corridor / portfolio
SystemsPower + fuel + water
DeliverySource-backed readiness brief
Physical path and responsible infrastructure systems
Capacity, commitments, and competing demand
Timing dependencies, contracts, and unresolved approvals
Stress cases and questions requiring formal confirmation
The deployability problem

Nearby infrastructure does not mean a project is deployable.

A project can sit near power lines, pipelines, treatment plants, or major corridors and still fail because capacity is committed, transportation is interruptible, local infrastructure is missing, contracts are unresolved, or timing does not align.

Frontier Grid assembles the physical, commercial, and geographic record, identifies what is known, and separates documented conditions from claims that still require formal confirmation.

Current service modules

Readiness before engineering and capital commitment.

Frontier Grid uses a common evidence and dependency model across infrastructure systems. Each engagement begins with a specific project, operating requirement, geography, and decision.

Available now

Water & Wastewater Serviceability Screen

Preliminary site and corridor screening that separates systemwide treatment capacity and mapped service areas from parcel-level serviceability.

utility and service pathcapacity and expansion contextconnection and formal-confirmation gaps
View sample screen
Selected engagements

Fuel-Backed Power Readiness

Large-load readiness analysis connecting a generation plan to physical fuel supply, transportation, contracts, competing demand, permitting, and timing.

implied fuel demand and generation configurationphysical and commercial delivery pathstress economics and dependency timeline
View completed pilot
01

Physical path

Identify the responsible systems, assets, delivery path, and dependencies between regional infrastructure and the project.

02

Capacity and commitments

Separate published capacity from available, allocated, contracted, or physically deliverable capacity at the required date.

03

Constraint stack

Surface infrastructure bottlenecks, competing demand, contract gaps, permitting dependencies, and conflicting claims.

04

Decision support

Translate the evidence into an advance, investigate, restructure, or deprioritize recommendation with explicit assumptions.

Buying moment

Before the infrastructure strategy hardens.

The work is most useful during site comparison, project underwriting, land diligence, financing, or power-strategy development — before a team treats announced capacity, nearby assets, or preliminary supplier claims as an executable operating path.

First public module

Water serviceability across St. Johns–Flagler.

The initial public layer connects official St. Johns utility-zone geometry with treatment facilities, published capacity, expansion programs, known constraints, and formal-confirmation requirements.

Open full coverage and sources
Public coverage layer
St. Johns–Flagler corridor
Verified 2026-07-26
Basemap © Esri · Utility polygons © St. Johns County
Selected record
Palm Coast Wastewater Treatment Plant #1
Known constraint

Palm Coast identifies WWTP1 as the system's principal localized capacity pressure point. The city is funding a major expansion and modernization program.

Utility
City of Palm Coast Utility Department
Published capacity
6.83 MGD
Facility address
26 Utility Drive, Palm Coast, FL 32137
Evidence
Official utility record

Facility markers are approximate to the published address. Published capacity is not the same as remaining or committed project capacity.

This public layer does not claim live capacity or certify serviceability for a parcel. Published treatment capacity, service boundaries, remaining capacity, committed capacity, and local connection feasibility are separate facts.
Evidence standards

Every conclusion carries a source, date, and confidence level.

Deployability is not one static number. Frontier Grid keeps evidence quality separate from operational condition so an inference is never presented as physical delivery, reserved capacity, or a contractual commitment.

Counterparty-confirmed

Formal material or direct written confirmation from the responsible party.

Official public record

Permits, plans, capital programs, tariffs, filings, maps, agendas, and regulatory records.

Supported inference

Multiple sources point to the same condition, but project-specific confirmation is still required.

Unverified

A claim exists, but the available evidence is insufficient, conflicting, or outdated.

Public status language

Factual states before simplified scores.

Infrastructure path confirmed
Expansion or project underway
Known constraint
Formal confirmation required
Insufficient data
Who it is for

Teams with capital at risk and incomplete infrastructure information.

The clearest fit is a team comparing sites, underwriting a project, or testing whether an infrastructure strategy survives its physical, commercial, and timing dependencies.

Large-load and data-center developers
Industrial and process-facility developers
Infrastructure and real-asset investors
Lenders and independent diligence teams
Site-selection and land acquisition teams
IPPs, utilities, and project developers
Midstream and energy infrastructure teams
Advisers evaluating multi-site or corridor exposure
Scope boundary

Intelligence before formal confirmation.

Frontier Grid reduces uncertainty and prepares the next diligence step. It does not replace asset owners, utilities, suppliers, engineers, regulators, or legal counsel.

Frontier Grid provides

  • Preliminary site, project, and corridor screening
  • Source-backed infrastructure and commercial research
  • Dependency mapping across power, fuel, water, permitting, and timing
  • Comparison across a small portfolio of sites or projects
  • Evidence dates, confidence levels, assumptions, and unresolved questions

Frontier Grid does not provide

  • Utility, transportation, or fuel-supply commitments
  • Hydraulic, electrical, pipeline, or process engineering
  • Commodity trading or hedging execution
  • Legal, regulatory, environmental, or permitting advice
  • Certification that a project can be served, built, or operated
Large-load deployment

Compute is where the full dependency stack becomes visible.

Data centers connect power, fuel, water, equipment, permitting, geography, contracts, and capital on the same timeline. Frontier Grid uses that pressure to develop a broader deployment-intelligence system, rather than treating compute as a disconnected research category.

Strategic structure
Company focus
Infrastructure deployment intelligence
Current module
Water and wastewater serviceability
Next module
Fuel-backed power readiness
Systems layer
Signals, dependency graphs, and monitoring
Operating discipline

Build each module from verified records, not broad claims.

Water coverage begins in Northeast Florida. Fuel and power work follows the project corridor, generation configuration, physical delivery path, and commercial dependencies. Expansion happens only when the evidence can support a decision.

Selected intelligence · Pilot 01

A real project, tested against its operating dependencies.

Frontier Grid evaluated whether Project Kilby's proposed fuel-backed power strategy could support Microsoft's Pecos data-center campus at the announced scale and timeline.

The analysis followed the project from load and generation configuration through fuel demand, transportation, commercial access, permitting, construction, commissioning, and operating stress.

~2 GW
announced campus capacity
~2.67 GW
announced Kilby generation
2028
targeted first power
INVESTIGATE
final classification

Independent public-evidence assessment · Evidence cutoff: July 28, 2026

Executive result

The strategy is physically plausible, but the public record does not yet establish an executable end-to-end gas-delivery path. The controlling dependency is the project-specific chain connecting firm transportation, usable pressure, lateral infrastructure, and gas-in to the first operable generation block.

Decision implication

Do not underwrite the full 2 GW headline for 2028. Advance only a bounded first phase after its fuel path, pressure, lateral, final permit, equipment schedule, and Microsoft acceptance block are evidenced.

Controlling dependency
Named load
fuel requirement
carrier and delivery points
hydraulic validation
firm transportation
lateral and pressure facilities
gas-in
commissioning
Sample deliverable

See how public evidence becomes a site decision.

The illustrative Site Screen shows the executive recommendation, assessment matrix, open utility questions, next actions, evidence trail, and the line between preliminary intelligence and formal confirmation.

Start a conversation

Bring the project and the unresolved infrastructure dependency.

Use the project inquiry for deployment readiness, fuel-backed power, portfolio diligence, or partnerships. Use the structured Water & Wastewater Site Screen for a specific parcel or shortlist in the current coverage area.

Frontier Grid updates

Track new infrastructure constraint releases.

Receive occasional notes on infrastructure serviceability, new Florida coverage, compute research, and Frontier Grid releases.

Frontier Grid | Infrastructure Deployment Intelligence