Who Pays for Infrastructure in Data Center Development?

In nearly every data center development deal, there's a moment when the numbers stop making sense. The land is secured, the power agreement is drafted, the anchor tenant is committed — and then the full picture of public infrastructure costs lands on the table. Roads need to be widened. Transmission lines need to be extended. Water and sewer capacity needs to be built, sometimes from scratch. Unlike the construction of the building itself, none of these costs show up neatly in a pro forma template you can download from the internet.

The rule is blunt and non-negotiable: every data center owner and developer must pay all costs for — and associated with — public infrastructure improvements, including power, water, sewer, and road access. Not partially. Not after negotiation. All of them.

Understanding what that actually means in practice separates developers who close projects from those who tie up land for two years and walk away.

What "Infrastructure Costs" Actually Means

When people talk about infrastructure costs in data center development, they often mean two different things — and conflating them is expensive.

The first category is the obvious one: the physical systems inside the fence line. Generators, cooling towers, switchgear, internal fiber — all of it is the developer's problem, full stop. Nobody disputes this.

The second category is where deals get complicated: public infrastructure improvements required to support the facility but located outside the project boundary. This is where municipalities and utilities hand the bill to developers without apology, and often without much warning if the developer hasn't done rigorous due diligence upfront.

A 100 MW hyperscale campus doesn't just require power — it requires transmission infrastructure capable of delivering that power reliably. In rural areas, which are increasingly attractive for data center development due to land cost and available acreage, the nearest substation capable of handling that load might be 10 miles away. Extending a 138kV or 230kV line that distance can cost $3–5 million per mile. That's a $30–50 million line item that has nothing to do with your building.

Water tells a similar story. Data centers — even modern ones using advanced cooling — consume substantial amounts of water. A large facility might require 300,000 to 500,000 gallons per day. If the municipal water main doesn't have capacity or doesn't reach the site, the developer funds the extension and the capacity upgrade.

The Four Cost Categories Every Developer Must Budget

Power

Power is almost always the largest and most complex infrastructure obligation. The utility will typically conduct an interconnection study — a process that can take 12 to 24 months — to determine what grid upgrades are needed to support the facility. Whatever those upgrades cost, the developer funds them, often through a facilities extension agreement or a direct contribution to the utility.

The interconnection queue problem is real: in many high-demand markets, developers are waiting years and spending millions just to get a definitive answer on what their infrastructure bill will be.

Experienced developers now commission preliminary power studies before closing on land, precisely to avoid discovering a $40 million transmission upgrade obligation after the deal is done.

Water and Sewer

Water and sewer infrastructure costs are frequently underestimated, especially for sites outside established industrial zones. Municipal systems are sized for residential and light commercial loads, not for facilities that rival small cities in their daily consumption.

Sewer capacity is the sleeper issue. Many jurisdictions have strict limits on discharge volume and wastewater temperature — data center cooling systems can discharge warm water that requires treatment before it enters the municipal system. Upgrades to treatment capacity, when required, fall to the developer.

Road and Transportation Access

Heavy construction equipment, ongoing deliveries of servers and hardware, backup generator fuel trucks, and daily employee traffic all impose demands on local road infrastructure. Municipalities routinely require developers to fund turn lanes, road widenings, traffic signal installations, and sometimes bridge load-rating upgrades.

In Virginia's Loudoun County — the largest data center market on earth, with over 25 million square feet of capacity — developers have collectively spent hundreds of millions of dollars on road improvements as a condition of permitting. It's not optional. It's the price of access to the market.

Who Is Actually on the Hook

The legal and contractual responsibility flows in a clear direction, even if the practical burden sometimes gets distributed across the deal structure.

The developer carries primary responsibility for all public infrastructure costs. This obligation typically appears in the conditional use permit, the utility service agreement, and any development agreement executed with the local jurisdiction. Trying to negotiate around it is largely futile — municipalities have leverage, and they know it.

Landowners who enter into ground leases or fee sales to data center developers should understand that infrastructure obligations can affect deal value significantly. If a seller is carrying back any financing or has earnout provisions tied to development milestones, infrastructure cost overruns can delay or derail those payments. Smart landowners do their own diligence on infrastructure feasibility before negotiating deal terms.

EPC (Engineering, Procurement, and Construction) contractors execute the work, but they don't absorb the cost — they pass it through. Where contractors do add value is in estimating accuracy and constructability review. A good EPC team will flag infrastructure scope gaps before they become change orders. A mediocre one won't, and the developer pays the difference.

How Experienced Developers Manage These Costs

The developers who execute data center projects efficiently have internalized one principle: infrastructure cost management starts before the LOI, not after the permit is issued.

Do the Site-Specific Study Before You Close

Generic assumptions about infrastructure costs are nearly worthless. Power availability, water capacity, and sewer headroom vary dramatically not just by state, but by county, by municipality, and sometimes by which substation serves a given parcel. Commission a preliminary infrastructure assessment on every site before closing. The cost — typically $50,000 to $150,000 — is trivial compared to the exposure it mitigates.

Negotiate the Timeline, Not the Obligation

Developers can rarely negotiate away infrastructure cost obligations, but they can negotiate timing, phasing, and cost-sharing with municipalities when the project brings significant economic benefit. A 1,000-job construction project with a $200 million annual tax assessment creates political will. Use it — not to avoid infrastructure investment, but to potentially phase it in line with facility buildout, reducing upfront capital requirements.

Some jurisdictions offer tax increment financing (TIF) districts or special assessment districts that can provide partial cost offsets for public infrastructure. These mechanisms are not guaranteed and often require multi-year negotiations, but they exist and are worth pursuing on larger projects.

Model Infrastructure Costs as a Range, Not a Point Estimate

Interconnection studies come back with options. Utility engineers present alternatives with different cost and timeline profiles. Build your financial model to reflect a base case, a moderate upside case, and a stress case on infrastructure costs. Deals that only pencil under best-case infrastructure assumptions are deals that should make you nervous.

What the Market's Best Developers Actually Do Differently

The data center development firms that consistently close complex projects share a few non-obvious habits.

They hire former utility engineers. Having someone on the team who understands how interconnection studies are conducted — and how to influence the utility's engineering assumptions in a developer-favorable direction — is worth more than most people realize. Interconnection studies are not purely objective exercises; the assumptions built into them drive the cost outputs.

They build infrastructure relationships before they need them. The developer who has a working relationship with the municipal public works director gets a call when a competing project threatens shared infrastructure capacity. The developer who shows up for the first time at a pre-application meeting gets whatever is left.

They treat infrastructure cost uncertainty as a siting factor, not just a budget factor. A site that's 15% cheaper on land but carries $60 million in infrastructure uncertainty may be the worse deal at the portfolio level, even if it looks better on a per-acre basis.

The bottom line for anyone entering data center development is straightforward, even if the execution isn't: the infrastructure bill is yours. Plan for it early, model it conservatively, and build the relationships that let you execute it efficiently. Developers who absorb that reality from the start build projects. Those who discover it mid-development build expensive lessons.

For more insights on navigating the complexities of data center development, visit our marketplace at InfraSale Marketplace.