Across U.S. towns and suburbs, a building type that rarely drew attention is now filling meeting rooms: the data center. For many, the stakes feel personal and immediate: electricity bills that have already climbed, familiar rural landscapes giving way to industrial campuses, and the fear that the next big project will deliver noise, diesel exhaust, and water stress while creating fewer permanent jobs than the hype suggests.
Developers chasing ever larger sites to support the growth of artificial intelligence and cloud computing are running into a wave of organized local resistance. Where residents once treated zoning hearings as an afterthought, they now show up early, coordinate on social media, and pressure local boards to reject proposals outright. In Pennsylvania’s East Vincent Township, resident Larry Shank framed the conflict in backyard terms: “Would you want this built in your backyard?” he asked supervisors. “Because that’s where it’s literally going, is in my backyard.”
For the data center industry a powerful ecosystem of Big Tech firms, real estate developers, electric utilities and labor groups this shift forces a new kind of project risk. Andy Cvengros, who helps lead the data center practice at JLL, said opposition tactics have escalated fast. “It’s becoming a huge problem,” he said, describing recent deals where opponents canvassed neighborhoods, handed out shirts and planted yard signs.
Pushback has also turned into measurable friction for project pipelines. Data Center Watch, a project of 10a Labs, said it counted 20 proposals valued at $98 billion in 11 states that were blocked or delayed over a three month period two thirds of the projects it was tracking. In Indiana, Bryce Gustafson of the Citizens Action Coalition said local resistance has surged beyond anything he has seen. “I’ve been doing this work for 16 years, worked on hundreds of campaigns I’d guess, and this by far is the biggest kind of local pushback I’ve ever seen here in Indiana,” he said.
The reaction of the resident is less to the internet itself than to its physical footprint needed to keep it always on. Data centers are built for reliability measured in “five nines” 99.999% uptime driving decisions on redundancy that spill into land use, power planning, and local permits. They can require massive grid connections and, in many climates, steady cooling capacity that translates into water demand. Technical debates that used to live in utility dockets rules around curtailment, interconnection queues, cost allocation now pop up in township halls as constituencies try to figure out who pays when a project needs new lines, new substations, or new generation.
Already, a surge of proposed large load hookups in California has pushed questions about planning and cost responsibility into the regulatory mainstream. For data centers alone, developers have asked for 18.7 gigawatts of serving capacity, according to the California Energy Commission, on a scale that helps explain why consumer advocates have argued over whether households could end up absorbing infrastructure costs when forecasts of demand shift.
The local concerns that dominate public comment periods tend to cluster around a handful of stress points. Electricity is often the first. In communities where residents have watched rates rise, the arrival of a single new load sometimes described as rivaling a small city can feel like a direct threat to affordability, even if the mechanics are buried in tariffs and planning rules. In Matthews, North Carolina, a proposed project promised environmentally friendly features and revenue large enough to cover half the city’s budget. It still faced such overwhelming opposition that Mayor John Higdon said developers were told it would be defeated unanimously. He described the incoming message traffic to city officials as “999 to one against.”
Water is often the second flashpoint, particularly where wells, aquifers or reservoirs already feel stretched. Research and policy briefings have pointed to large facilities that can reach up to 5 million gallons per day for cooling in certain designs and climates, putting data centers into the same resource category as other major industrial water users. Timing and disclosure are usually the municipal controversy: residents want clear numbers early enough to influence site decisions, not after land is acquired and power secured.
Air quality and noise may be considered secondary, but can be deciding factors in close neighborhoods. A typical modern data center has backup generation, usually diesel, to protect uptime. Federal rules limit non emergency testing to 100 hours, up to 50 hours of which may be used for demand response programs, but residents’ concerns tend to focus less on annual hour counts than on what those engines mean for daily life: periodic testing noise, perceived health exposure, and the optics of large fuel tanks beside a facility marketed as digital and clean. In Washington state, regulators explicitly track permitting and combined impacts from diesel powered backup generators at data centers, illustrating how the “invisible cloud” becomes a visible local question of emissions.
Then there is the jobs argument often the sharpest edge of the “job killing AI” claim residents bring into hearings. The facilities can create enormous construction activity, and some projects generate substantial tax revenue. But ongoing staffing is limited compared with other land uses that occupy similar acreage, a mismatch that can fuel skepticism when developers pitch a campus as an employment engine. In practice, the employment profile becomes part of a larger calculus: if a town gives up farmland or green space, absorbs truck traffic during the construction process, and accepts a long lived industrial neighbor, residents want durable benefits commensurate with the scale of resource use.
Developers and their boosters have shifted course in predictable ways, touting community engagement earlier in the process and offering design commitments intended to mollify the most common complaints. Dan Diorio of the Data Center Coalition called it an internal industry priority to get better at outreach. “It’s definitely a discussion that the industry is having internally about, ‘Hey, how do we do a better job of community engagement?’” he said.
But process not just impacts often fuels community anger. In Hermantown, Minnesota, residents opposing a proposed campus said they felt blindsided upon learning the project had been discussed internally among officials for a year before internal emails became public. Realtor Jonathan Thornton, who lives across the road from the site, said the issue wasn’t only one of scale or resource use. “It’s the secrecy. The secrecy just drives people crazy,” he said. The project’s developer, Mortenson, said it is considering changes based on public feedback and that “more engagement with the community is appropriate.”
As opposition mounts, developers are also reassessing the way they value a site. Maxx Kossof, vice president of investment at The Missner Group, explained a strategy shaped by this new reality: land can become more valuable if power is secured, even when zoning might look uncertain. “You might as well take chips off the table,” he said. “The thing is you could have power to a site and it’s futile because you might not get the zoning. You might not get the community support.”
That dynamic power first, permission second is part of why local boards are rewriting ordinances, adding special exceptions, and requiring impact reports that quantify electricity and water needs. The emerging fight is not over whether data centers exist modern life routes through them constantly but over where the costs land, what disclosures arrive before decisions get locked in, and whether the AI era buildout can fit inside zoning systems designed for smaller, slower moving development.
