Big Tech's AI Bet Counted on Three Escape Routes. They're Closing.

Amazon CEO Andy Jassy made the bet explicit in February.

We are monetizing capacity as fast as we can install it. — Andy Jassy

The verb is "install." It is the exact point where a local moratorium bites: a company can monetize as fast as it can install, but a moratorium prevents installation. The C-suite's bet on speed is not abstract. A survey of more than 1,500 CFOs found that 92% feel career pressure to demonstrate AI ROI, while only 7% prioritize governance over deployment speed ^[1]. The numbers describe a corporate class that has priced in everything except the one variable it cannot control: whether a town board in Ohio or a county commission in Texas will let it pour concrete at all. The bet assumed local resistance would stay reactive. A developer could race to file permits before a ban took effect, flee to rural counties with lighter zoning, or sue to overturn a moratorium after it passed. Each of those escape routes is now closing. The first route, racing the clock, worked for a while. Digital Realty filed permit applications for a Seattle data center just before the city council's Land Use Committee voted unanimously on a moratorium ^[2]. In Upper Hanover Township, Pennsylvania, a developer submitted an application just before the board adopted new restrictions and was grandfathered in because the application was deemed complete ^[3]. But local governments have now shifted from reacting to applications to imposing moratoriums before any developer arrives. Pere Marquette Township's planning commissioner Louis Prima was explicit.

I wanted to make sure you knew this wasn’t in response to any type of application for a center. — Louis Prima

Southport, North Carolina's planning director Lawrence Ashley put the same logic in his own words.

The moratorium is simply being proactive in the fact the township knows it’s not addressed in our ordinance and we need to do so. — Louis Prima

Urbana, Ohio council member Amy Jumper stated the inverse of the corporate speed frame directly.

Our responsibility isn't about moving quickly, it's about doing what's right. — Amy Jumper

When a moratorium is already in place before a developer identifies a site, there is no clock to race. The window closes before it opens. The second route, fleeing to rural counties, is closing for the same reason. Developers migrated to Texas, Oklahoma, Kentucky, and the Dakotas specifically to bypass power constraints and operate under less burdensome zoning restrictions ^[4]. But those are now the exact communities imposing bans. Hamilton County, Tennessee passed a unanimous one-year moratorium on facilities over one megawatt ^[5]. Hill County, Texas imposed its own. Salix, Iowa voted for a moratorium after 900 acres of farmland were annexed for a data center project, and Adams and Brown counties in Ohio followed ^[6]. The flight to rural America carried the resistance with it. The third route, litigation, still works. It is the one escape hatch that has not sealed. Hill County, Texas imposed a moratorium on May 12, 2026 and was forced to unanimously rescind it on June 4 after developer RCM Hill filed a $100 million federal lawsuit; the county's own attorney had warned that neither the state constitution nor any state statute authorized the commissioners to enact a moratorium ^[7][8]. In Kentucky, the Data Center Coalition successfully lobbied to kill a bill that would have protected ratepayers from data center infrastructure costs ^[9]. In Indianapolis, DC BLOX got its data center approved after scaling down from three buildings to two and reducing the number of diesel generators ^[10]. But each legal win adds cost and delay that erodes the speed the bet was meant to protect. A $100 million federal lawsuit, a lobbying campaign that consumes months, a scope reduction that shrinks the project: these are not the frictionless installs the capex schedules assume. The litigation route works, but it works slowly. The resistance is not coordinated, and it is not universal. Maine Governor Janet Mills vetoed a proposed 18-month statewide moratorium ^[11]. Sand Springs, Oklahoma voted 6-1 to approve a Google data center despite a citizen lawsuit, with the mayor calling Google a good partner ^[12]. In Saline Township, Michigan, developers obtained a consent judgment that allowed the $16 billion Stargate project to proceed in exchange for $14 million in community benefits ^[13]. Moratoriums are individually overturnable. But each of those developer victories required resources, lawyers, and months that a company betting on speed did not budget for. Underneath the political friction sits a structural fact that no moratorium can impose and no lawsuit can repeal. PJM Interconnection, the grid operator for 67 million people across 13 states, cannot keep pace with data center construction because new power plants take five to seven years to build while data centers go up in twelve to twenty-four months ^[14]. The moratoriums are the visible political surface of a timeline collision the C-suite never priced in: both the physical infrastructure (grid, water, labor) and the political infrastructure (zoning, consent, litigation) operate on cycles that cannot be compressed to match a software-company capex schedule. Amazon projects $200 billion in 2026 capex ^[15]. Nvidia projects global data center spending of three to four trillion dollars annually by 2030 ^[16]. The money is committed. But PJM cannot deliver a new power plant in less than five years, and no lawsuit can change that.