phone Ready to learn more?
Call phone number to talk with an Odin representative today.
Public sentiment is now the #1 concern in data center construction — and it’s changing everything inside the fence. If you’re smart, you’ll start looking outside the fence too.
Public sentiment is now the #1 concern in data center construction — and it’s changing everything inside the fence. If you’re smart, you’ll start looking outside the fence too.
For the past decade, data center projects stalled for familiar reasons. Power access. Supply chain. Labor. Everyone knew the variables. Everyone had a mitigation plan.
That changed. The variable that now determines whether a project breaks ground — or gets shelved permanently — is public sentiment.
At this year's New York Build conference, Rob LoBuono, principal at Gensler, said it plainly: "The number one concern we have in the market right now is public sentiment." Not a throwaway line. A structural observation from someone who builds these things for a living.
According to research from Baird analyst Justin Hauke, project cancellations jumped to 25 in 2025 — up from six in 2024 and two in 2023. That's more than a fourfold increase in a single year. According to Data Center Watch, an estimated $64 billion in data center projects have been blocked or delayed nationwide due to community opposition. At least 188 organized local opposition groups are now active across 40 states, and moratorium legislation has been introduced in 11 states in 2026 alone.
Maine’s legislature passed an 18-month moratorium bill this spring — the governor vetoed it on April 24, 2026 — but the political pressure it represents is spreading fast. Similar legislation is now advancing in New York, Georgia, Oklahoma, and Michigan. In Virginia, a major campus near the Manassas National Battlefield was shelved under community and legal pressure. In Indianapolis, Google quietly withdrew a data center rezoning request after hundreds packed a city council meeting — overflow rooms required, loud cheers from the crowd when Google pulled out. In St. Louis, a February 2026 public hearing ran four hours, with the vast majority of speakers demanding an outright ban. These aren’t edge cases. They’re the new normal.
The opposition has organized. It has political cover. And it knows exactly where projects are most vulnerable — permitting. A community benefits plan used to be optional. It's not anymore.
That’s the national picture. Nothing captures the intensity of this shift — or its implications for every project in the ground — like what’s happening right now in Michigan.
In Indianapolis, one of America’s most recognizable technology companies withdrew a data center rezoning request before the city council could even vote on it. Hundreds of residents had packed the chambers — overflow rooms required. They held signs. They waited. When Google announced it was pulling the request, the room erupted in cheers. The council member who led the opposition summarized his constituents’ concerns in three words: “quality-of-life impacts.” No complex environmental review. No legal ambush. A room full of people who showed up and made the math undeniable.
Indianapolis is not an outlier. On May 1, 2026, the New York Times ran a video report with a headline the industry is still processing: “Data Centers: The Issue Uniting Liberals and Conservatives.” The story spans the country — Indiana, Georgia, Oregon, North Carolina, Tennessee, Michigan. Moratoriums. Packed town halls. State legislative battles. The opposition is methodical. It is cross-partisan. And it learns from every project it fights.
The Times reported from Lyon Township, Michigan — a community that voted Republican in the last election — where a routine monthly board meeting was standing-room-only even though the main agenda item was a drain easement. A resident in a pink shirt played a recording of noise from a nearby data center. When her time expired, she refused to stop: “I haven’t even gotten off my first page.” That’s the room. That’s the political temperature. And it exists across every demographic, in every region, around contested projects from coast to coast.
Organized communities are disciplined watchers. They document everything. A construction vehicle running without authorization. A noise complaint at 2 a.m. that lands on social media by morning. A drone capturing footage the project team never knew existed. Once that material enters a community’s narrative, it doesn’t come out. Every GC and owner on a contested site will be scrutinized. The question is whether they’ll be accountable when they are.
On one of the most high-profile contested data center sites currently under construction in this country, Odin is deployed. Online threat monitoring and mitigation — tracking organizing activity, forum discussions, and coordinated disruption planning before it ever reaches the gate. Drone and counter-drone technology — active awareness of the airspace above the site and the ability to respond. Mandatory security training for every worker before they access the project. The documentation exists. The awareness is real-time. When regulators ask questions, the answers are there. That’s not a communications strategy. That’s accountability built into the operational infrastructure from day one — which is the only place it works.
When the gating question shifts from “can we build this?” to “will this community let us build this?” — everything inside the fence looks different.
Two years ago, site access policy was not much more than a compliance checkbox. OSHA requirements. Subcontractor liability. Insurance carrier boxes to check. Nobody was thinking about it as a community relations tool.
Today it's strategy. A project isn't just accountable to the owner and the GC anymore. It's accountable to the township that issued the permit, the utility managing grid impact, and the residents filming drone footage for local Facebook groups. Every incident on site feeds a narrative that opposition groups are actively building. A gate fight. An unauthorized vehicle. A safety violation caught on camera. All of it.
You can't manage that with clipboards and end-of-shift headcount reports. The scrutiny is real-time. The response has to be too.
Run the numbers on a modern hyperscale build. Three or more CMs. Dozens of subcontractors. Thousands of workers rotating through on shifting schedules. Gigawatt-scale power infrastructure. Multi-year timeline. The complexity is manageable — if it’s visible. The problem is when it isn’t.
Invisible means you don’t know who’s on site right now. You don’t know if a credential expired two weeks ago and nobody caught it. You don’t know that the vehicle that came through the east gate at 2 a.m. had no business being there. You don’t know that an opposition group has been coordinating a disruption on a private forum for the past three weeks.
That kind of invisibility used to be tolerable. The margin for error was wide enough. It isn’t anymore. One incident — documented, amplified, shared — can reopen permit battles, trigger regulatory inquiries, and cost you months. The risk environment changed. The operational posture has to catch up.
This isn’t a communications problem. It’s an operational one. And it gets solved the same way every operational problem gets solved — with the right systems and the discipline to run them.
The threats that show up at your gate started somewhere else. Organized opposition doesn’t appear at the fence line. It builds over weeks — on social media, community forums, private groups. Protests get planned. Workers get doxxed. Coordinated disruption gets organized and shared long before anyone acts.
You need to know about it before it reaches the gate. Not from the local news. Not from a contractor who heard something. Around-the-clock monitoring — surface web, social media, relevant forums — validated by human analysts who can tell the difference between noise and a real signal. Early warning is the whole point.
Every vehicle on site should be verified. Every entry and exit logged. The audit trail should exist and it should be clean.
Automated license plate recognition closes the gap that manual logs leave wide open. When a regulator asks who was on site between midnight and 4 a.m. last Tuesday, the answer shouldn’t take three days to compile from paper records across five contractors. Three clicks. A report. That’s what accountability actually looks like to a regulator or a community board that’s already skeptical.
Jobsites have an air problem now. Most still don’t know it.
Activist groups figured out early that a consumer drone goes where a fence doesn’t. The footage ends up on social media. The narrative gets written by whoever posts it first. And that’s just the lowest-stakes version of the problem. Surveillance drones. Competitive intelligence gathering. Hostile drone activity near critical infrastructure. All real. All increasing.
Anti-drone detection isn’t a specialty for government facilities anymore. It’s a practical requirement for any hyperscale site operating in a contested community environment.
Every worker on site should be verified. Every credential current. Every zone access authorized. That’s the baseline — and it’s not consistently happening.
Ghost workers exist in headcount reports but not in reality. Expired certifications don’t get flagged until something goes wrong. Unauthorized people in restricted zones are a security failure that turns into a reputational one the moment anyone documents it. These aren’t theoretical risks. They show up on real projects.
Digital onboarding. Real-time certification tracking with expiration alerts. Zone-level access authorization. The workforce coming through your gate should be who they say they are, credentialed for where they’re going. That’s what you owe the project — and increasingly, that’s what you owe the community watching.
If something happens, you need to know immediately. Not in the morning report. Not when someone calls it in. If a regulator asks who was on site, you show them — you don’t spend 48 hours compiling an answer. If a community leader asks whether the site is being run safely and accountably, you answer with documentation. Not assurances.
Real-time workforce visibility gives you that. A live dashboard — who’s on site, by trade and subcontractor, with access logs, incident documentation, activity monitoring. The ability to answer questions fast, completely, with a record that exists. That’s what separates projects that survive scrutiny from the ones that don’t.
Most site security programs aren’t missing a specific tool. They’re missing integration. Digital threat monitoring runs in one system. Access logs in another. Camera feeds on a separate screen. Credential records in a spreadsheet somewhere. When an incident happens, piecing together what occurred means pulling from five systems that don’t talk to each other.
A threat flagged in a monitoring alert doesn’t automatically tighten access controls. A credential issue doesn’t surface in the command center. A vehicle anomaly doesn’t connect to workforce activity data. Disconnected awareness is no awareness — not in the moments that matter.
One platform. One pane of glass. Digital threat monitoring, license plate recognition, drone detection, workforce credential management, real-time site visibility — all feeding the same picture. When something happens, the response is informed. When a regulator asks, the answer is there. When a community stakeholder asks, the documentation exists.
That’s not a feature checklist. That’s the operational infrastructure for permission to operate.
The build cycle isn’t slowing. Hyperscalers and neoclouds are still committing to gigawatt-scale projects. The capital is there. The demand is structural.
What changed is the cost of operating without community trust. When 188 organized opposition groups are active and cancellations are running at four times last year’s rate, the projects that get built aren’t necessarily the best funded or the best designed. They’re the ones that can demonstrate accountability — to regulators, to communities, to the public record.
That starts inside the fence. Knowing who’s on site. What’s happening in your airspace. What threats are organizing against you online. Whether your workforce is credentialed, authorized, and accounted for.
That’s not nice-to-have. That’s permission to operate.
Tell us a little about your project and we’ll send you a personalized invitation to try Odin for yourself.
Join our newsletter for industry updates, product innovation, videos, and more.
