How to Stop a Data Center Near You.

The short version: You can fight a data center, and people are winning. In the first three months of 2026, community groups blocked or delayed at least 75 projects worth about $130 billion — the most in any quarter on record. There are now 833 active groups across 49 states. Seattle's city council voted to pause new large data centers 9 to 0. None of that took special expertise. It took showing up early, with neighbors, with the right two questions. This is the playbook.

Why This Fight · The Window · The Five Moves · The Two Questions · The Seattle Model · Tools

Why This Fight Is Winnable

Most fights against big capital feel hopeless because they happen somewhere you can't reach: a boardroom, a statehouse, a federal agency. The data-center buildout is different. It has to touch the ground. It needs your land, your power grid, your water, your zoning variance. And those decisions get made in a room small enough to walk into: a county planning commission, a city council, a board of supervisors.

That's the whole opening. The industry's story is inevitability — $700 billion in spending this year, a race against China, no city has the right to slow it down. The reality is that a 9-0 vote in the most tech-saturated big city in America just called the bluff. In Monterey Park, California, voters approved the first permanent municipal data-center ban in the country with 86% of the vote. Baltimore, Denver, and Minneapolis all passed pauses inside a single month. Gallup asked Americans about data centers for the first time this spring and found 71% don't want one near them, higher opposition than nuclear plants draw.

You are not the outlier for objecting. You're the majority. The job is to get the majority into the room.

The Window

This is the single most important thing on the page: the fight is won or lost early.

A data center is hardest to stop the day before groundbreaking and easiest to stop before the site is even chosen. Once a developer has a signed agreement and sunk costs, you're fighting uphill against a permit. Before that, while it's still a rezoning request, a special-use permit, a utility-hookup application, a tax-abatement vote, a few organized people can change the outcome.

So the first move isn't a protest. It's a calendar. Find your county or city's planning-commission and board-of-supervisors agendas, and start reading them every week before the data-center item shows up on one. The groups that win intervene before site selection is final and lobby state legislators before the developer is locked in. The groups that lose find out at groundbreaking.

The Five Moves

The communities that are winning do roughly the same five things.

1. Build the calendar.

Track every relevant public meeting — planning commission, council, county board, utility board. Public bodies have to post agendas in advance. Put the data-center-adjacent items on a shared calendar your group watches. This is how you keep the window open.

2. Coalition before content.

The Seattle endorsement letter carried 50-plus organizational signatures — teachers next to hotel workers next to climate groups next to retirees. Breadth is the weapon. A data center hits utility bills, water, noise, air, traffic, and property values, which means it gives you a reason to call almost every group in town. Map them. Ask each for one signature and one body in the room.

3. Bring the bill, not the vibe.

The argument that moves a swing vote isn't "we don't like it." It's "here's what it costs us." Ratepayers subsidizing corporate power demand. Water draw in a place that's already short. Property values near a humming, lit, 24/7 facility. Few permanent jobs for the acreage and the abatement. Pull the actual numbers for the actual project. Local officials can ignore a feeling. They have a harder time ignoring a load figure and a rate impact in front of a full room.

4. Fill the room, then fill it again.

A vote is not the end. Seattle's ordinance requires a public hearing within 60 days, and permanent zoning won't be settled until early 2027 — which means the room that was full on vote day has to be full again, repeatedly. Plan for the long meeting, the follow-up meeting, and the one after that. Persistence is the thing developers are betting you don't have.

5. Look for the inside voice.

The most damaging testimony in Seattle came from Amazon's own engineers, on the record, doing the math on their employer: $200 billion in capital spending, 30,000 colleagues cut in eight months. If anyone in your coalition works in tech, in the utility, or in local government, their testimony lands harder than a hundred reposts. Find them. Make it safe for them to speak.

The Two Questions

When the developer's representative is at the podium promising jobs and tax revenue, you don't need a speech. You need two questions on the record:

Watch how fast the answers get vague. Vague answers, in the minutes, in front of the press, are how a project loses momentum. You're not trying to win a debate. You're trying to put the cost on the record before the vote.

The Seattle Model, in One Paragraph

Here's the whole thing to copy. In April, four companies approached Seattle's public utility about five large data centers totaling enough power for 300,000 homes, in a city of 750,000. Residents didn't wait. By the June committee hearing, Amazon's own engineers were testifying for limits. By the June 9 vote, more than 50 people had signed up to speak and not one spoke for the data centers. The council voted 9-0 for an emergency moratorium on new large facilities while the city studies the grid, water, rates, and jobs. Coalition first. Numbers second. Inside voices third. A full room, then a fuller one. That's the model, and it's portable.

Tools We Built for You

You don't have to start from a blank page. We maintain the infrastructure this fight runs on:

And if you want to do this under a banner instead of alone, that's what we're for.