64% Opposed: Cherokee Ban Adds a Sovereign Layer to AI Data Center Site Selection

Cherokee Nation hyperscale data center ban illustrated by a large data center campus bordering open tribal land

TL;DR · 30-second read

The Short Version

The Cherokee Nation, a Native American tribe with its own government, has banned giant artificial intelligence computer warehouses from land it owns. About two in three citizens who answered a tribal survey opposed building them on the reservation.

A tribal report says a complex the size of a small town may employ only about 100 people once open, while using huge amounts of power and water.

Why care? These projects usually need a willing landowner and a willing local government. Here, those can be the same body, and it said no.

Gizmodo reported that Cherokee Nation Principal Chief Chuck Hoskin Jr. announced in early August 2026 a ban on hyperscale data center projects on land owned by or held in trust for the Nation. Hyperscale data centers are the very large computing campuses used by major cloud and AI companies.

The decision followed a report from the Nation’s Data Center Task Force, which surveyed 1,593 citizens and found about 64% opposed to building such facilities within the reservation. Separately, the Nation said it will not support hyperscale projects on non-tribal land inside the reservation unless developers conduct “robust” consultation with the tribe.

Executive Summary

The Cherokee Nation has drawn two lines for AI data center developers. On land it owns or that is held in trust for it, hyperscale projects are banned. On non-tribal land inside its reservation, the position is conditional: no support without early, transparent and “robust” consultation.

The announcement matters because it changes who a developer may need to deal with. Data center siting fights usually play out before county boards, state regulators and utilities. Here, a tribal government is acting both as a landowner and as a political authority speaking for its citizens, and it is asking to be involved before a project becomes public.

The move is not an isolated one, but neither is it a uniform trend. The Seminole Nation approved a moratorium in March and the Kickapoo Tribe declared its opposition in July, while New York and Texas have taken different state-level steps. Together, these actions make site selection harder to predict, even though the direct reach of the Cherokee ban is limited to land the Nation controls.

Why a Sovereign Landowner Changes the Siting Equation

In a typical local dispute, a developer has several ways to keep a project moving. It can redesign the plan, offer new community benefits, appeal a decision or wait for a change in local politics. A ban set by the party that holds the land leaves fewer of those options, because the question is no longer only whether a project meets the rules. It is whether the owner will allow the project at all. On tribal-owned and trust land, that owner is also a government. Trust land is property whose legal title is held by the federal government for a tribe’s benefit.

The second part of the announcement extends the Nation’s influence, though in a different form. On non-tribal land inside the reservation, Chief Hoskin said the Nation “will not support” hyperscale projects without proper consultation. That is a statement of political opposition with conditions attached, not a ban. Its practical force will depend on what leverage the Nation can bring to bear on permits, public opinion and project partners. Even so, it adds another party to the list developers must assess before committing capital.

The people most directly affected are site-selection teams, land brokers, utilities planning for large new loads and the lenders underwriting those projects. Each now has a further question to ask about sites in this region: is the parcel tribal, and if not, has the Nation been consulted? The ban’s strength should not be overstated, however. It closes off a defined category of land, and whether any live project is affected remains an open question.

Confidential Site Selection Meets “Early and Transparently”

The sharpest operational conflict may be over timing rather than land. The task force said some projects remain under discussion behind non-disclosure agreements, which limit the public’s ability to provide input. It also said no comprehensive state or federal system tracks planned data centers, and that different databases give inconsistent estimates.

Chief Hoskin’s statement that the Nation expects companies “to engage with us early and transparently” runs directly into that practice. Developers often value confidentiality while they assemble land and negotiate for power, since early publicity can raise prices or invite opposition. A request for consultation before the plans are settled asks them to give up some of that advantage. Developers working inside the reservation will have to decide whether to approach the Nation first and accept that exposure, or stay quiet and risk formal opposition later.

Testing the 64% Figure and the 100-Jobs Claim

The survey result is the strongest public signal behind the decision, and 1,593 responses is a substantial number. Its weight still depends on how respondents were recruited and how the question was worded. A self-selected sample and a random one can produce different results, and a single percentage does not show how opinion shifts when a specific project and its terms are on the table.

The jobs argument deserves similar scrutiny from both directions. The report calls these facilities “among the least labor-intensive large structures in the economy,” saying a hyperscale site the size of a small town can employ only around 100 people once operating, alongside temporary construction work. That frames the permanent-employment question squarely, and developers cannot answer it with construction totals alone. But permanent headcount is not the entire economic case. A full comparison would also weigh lease income, tax revenue and indirect employment against the energy, water, air quality, noise, light and cultural resource concerns the report raises. Developers seeking local approval will need to bring project-specific numbers on those points.

A Patchwork Without a Federal Map

The Cherokee decision arrives amid a widening mix of responses. New York imposed a statewide moratorium on large data center projects in July, the first state to do so. Texas has ordered regulators to audit every large data center seeking to connect to its main power grid. Some lawmakers have called for a national moratorium, while the Trump administration has taken a largely hands-off approach, arguing that unfettered AI development is important for national security.

These measures differ considerably: a moratorium pauses projects, an audit examines them, a declaration signals opposition and a landowner’s ban rules them out. Treating them as one movement would blur real differences in legal effect. What they share is the consequence for planners. As Meta, Amazon, Microsoft, Google and OpenAI pour billions of dollars into AI capacity, the risk attached to a site increasingly depends on which government, or governments, have a say over it. Tribal nations are now part of that assessment in at least some regions.

Background

The Cherokee Nation is a tribal government led by Principal Chief Chuck Hoskin Jr. It created a Data Center Task Force to examine the economic, environmental, cultural and community effects of these developments across its reservation, and that group’s report preceded the ban.

The wider context is the AI buildout. Companies including Meta, Amazon, Microsoft, Google and OpenAI are investing billions of dollars in the infrastructure needed to train and run AI models, and those projects have drawn growing opposition from residents worried about water supplies, power grids and community effects. Responses now span tribal governments, states and calls for federal action.

Sources

Source: Cherokee Nation Bans Hyperscale Data Center Projects on Tribal-Owned Lands, Gizmodo’s report on the Nation’s ban, its task force findings and the wider response to data center development.