Data-Center Guardrails Are State Capacity

Florida’s new data-center law shows how states can turn AI infrastructure growth into a public-governance question about water, electricity, ratepayers, and local authority.

Share

AI infrastructure does not have to be governed only after the fact.

Florida just offered one early example of what it looks like when a state tries to set rules before data-center growth becomes an unstoppable local fight.

In May 2026, Florida enacted Senate Bill 484, a law regulating large-scale data centers. The law requires water-management districts to deny consumptive-use permits if a proposed data center’s water use would harm local water resources. It also requires reclaimed water where possible and says large data centers must bear their own full cost of electric service rather than shifting those costs to the public.

That matters because data centers are not ordinary buildings. They can require enormous amounts of electricity, water, land, cooling capacity, and transmission infrastructure. When those costs are not clearly assigned, they can spread outward to residents, utility customers, water systems, and local governments.

Read Government Technology’s coverage of Florida’s data-center guardrails

The important point is not that Florida has solved data-center governance. It has not. The law’s implementation will matter. So will transparency, enforcement, local authority, and whether developers can still negotiate around public concerns.

But Florida’s move is still significant because it treats data-center growth as a public-governance problem, not just a private development question.

That is what state capacity looks like in this part of the AI race.

State capacity does not always mean a new agency, a sweeping regulatory code, or a grand national strategy. Sometimes it means the state can ask basic questions before infrastructure commitments become irreversible:

Who pays for the electricity?

Who bears the water burden?

Can local governments say no?

Are the public costs visible?

Are resource constraints part of the approval process?

This is where the race between concentration and dispersion becomes concrete. Large data centers concentrate compute, capital, energy demand, and bargaining power. Guardrails push in the other direction. They create public leverage over where infrastructure goes, what conditions attach, and whether ordinary residents subsidize the buildout.

Good guardrails are not automatically anti-growth. They can make growth more legitimate by forcing the costs, tradeoffs, and responsibilities into the open.

That is the lesson from Florida: AI infrastructure governance is not only about stopping bad projects. It is about building enough public capacity to decide what responsible infrastructure should require.

This article is part of the AI Infrastructure Governance series.