The cloud is discovering that it lives somewhere.
A data center needs land, cooling equipment and a connection to physical infrastructure. Its business may serve customers around the world. Its neighbours experience the building next door. That difference is becoming a political problem for the industry—and an opportunity for communities to negotiate before decisions become concrete.
Calling the emerging restrictions a single American “data-center ban” obscures what actually changes. A state environmental permit, a city’s land-use approval and a temporary refusal to accept new applications are different instruments. Their exceptions determine which projects can continue. Their deadlines determine when the fight returns.
Three examples show why those details matter.
New York: read the order, not just the headline
Governor Kathy Hochul issued Executive Order 62 on July 14, 2026. It covers qualifying facilities capable of consuming at least 50 megawatts, with exclusions for facilities primarily used for manufacturing, research, education or medical care.
The mechanism is specific: the Department of Environmental Conservation must hold relevant discretionary-permit applications that it had not deemed complete before the order. That hold continues until the Department of Public Service submits its final environmental-impact report and findings. Local-government permissions are explicitly outside this provision. Executive Order 62
The governor’s announcement describes the pause as lasting up to one year. The operative order ties the permitting hold to that report, a distinction worth preserving when discussing the timetable. Governor’s announcement
The political message is forceful. The legal effect is narrower than a command to stop every data-center project in the state.
Seattle: a city draws a line
Seattle’s council passed its moratorium on June 9; the mayor signed it on June 11. The ordinance establishes a 365-day pause on applications to establish or expand covered data centers, or change another use into one, throughout the city.
Its definition uses capacity above 20 megavolt-amperes, alongside other facility characteristics. Existing operating facilities have an exception for applications adding no more than 20 MVA. These are capacity thresholds, not measurements of the electricity a facility actually consumes. Ordinance 127447 and legislative history
Seattle is also studying effects on land use, public health, employment and utilities. Those questions go beyond whether a company can obtain enough electricity. They ask what a city wants its limited space and infrastructure to support. Council’s policy framework
A technically feasible project can still be a contested use of urban land.
Charlotte: the argument gets a timetable
Charlotte approved its pause on June 8. The city says it is temporarily refusing new data-center applications, with the moratorium running until November 5, 2026. City FAQ
A task force combines council-appointed community members with technical industry experts. Its recommendations are intended to feed a draft policy, public hearing and council decision. City’s engagement plan
Charlotte announced six public feedback sessions for September. As of September 7, the next scheduled meeting is September 10, followed by sessions on September 15, 25, 26 and 29. These are opportunities for input; they are not promises that residents will receive every restriction they request. Meeting schedule
The consequential document will be the policy produced when the pause ends.
Permission is part of the product
Our reading of these actions is straightforward: developers need a credible answer to the people hosting their infrastructure.
That answer should be inspectable. What noise limit will apply at the property boundary? Which water figures will be disclosed? How many permanent jobs are contractually promised? Who checks compliance, and what happens if the operator changes?
A rendering of a handsome building cannot answer those questions. Neither can an enormous investment figure. Construction spending, permanent employment and community benefit are different claims and should be examined separately.
There is also a serious argument against using pauses indefinitely. Delayed projects can mean delayed investment. Developers may choose another location. Communities that need digital infrastructure still need somewhere to put it. Seattle’s own ordinance acknowledges the economic value of processing and storage capacity and the needs of existing businesses and public services. Seattle ordinance
A moratorium earns its value through what replaces it: clear standards, public evidence and enforceable obligations. A pause without that work leaves the same argument waiting at the deadline.
What to watch next
Watch Charlotte’s draft recommendations before November 5, Seattle’s permanent rules, and New York’s environmental review. Ask whether the resulting obligations are measurable and survive a change of owner.
For developers, that may mean a less comfortable sales pitch and a more credible project. For residents, it offers a chance to judge specific terms rather than choose between enthusiasm for AI and an unconditional refusal to host it.
The AI industry can promise a different future. It still has to obtain permission to build the address.
Method: AI assisted with research and drafting. Editorial source checks used the public records linked above, reviewed on September 7, 2026. Publication was authorized by Vastkind’s publisher. No interviews or site visits were conducted.
