Nashville seizes the land to stop a data center. Cities are done asking nicely.

What happened

On August 5, 2026, Nashville's Metro Council voted to authorize eminent domain proceedings against a 71-acre parcel on Nolensville Pike, directly adjacent to the Nashville Zoo. The parcel had been under contract to a data center developer, with a project that would have added tens of megawatts of load to a corridor the city has spent a decade rezoning for parks, housing, and zoo expansion. Rather than fight the project through the standard planning-commission channels — where a developer with signed utility agreements typically wins — the council skipped ahead and moved to take the land.

Eminent domain to block a data center is not something that shows up in the standard hyperscaler siting playbook. The mechanism is usually reserved for roads, schools, and utility right-of-way. Nashville's argument is that the parcel is needed for public use — specifically, zoo expansion and adjacent green space — and that the data center would foreclose that use permanently. The developer will get fair market value. What they won't get is the site.

The vote followed months of neighborhood opposition centered on the usual data center complaints: substation buildout, diesel backup generators, water draw for evaporative cooling, and the fact that a windowless concrete box next to a zoo is a hard sell to anyone who doesn't work in infrastructure. What's new is the council's willingness to use the nuclear option to end the conversation.

Why it matters

For most of the last decade, data center siting has been an economic-development story. Cities and counties competed for the projects, offered abatements, and celebrated the tax base. That framing has quietly inverted. The load a modern AI-era data center puts on a local grid — 100 to 500 MW is now a mid-sized campus, and the gigawatt tier is real — has become large enough that the host community absorbs the externalities without seeing much of the upside. The jobs numbers are thin. The property tax is often abated. The power draw shows up in everyone else's rates. And in a lot of the country, the grid interconnect queue is now the binding constraint on residential and industrial growth alike.

Nashville is not alone. Loudoun County, Virginia — the physical center of gravity for U.S. hyperscale — has been layering moratoria, setback requirements, and noise ordinances. Prince William County flipped from cheerleader to skeptic. Chandler, Arizona, has pushed back on water use. Santa Clara has capped new load. What's different here is the escalation from "we won't approve it" to "we will take the parcel." Once one council does this and survives the inevitable takings-clause challenge, the option is on every other city attorney's desk.

The hyperscalers see this coming and have been quietly rerouting capital. Meta's Louisiana campus, the Stargate sites in Abilene, the Oracle/OpenAI Texas buildouts, xAI's Memphis footprint — the pattern is unmistakable. Move to jurisdictions where the local government is a partner, the power comes from behind-the-meter gas or a nearby nuclear plant, and the neighbors are twenty miles away. The industry's answer to political risk in urban and suburban markets is to stop building in urban and suburban markets.

That has second-order consequences that hit the people reading this. Latency-sensitive workloads — the ones that actually need to be near your users — get harder to place. Regional availability zones in Tier 2 metros become scarcer or more expensive. And the concentration of new capacity in a handful of energy-rich rural counties creates the same single-region blast radius that everyone spent the 2010s trying to engineer away.

What this means for your stack

If you're doing infrastructure planning on a 2-to-5-year horizon, the political risk on data center siting is now a variable you have to model. Concretely: stop assuming that the region your provider promised in 2024 will actually have the capacity you need in 2027, particularly in metros where local politics has turned. Ask your account team where the next 500 MW of capacity in your primary region is coming from, and where it's actually being built. "Coming online in Q3" and "has broken ground on a site the county won't take back" are different levels of certainty.

For anyone running latency-sensitive workloads — real-time inference, gaming backends, financial APIs, WebRTC — the shift of new capacity to rural Texas, Louisiana, and the Ohio River valley matters. You may need to accept 20-30 ms of additional RTT to your compute, or start budgeting for edge deployments that were previously nice-to-haves. Cloudflare, Fastly, and the CDN-with-compute crowd are quietly repositioning around exactly this gap.

If you're on the buy side of a colo or wholesale lease, get much more specific about entitlement risk in the contract. "Landlord will use commercially reasonable efforts to obtain permits" is not the same protection it was two years ago. Ask what happens to your deposit if the site gets challenged, moratoria'd, or — now — condemned. The answer for most standard-form leases is "you eat it."

Looking ahead

Expect a takings-clause lawsuit, expect it to drag, and expect Nashville to win at least on the threshold question of whether zoo expansion is a public use — the Supreme Court's *Kelo* framework is genuinely permissive on that point. The more interesting question is what happens the tenth time a city does this. At some point, the hyperscalers stop treating community opposition as a PR problem and start treating it as a portfolio-level constraint on where AI compute can physically exist — and the map of the internet redraws itself around that constraint. Nashville just made that redrawing happen a little faster.