Seattle has paused applications for certain large data centers. In San Francisco, protesters have urged AI-company employees to quit and city officials to act. The responses differ, but both bring an older tension into the AI boom: who benefits when tech firms grow, and what do their host cities experience in return?
Historian Margaret O’Mara’s account of earlier tech backlash offers one way to understand that tension. She links rising conflict to companies moving from suburban campuses into city neighborhoods, where their presence became harder to separate from arguments about housing and public services. That history helps explain the politics; it does not prove what AI has caused in either city.
When tech moved closer to city life
At a Seattle discussion reported Saturday by GeekWire, O’Mara contrasted Silicon Valley’s growth south of San Francisco with Microsoft’s suburban campus in Redmond, outside Seattle. For years, major tech workplaces were at a distance from the city neighborhoods that later became central to disputes over the industry.
San Francisco journalist Jonathan Weber said he encountered little tech in the city when he arrived in 1990. GeekWire places an early backlash to the dot-com boom in the Mission District in the late 1990s. In Seattle, it dates a shift toward a larger central-city tech presence to Amazon’s move into South Lake Union in 2010.
O’Mara’s interpretation is that an industry’s expansion becomes more politically visible when its companies become neighbors. Residents can judge firms not just by the jobs they offer, but by what changes around their offices. That is an account of where conflict becomes visible, not a measurement of how much any one company changed rents, taxes or city services.
The history also complicates the idea that the two cities are simply rivals. GeekWire reported that OpenAI and Anthropic have opened Seattle-area engineering centers. O’Mara noted that Bay Area venture capitalists provided early funding to Microsoft and Amazon. The regions have long been connected, even as their local disputes take different forms.
Seattle draws a line around data centers
On June 9, Seattle’s City Council passed an emergency moratorium on applications for certain large data centers. Mayor Katie Wilson signed it June 11, according to the city’s legislative record. The one-year pause gives the city time to study data-center impacts and develop policy; it is not a ban on AI or on every data center.
That distinction matters. The council acted on a question within city government’s reach: whether and under what conditions a large facility can be sited locally. The pause does not establish what effects such facilities would have on Seattle residents, or what rules the city will ultimately adopt. It turns those questions into work the city has committed to do.
GeekWire reported that more than 50 people testified at the council meeting and that councilmembers said they had received more than 98,000 emails about data centers. The figures describe participation and correspondence, not a measure of public opinion. They show how much attention infrastructure associated with the AI boom has drawn in local politics.
GeekWire co-founder John Cook described a separate Seattle tension. In his assessment, businesses feel they pay more taxes without seeing enough improvement in city services, while city leaders seek more from them as costs rise. Cook’s account conveys a business perspective; it is not an audit of tax payments or service quality.
Free newsletter
Get the morning briefing
Start each day with the AI stories that matter and why — a short, free email from our newsroom.
San Francisco’s pressures are not one protest
The San Francisco Chronicle reported that several dozen people gathered outside OpenAI and Anthropic on Sept. 17. Protesters called on employees to quit and urged city leaders to declare an emergency over their concerns about AI. Those were the protesters’ demands, not policies the city adopted or established findings about AI’s effects.
Housing poses another, distinct political pressure. Mayor Daniel Lurie announced a tenant-protection package on Sept. 10 as the city faced rising rents. A GeekWire housing report, citing Redfin, put San Francisco’s July median home sale price at $1.6 million, up 6% from a year earlier. It put Seattle’s at $809,479, down 3.6%. GeekWire connected the contrasting markets to AI wealth in San Francisco and tech layoffs in Seattle, but those figures do not isolate AI’s effect on prices.
The protest and the housing debate should not be collapsed into one backlash. One group sought action over perceived risks from AI development; the mayor’s package addressed tenants facing a costly housing market. Both involve decisions about how San Francisco responds to change, but neither supplies a complete account of what the industry has contributed or cost the city.
Weber’s strongest caution is about leverage: he argued that companies can relocate nearby, limiting what San Francisco can demand of them. O’Mara pointed to another constraint in the industry’s history, California’s 1978 Proposition 13, which limited local property-tax revenue. Together, their accounts challenge any easy assumption that a city can simply collect more from tech firms or dictate where they operate.
Limited leverage, though, is not a reason to leave local effects unexamined. O’Mara argued that AI’s novelty should not excuse avoiding regulation. Seattle has chosen to study a defined infrastructure question before setting longer-term rules. For both cities, the more useful test is identifying which effects local policy can address and producing evidence strong enough to justify the decisions that follow.