How Amazon and Gilroy, California, quietly negotiated a $2B data center project that AWS applied to build in 2020, without any public meetings or votes
Company and Gilroy, Calif., spent years quietly negotiating $2 billion project that few residents knew about until work began
Context & Ripple Effects
Amazon’s Gilroy project fits a longer playbook: the company has used a specialized internal team to pursue local and state incentives for major developments, as described in its earlier incentives-negotiation strategy. The difference here is that AWS’s 2020 application and years of negotiations proceeded without public meetings or votes.
The disclosure also follows reporting on Meta’s advantageous Hyperion data-center deal and a broader review finding that local officials often used NDAs and opaque counterparties for U.S. data-center proposals. Gilroy is therefore a concrete example of how hyperscaler siting negotiations can outrun public visibility.
First-order effects
- Gilroy residents are confronting a $2 billion AWS project after work began, rather than through a public hearing or vote during the negotiation process.
- Amazon and AWS secure a path for a major facility negotiated directly with Gilroy, while the city now faces scrutiny over having kept the project outside public meetings and votes.
Second-order effects
- The Gilroy case gives other municipalities and residents a direct comparison point when evaluating confidential data-center negotiations, particularly alongside the multi-state pattern of NDAs and hidden project details.
- Other hyperscalers seeking local concessions can point to opaque dealmaking as an established route, while cities may face greater pressure to justify confidentiality before construction begins.
Third-order effects
- If confidential siting becomes the standard route for large compute facilities, bargaining power shifts further toward companies able to negotiate project terms before residents know the identity or scale of a proposal.
- The resulting legitimacy gap may make public-process rules part of data-center execution risk, not merely a local political concern.
The trend: Large data-center development is increasingly testing whether private hyperscaler-municipality bargaining can retain public legitimacy once projects become visible.