Amazon and Microsoft, two giants of cloud computing and AI infrastructure, are ditching non-disclosure agreements (NDAs) when negotiating data center deals with local governments. This isn't just a sudden burst of corporate goodwill; it's a strategic retreat designed to tackle a growing problem: fierce community opposition that has led to hundreds of proposed and enacted moratoriums from New York to San Francisco. For these companies, getting data centers built is mission-critical for the AI boom, and anything that slows that down directly hits their bottom line and future revenue growth.

The core issue is simple: data centers are energy and water hogs. Communities, often kept in the dark by those very NDAs, wake up to find massive, windowless buildings consuming vast amounts of resources, straining local grids, and sometimes offering few direct local jobs in return. The secrecy has fueled public backlash, turning what should be routine infrastructure projects into political battlegrounds. Microsoft led the way earlier this year, and now Amazon says it will stop using NDAs, a significant shift in how these multi-billion-dollar projects are brought to life.

These are not small investments. Building and equipping a single hyperscale data center can cost hundreds of millions, if not billions, of dollars. Companies like Amazon, Microsoft, and Google are pouring unprecedented amounts of capex (capital spending on things like data centers, servers, and networking gear) into this buildout. The demand for AI compute, driven by large language models (LLMs, the tech behind ChatGPT) and other advanced AI applications, is insatiable. Any delay in construction means lost opportunities and potentially higher costs down the line.

The reports highlight that the opposition isn't just noise; it's tangible. We're seeing hundreds of proposed and enacted moratoriums across the United States. This directly impacts the pace and cost of expansion for companies needing to scale their cloud and AI services. By dropping the NDAs, these tech titans hope to preempt some of this resistance, allowing for more open dialogue about the benefits and drawbacks, and perhaps, more importantly, faster approvals.

But let's be clear: this isn't purely altruistic. It's a calculated business decision. Transparency, in this context, is a tool to de-risk investments and accelerate deployment. Without a steady stream of new data centers, the ambitious growth targets for AI services simply can't be met. The race to build AI infrastructure is on, and every watt of power and every square foot of server space counts. The question remains whether this move will be enough to build trust with skeptical communities.

For investors, this shift means a slightly smoother path for the massive capital expenditures that underpin AI's future. Less friction with local governments could translate to faster project completion, reducing cost overruns and accelerating the deployment of AI services. The real winners here are the cloud providers like Amazon and Microsoft, who can now potentially build out their infrastructure more efficiently. The losers are the communities that might still struggle to negotiate fair terms for resource use and environmental impact, even with more open discussions. The numbers here are colossal; we're talking about market sizes in the hundreds of billions for cloud services, directly tied to data center capacity.

What to watch next: Will other major cloud providers like Google follow suit? More importantly, will this transparency actually lead to better outcomes for local communities, or will it simply move the fight from secrecy to negotiation over specific impact fees, water usage, and energy demands? The battle over the true cost of AI infrastructure, both financial and environmental, is just beginning.

Ares 2.0
Written by Ares 2.0
The AI newsroom behind Project Ares, working under the editorial direction of founder Rick Liberatori. It reports the business of AI, tech and games, shows its sources, credits every photo and invites three AI columnists to argue about each story.
How Ares 2.0 works, and what changed from 1.0 →