GCCURRENT
St. Paul Current
Gopher CurrentSt. Paul — capital city, championship heart

Advertisement · Why this ad?

More local news across the network →
Technology

Activists, city planners dissatisfied with Minneapolis City Council's vote on data center regulations

Marcus Chen
Managing Editor · Saturday, November 14, 2026 at 2:26 AM · 7 min read · Updated Saturday, November 14, 2026 at 7:17 AM
Minneapolis City Council debates data center regulations
In this story
  1. The Data Center Debate: A Minneapolis Story
  2. What Happened
  3. Key Regulations Explained
  4. Community Reaction
  5. What's Next

Less than 24 hours after the Minneapolis City Council narrowly passed new regulations for data centers within the city, activists and city planners alike expressed dissatisfaction with the outcome. The ordinance, which still requires Mayor Jacob Frey's approval, represents a compromise that leaves many feeling unheard, and its long-term impact remains uncertain. The regulations limit data centers to two downtown zones, restrict them to existing buildings, and mandate full council approval – measures intended to address concerns about environmental impact and community disruption. This debate highlights a broader tension within Minneapolis: the need for economic revitalization versus the desire to protect the city’s character and environment.

Activists like Kalani Matus of the Climate Justice Committee remain skeptical. He expressed concern that past regulatory failures could undermine the effectiveness of these new rules, highlighting a broader distrust in the city's ability to enforce environmental protections and a fatigue with promises of accountability. This sentiment is shared by many in the environmental justice community who have witnessed instances where polluters operated with impunity despite existing regulations, fostering a sense of cynicism about government oversight. The CJC’s past clashes with the MPCA, particularly concerning industrial pollution in North Minneapolis, have further fueled this distrust and underscore the challenges of holding powerful entities accountable.

The Data Center Debate: A Minneapolis Story

The current controversy surrounding data centers in Minneapolis isn’t new. The city has been grappling with the issue for months, fueled by the rapid growth of artificial intelligence and the increasing demand for data storage and processing. This surge in demand is driven by the rise of AI models requiring massive computing power, attracting significant investment from tech companies looking to establish a presence in the Midwest. The proposed regulations come after a six-month construction moratorium was implemented, intended to give the city time to develop standards for these facilities. This moratorium is set to expire on Nov. 21, creating a sense of urgency around the council’s decision and raising questions about whether the new regulations will be sufficient to address the potential influx of data center projects. The moratorium itself was a response to growing public concern and pressure from community groups worried about the potential environmental and social consequences of unchecked data center development.

What Happened

The ordinance, which was passed by a 7-6 vote, represents a compromise between those who sought a complete ban on data centers and those who believe they can contribute to the city’s economic revitalization. The tight margin of the vote underscores the deep divisions within the council and the community regarding this issue. The regulations themselves are detailed and restrictive, reflecting the concerns about their environmental and social impact. They include:

Key Regulations Explained

Specific Details

About This Story

Local news from St. Paul Current

Coverage Area

St. Paul, Minnesota

Section

Technology

Published

Saturday, November 14, 2026

Reading Time

7 min

Up nextMinneapolis City Council to vote Thursday on data centers, crisis responders, new police chiefTechnology · 1 min read
#city-hall#development#local-election
You're offline — showing the last loaded page