Amazon bypassed Gilroy’s public right to decide what gets built.
The company received approval last July for a 438,500-square-foot data centre on 56 acres of farmland between a Walmart Supercenter and the Gilroy Premium Outlets. The project is valued at $2 billion. Construction began before many residents knew there was a project to oppose.
This is not a story about a loophole discovered by accident. It is a story about an industrial zoning code doing exactly what it was written to do 45 years ago, while the thing being built under that code had changed beyond recognition.
Amazon Web Services applied in 2020. The parcel was zoned for industrial development along a freeway. The city conducted an environmental review, and a community-development director approved the project with a single signature because it fit the existing zoning category. That approval was legally sufficient under the city’s rules. It also eliminated any public vote and any planning-commission decision.
The zoning code answered a narrow question: does this proposal fit the category? It did not answer the question residents actually needed answered: what will this particular facility do to water, fire safety, land use, tax capacity, and the town’s future?
Those are different questions. Treating them as one is how public authority disappears into a checklist.
It is true that Amazon followed the formal process, in the narrow sense in which a process can be formal while the people affected by it remain functionally absent. Amazon says the project included public notices and public-comment periods. The environmental-review comment period closed in September 2024. The trouble is that a comment period no one knows exists is not a meaningful public decision. It is an administrative event that later permits the institution to say the public was invited.
Gilroy residents learned about the project after construction had begun. Coleen Crew, an elementary-school teacher, told the city council that “many if not most residents” first learned about it at that point. Landon Sepulveda, a 21-year-old college student organising opposition, put the practical problem more plainly: people have jobs and lives. They elected officials to tell them what was happening, not to require them to watch over the officials’ shoulders.
Rosa Rodriguez raised concerns in February about the damage data centres can cause in a drought-stricken state. A city planner told her the comment period was over.
This is not public participation. It is the paperwork-shaped imitation of public participation.
A town cannot hold a referendum on every warehouse, factory, or loading dock. Government needs delegated authority, and not every land-use decision deserves a civic pageant. Mayor Greg Bozzo pointed to a food-distribution centre that arrived without public engagement and caused no uproar.
That comparison proves only that Gilroy’s rules are broad. It does not prove that they are adequate.
A warehouse stores goods. A data centre converts electricity, cooling capacity, land, water, fibre connections, backup systems, and public infrastructure into computational capacity. Its physical footprint is only one part of the facility. The rest is distributed across the utility system, the water system, the road network, the emergency-response apparatus, and the public balance sheet.
That is the engineering distinction the zoning category cannot see.
A data centre is not a mysterious cloud. It is a large industrial machine with a building around it. The servers consume electricity. Cooling systems reject heat. Battery systems introduce a fire-safety question. Water systems support operations. Telecommunications links connect the facility to a cloud platform operating at a much larger scale.
The technical specification is not a brochure. It is the set of physical demands the town must absorb.
“Industrial” tells residents where a building sits in a zoning table. It does not tell them how much clean water the facility will use, what battery systems will be installed, how fire crews are expected to respond, or which costs remain public when a private project receives permission to proceed.
Gilroy’s residents are especially concerned about water because this is a drought-scorched community. The facility will use clean water until a wastewater system is built. Amazon has promised to construct, at its own expense, a pipeline bringing wastewater to the site.
That may be useful. It does not change the sequence. The immediate public consequence arrives before the promised mitigation.
Private spending does not turn a public resource into a private matter. Amazon can pay for a pipeline and still depend on municipal water rules, emergency services, roads, permitting staff, and the region’s finite water supply. A company cheque can cover a cost without answering who controls the decision, who bears the risk if the system is delayed, what happens when the facility operates for decades after the original officials have left office, or what remedy applies if the promise is not kept.
The same problem appears in the fire-safety correspondence. When residents raised concerns about battery fires, including the Moss Landing fire, Gilroy’s fire marshal wrote that officials should limit the technical detail distributed publicly because Amazon’s fire-suppression systems were proprietary. An Amazon official replied that he would determine what the company was “allowed to share with the public.”
This is the wrong direction of authority.
A proprietary system is a system whose owner controls the information needed to evaluate it. That may be commercially understandable. It is not automatically a public-safety justification. A private company may own its technical design. It does not own the public’s right to understand the hazards that design creates.
The word “proprietary” is not a technical conclusion. It is a claim about ownership. It tells us who controls the information, not whether withholding it protects the public.
A system that cannot be described well enough for the people responsible for responding to its failure is not merely private. It is an accountability problem.
This is the basic mistake made whenever a company’s description of its own machinery is accepted as a substitute for examining what the machinery does. The name on the machine is never the specification. The specification is what happens when you turn it on.
The city and Amazon negotiated for five years. Emails from that negotiation show Amazon pressing against delays after the project had fallen more than a year behind schedule. City staff eventually wrote that a matter was “no longer up for discussion.”
That is the familiar shape of a private negotiation being mistaken for public governance: the company knows what it wants, the officials know the deadline, and residents enter only after the meaningful choices have been made.
The record does not show a single villain overriding a democratic process. It shows a company pressing for speed and a city government treating public visibility as something to manage rather than something the public was owed.
The political economy is straightforward. Amazon benefits from speed, secrecy, and administrative classification. The city receives the immediate appearance of investment. Residents receive a completed project and the opportunity to comment on its consequences.
That is not a market failure in the narrow textbook sense. It is a governance failure produced by a mismatch between private scale and public procedure. Amazon can negotiate across five years with lawyers, engineers, planners, and project managers. An ordinary resident cannot devote five years to discovering whether a project exists.
The benefits are real. Amazon has promised tax revenue, construction jobs, a $1 million contribution toward a new firetruck, grants to local nonprofits, sponsorship of the Gilroy Garlic Festival, and the wastewater pipeline. Mayor Bozzo is entitled to count those benefits.
They should not be allowed to purchase silence.
A firetruck is useful. It does not turn a closed approval process into an open one. A firetruck is not a substitute for fire-safety disclosure. A festival sponsorship is not a public hearing or a planning process. Tax revenue does not make water abundant. The garlic festival, admirable though it may be, is not a municipal constitution.
The same pattern is now appearing elsewhere. Recall campaigns are targeting officials over data-centre approvals because residents are discovering that the formal existence of an approval does not settle whether the approval process deserved their trust. Residents in California’s Imperial Valley are fighting a proposed $10 billion data-centre development. Communities in Georgia are seeking a referendum over a rural facility. Seattle has taken the opposite route and enacted a year-long ban on new AI data centres.
These are not isolated episodes of local nervousness. They are evidence that ordinary permitting machinery is being asked to govern an industrial buildout it was not designed to see.
The missing constraints were public notice early enough to matter, independent review, accessible technical information, and a meaningful ability to refuse or reshape the project. Remove those constraints and a process can remain formally legal while becoming substantively unaccountable.
I learned the basic version of this in my father’s workshop, where a machine was not judged by the label painted on its side but by the loads it placed on the bench, the wiring, the bearings, and the person expected to repair it. The name on the machine was never the specification. The specification was what happened when you turned it on.
Gilroy’s officials are now considering the sensible correction: future data-centre projects would require planning-commission approval, community meetings, and notice to nearby residents. That should be the minimum, not the concession. It should apply before the project becomes a construction site, before the environmental-review window closes, and before opposition becomes largely ceremonial.
Gilroy should require plain-language disclosure of water demand, wastewater timelines, backup-power systems, battery chemistry, fire-suppression systems, emergency-response plans, tax arrangements, enforceable mitigation conditions, and the cost of every public commitment. The city should distinguish what Amazon says from what the facility is physically required to do. It should not permit “proprietary” to become a general-purpose blackout over public safety.
Planning-commission review is not a veto by every neighbour over every building. It is an institutional checkpoint for projects whose effects cross the boundaries of an ordinary industrial parcel. Community meetings are not a demand that residents design the facility. They are the minimum condition for residents to know what is being built beside them while there is still something they can change.
The remedy is not to reject every data centre. It is to make the project answerable to the town it uses. Planning-commission review, early community meetings, independent technical review, public water conditions, accessible engineering records, and enforceable fire-safety requirements would restore the missing pieces: information, voice, and a meaningful chance to say no.
A 45-year-old industrial category may be administratively convenient, but convenience is not a theory of public consent.
Gilroy elected officials to tell residents what is happening before they have to discover it by watching construction equipment arrive. The residents are not asking to run Amazon Web Services. They are asking to see the plans, understand the risks, and retain a usable voice before the concrete hardens.
A public meeting held after the excavators arrive is not engagement.
It is customer service for a decision already made.