The Data Center Bargain

In Bessemer, Alabama, the city council was weighing a $14 billion data center project — the kind of proposal that has triggered moratoriums in dozens of American towns this year. Councilor Carla Jackson had a specific question: where would the water come from? The answer, she made clear, would be the Black Warrior River, not the city's drinking supply. Resident utility bills would not rise. The council approved the project. ^[1] That exchange captures something larger than one Alabama town. Across the United States, the fight over AI data centers has moved from a simple yes-or-no question to a negotiation. Local and state governments are replacing blanket moratoriums with a model that trades approval for specific resource guarantees: prove you will not drain our water, spike our electric bills, or leave us holding the infrastructure tab, and you can build. The conditions now being demanded fall into a few recurring categories. Water is the most visceral. In Indianapolis, Metrobloks secured approval for a $500 million data center only after incorporating closed-loop cooling to avoid groundwater extraction. ^[2] In Granville Township, Pennsylvania, a draft ordinance was revised to include protections for private groundwater wells. ^[3] In Ypsilanti Township, Michigan, the board imposed a 12-month water moratorium targeting a $1.2 billion University of Michigan computing facility. The university is exempt from local zoning, so the township used its utility authority to demand environmental studies before committing water. ^[4] Energy costs are the second front. Wisconsin's Public Service Commission unanimously approved a first-of-its-kind tariff requiring data centers to fund 100 percent of generation and grid infrastructure costs, lowering the threshold from 500 megawatts to 100 and extending agreements from 10 to 15 years. The shift moved $5 billion in new generation costs onto the companies building the centers. ^[5] Ohio's HB 706 requires data centers to sign contracts with minimum billing demands and exit fees set at 85 percent of projected energy use; Oklahoma's HB 2992 mandates separate electric contracts, collateral, and 10-year commitments. Both states designed these conditions explicitly to preempt local moratoria. ^[6] In Colorado, legislators are debating a bill that would mandate data centers match their total energy use with renewable energy credits. ^[7] Then there is the direct community-benefit payment. In Lansing, Michigan, Deep Green redrafted its $120 million data center plan to include $1 million in equity return to the city, upfront payment of all energy infrastructure costs, closed-loop cooling, and no request for tax incentives. Mayor Andy Schor called it "a better way to do data centers" being "watched across the country." ^[8] In Saline Township, Michigan, the $16 billion Stargate project — backed by Oracle, OpenAI, and Blackstone — proceeded only after developers sued to overturn a rezoning denial. An October consent judgment allowed construction in exchange for $14 million in community benefits. ^[9] In Franklin, Tennessee, TenKey LandCo won unanimous approval for a $1.6 billion data center only after agreeing to monthly public updates, water usage caps, and detailed stormwater plans following a contentious four-hour hearing. ^[10] Transparency is the newest and fastest-spreading demand. Minnesota state senators are pushing legislation that would ban nondisclosure agreements between tech firms and local governments, a direct response to the secrecy that has surrounded many project negotiations. ^[11] Virginia's General Assembly passed laws requiring data center developers and water authorities to disclose water usage after reports showed facilities consume at least 2 billion gallons annually, two-thirds of it from drinking supplies. ^[12] Illinois's POWER Act requires data center developers to fund their own energy infrastructure using renewable sources and maintain water usage transparency. State Senator Ram Villivalam made the conditional logic explicit.

With the shifting energy landscape, it is imperative that our growth does not undermine affordability and stability for our families. — JB Pritzker

The pattern is not confined to local government. Over the past eight months, the same conditional logic has been absorbed at the federal level. In January, President Trump announced that tech companies must "pay their own way" for data center costs. ^[13] In March, he issued a Ratepayer Protection Pledge. By July, the House Energy and Commerce Committee had unanimously approved the bipartisan Ratepayer Protection Act, which requires data centers drawing 100 megawatts or more to cover the full incremental costs of generation, transmission, and distribution. ^[14] The bill's Republican sponsor, Representative Bob Latta, framed it in language any town councilor would recognize.

Our communities are focused this Congress on winning the race to AI dominance while securing our grid. — Brett Guthrie

This is not a story of local resistance overriding federal ambition. It is a convergence: all three levels of government are arriving at the same conditional playbook from different directions. Microsoft itself has welcomed the shift. After Wisconsin's tariff passed, the company said it "gives us a clear path to continue investing" while protecting ratepayers. ^[5] Microsoft president Brad Smith went further in January, pledging to replenish water, avoid tax breaks, and not raise electricity rates, and acknowledging that "the future is going to require a lot more communication, which by definition means fewer nondisclosure agreements." ^[13] The convergence has been tested by direct federal override, and the results are instructive. When the Bureau of Land Management approved a data center on federal land in Boulder City, Nevada by amending a previous solar farm permit and determining the original environmental review was sufficient, the city voted unanimously to appeal. City Attorney Brittany Walker called it "a departure from previous precedent and procedure." ^[15] The federal government could bypass local review, but it could not make the city accept the outcome. The more revealing test came in Hill County, Texas. RCM Hill, LLC filed a $100 million federal lawsuit that forced the county to rescind its data center moratorium after less than a month. The county did not surrender. It replaced the ban with a mandatory developer checklist requiring detailed data on water, traffic, noise, and economic impacts. County Judge Shane Brassell said the moratorium had already achieved its purpose by weeding out "less desirable" developers. ^[16] The federal lawsuit killed the ban and produced a regulatory framework in its place. The same adaptation is visible wherever local governments have been cornered. Ypsilanti Township, lacking zoning power over the university, used its utility authority to demand environmental studies. ^[4] Saline Township, sued over a rezoning denial, extracted $14 million in the settlement. ^[9] In each case, the tool changed but the conditional logic held. The model is not universal, and its limits are sharpening. California offers the clearest warning of how industry lobbying can hollow out conditional regulation. Senator Padilla's original bill sought separate electricity rates for data centers, 100 percent carbon-free electricity by 2030, and large battery mandates. The Silicon Valley Leadership Group and the Data Center Coalition stripped it to a mere study, due by 2027. Governor Newsom vetoed water-use reporting. ^[17] The result was a condition so thin it barely qualifies as one. New York chose a different path entirely. Governor Kathy Hochul signed a one-year statewide moratorium on large data centers, making New York the first state to opt for a ban rather than a negotiated framework. ^[18] In Coachella, California, the city council unanimously terminated a development agreement with Stronghold Power after months of public protests over diesel generator pollution and water demands. Conditional approvals can be reversed when the conditions are not met. ^[19] The deepest vulnerability in the model was articulated not by an opponent but by a proponent. In Linn County, Iowa, Supervisor Sami Scheetz voted against a moratorium because the county had already passed a comprehensive data center ordinance with an independent water study, a binding water use agreement, and the board's authority to reject any project. But he warned that moratoriums create a structural problem.

The local government in Iowa with the strongest protections for residents on data centers will be closed for business, which will push projects towards the places with the weakest regulations, which is the opposite of protecting our region and our people — Sami Scheetz

That is the honest limit of the pattern. The conditional acceptance model is becoming dominant — visible in Bessemer and Lansing, in Wisconsin's tariffs and the House Ratepayer Protection Act, in the developer checklists that replaced bans in Hill County and the utility leverage deployed in Ypsilanti. But it is a patchwork, not a standard. Every jurisdiction negotiates its own terms, and the strongest protections risk becoming a reason for developers to look elsewhere. The model has moved the fight from "not in my backyard" to "only on my terms." Whether it can hold there depends on whether enough jurisdictions demand the same terms, or whether the race to the bottom that Scheetz warned about is already underway.