Nashville's eminent-domain gambit signals a new front in the AI compute wars

Nashville Metro Council voted 27-5 to use eminent domain to seize a 23-acre parcel from DC Blox, the data center developer that paid $23 million for the site at 648 Grassmere Park, according to NewsChannel 5’s Tony Sloan. The city plans to use the land for offices, warehouse space, and employee training. DC Blox wanted to build a 10-megawatt data center there, next to the Nashville Zoo.

The vote caps a months-long fight that began when Mayor Freddie O’Connell announced condemnation legislation in response to “concerns from neighbors, families and zoo supporters.” The zoo called the move “a huge win.” DC Blox attorney Doug Sloan argued the design would limit noise and reduce water use, and insisted the project would proceed regardless. The company also pushed back on a specific characterization of its facility: “This project is not an AI factory, as some fear.”

That last line is the tell. The company is right that a 10-megawatt facility is modest in AI terms. Frontier training clusters run in the hundreds of megawatts. But the fact that DC Blox felt compelled to disclaim AI at all shows how the compute buildout has changed the political terrain. A data center is no longer a utility. It is a symbol of everything residents fear about the AI boom, and Nashville just demonstrated the lengths a city will go to keep one out.

The 10-megawatt detail matters

Let’s be precise about scale. Ten megawatts is small. For comparison, a single large AI training run can consume more power in a week than this facility would in a year. DC Blox is a regional player, not a hyperscaler. The proposed site was not going to host GPT-6. It was going to host colocation and edge workloads, the kind of infrastructure that supports cloud services and, increasingly, inference for AI applications.

That is exactly why this case is significant. If Nashville’s residents and council were willing to invoke the government’s most aggressive property power to block a 10-megawatt facility, what happens when a 500-megawatt campus comes to town? The AI industry’s compute demand is not concentrated in a few mega-sites. It is distributed across thousands of small and medium facilities, the connective tissue of the inference economy. Every one of those is now a potential political flashpoint.

The condemnation mechanism is the sharpest tool yet deployed in this fight. Zoning restrictions, environmental reviews, and community benefit agreements are standard friction. Eminent domain is different. It is the state taking property it does not own, for a public purpose, at a price set by negotiation or litigation. The city has not taken ownership yet. Metro will negotiate with DC Blox first, and if talks fail, the city can go to court to establish fair market value, or walk away entirely. Councilmember Courtney Johnston, whose district contains the site, framed the vote as a handoff: “We’re entrusting Metro Legal to make good decision for everyone involved including taxpayers that will be writing the ultimate check.”

What the city actually wants

Here is the part that should make AI builders nervous. The city’s stated purpose for the land is not environmental preservation or noise mitigation. It is “offices, warehouse space, and employee training.” The public use justification is generic municipal operations. The condemnation is not about what the land will become. It is about what it will not become.

That is a meaningful shift in how local governments treat data centers. The old playbook was incentives: tax abatements, expedited permitting, utility upgrades. Cities competed for facilities the way they competed for auto plants. Nashville’s move inverts that logic. The city is spending taxpayer money to acquire land it does not need, for purposes it could satisfy elsewhere, specifically to prevent a private company from building on it.

The planning commission had already backed restrictions that could pause data center construction near the zoo. The council is also considering BL2026-1391, legislation to regulate all data centers in the city. The eminent domain vote is not an isolated act. It is the enforcement arm of a broader regulatory push.

The AI factory framing problem

DC Blox’s statement that the project is “not an AI factory” deserves scrutiny. The company is technically correct. But the distinction is collapsing in public perception. Every data center now has an AI story attached to it, because every major cloud provider is reorienting its infrastructure around AI workloads. A 10-megawatt facility in Nashville could easily host inference for a regional AI application, or serve as a caching and routing layer for larger training clusters elsewhere.

The public does not distinguish. When residents hear “data center,” they now hear “AI,” and when they hear “AI,” they hear noise, water consumption, power draw, and the sense that their city is being turned into a cog in someone else’s machine. The zoo’s framing, that this is a win for “families in this community,” is emotionally potent precisely because it pits a beloved civic institution against an abstract corporate behemoth.

This is the reputational problem the AI industry has not solved. The compute buildout is happening at a scale that touches every community, but the benefits are concentrated in a handful of companies and regions. Nashville’s residents looked at a data center and saw cost with no local upside. The city’s response was to treat the facility as a public nuisance, and to use the most extreme legal tool available to remove it.

What this means for AI builders

For the industry, the lesson is not that eminent domain is coming for every data center. It is that the political risk of siting has become a first-order constraint on compute availability. The AI economy needs distributed infrastructure, and distributed infrastructure needs local consent. Nashville just demonstrated that consent can be withdrawn, retroactively, at the ballot box.

The 27-5 vote is the number to remember. It was nearly unanimous. The opposition to DC Blox was not a fringe movement. It was a citywide consensus, backed by the mayor, the zoo, and a broad coalition of residents. That consensus formed around a facility that was, by industry standards, tiny.

The AI industry should read this as a warning about the limits of technical argument. DC Blox said it could design solutions to address concerns. It said noise would not exceed ambient levels. It said water use would be reduced. None of it mattered. The company’s technical assurances could not overcome the political reality that residents did not want the facility, full stop.

The next fight will be bigger. A hyperscaler proposing a 200-megawatt campus near a residential area will face the same dynamics, with higher stakes. The companies that survive the compute buildout will be the ones that treat local politics as a core engineering problem, not an afterthought. Nashville has shown that the cost of getting this wrong is not a delayed permit. It is the loss of the land itself.