Why This Matters for Woodbury
Woodbury is not facing data center expansion in isolation. Across Minnesota, cities have struggled with similar issues: hidden projects, rapid expansions, regulatory gaps, and pressure to approve developments that significantly impact infrastructure and neighborhoods.
Eagan's May 2026 permit denial is the most direct precedent. The same operator proposing expansion in Woodbury had a 5-0 council vote against them in a nearby city, citing noise, unpermitted equipment, and lack of transparency. This case shows that:
- Continuous noise monitoring (24-hour, 1/3-octave per Minnesota Rules 7030) is now a standard expectation
- Equipment must be permitted before operation, not retroactively
- Public disclosure is non-negotiable
- Councils can say no to expansion when facts are unclear
Minnesota Data Center Initiatives by City (2023–2026)
| City |
Project / Operator |
Timeline |
Status & Outcome |
Key Issue |
| Eagan |
IronGate Capital (same as Woodbury 401 & 500) |
Permit denial May 19, 2026 |
DENIED 5-0 |
Noise exceeds state limits; unpermitted equipment; transparency gaps |
| Hermantown |
Project Loon (operator name not disclosed) |
Feb 2024 disclosure (1 year hidden) |
Hidden; delayed disclosure |
NDA secrecy; residents unaware of project during construction |
| Rosemount |
Project Bigfoot (operator name not disclosed) |
2023–2024 (timeline unclear) |
Hidden; NDA enforcement |
Developer secrecy; public excluded from planning |
| Becker |
Data center project (operator unknown) |
2023–2024 (ongoing) |
Limited public information |
Lack of transparency in feasibility / permitting stage |
| Pine Island |
Data center project (operator unknown) |
2023–2024 (ongoing) |
Limited public information |
Lack of transparency in feasibility / permitting stage |
| Woodbury |
IronGate Capital (401 & 500 Bielenberg) |
401: operational 2025; 500: operational March 2024 |
Interim ordinance approved Sept 23, 2026 |
Same operator as Eagan denial; same regulatory gaps; expansion planned |
Note: "Project Bigfoot," "Project Loon," and other code names indicate NDAs preventing public disclosure. This is a common pattern: developers use secrecy agreements to prevent informed public participation until projects are underway or approved.
City-by-City Stories
🔴 Eagan — Permit Denial (May 19, 2026)
- Operator: IronGate Capital (Ned Abdul / Swervo Development Corp.)
- Project: Data center expansion
- Decision: DENIED 5-0 by City Council
- Grounds: (1) Noise exceeds Minnesota Rules 7030 limits; (2) Equipment operated without permits; (3) Lack of transparency
- Impact: Operator's representative answered "I don't know" 15+ times when asked about equipment, capacity, and timeline
- Lesson for Woodbury: Same operator; same issues (no noise study, no formal data center use determination, equipment installed before permits). Eagan's precedent shows this council can say no.
- Source: City of Eagan Findings of Fact (May 19, 2026); ESI noise study (March–April 2026)
🟡 Hermantown — "Project Loon" (1-Year Secrecy)
- Discovery Date: February 2024 (1 year after project began)
- Issue: Data center project hidden under NDA; residents unaware during construction phase
- Public Reaction: Community learned about project only when zoning or construction permits were being finalized
- Lesson for Woodbury: Secrecy agreements delay public input and make course correction harder. Interim ordinance must require advance disclosure.
- Source: Regional news reports; Hermantown city records (public disclosure delayed)
🟡 Rosemount — "Project Bigfoot" (Hidden Developer Plans)
- Status: Data center project under NDA
- Issue: Developer using confidentiality agreements to exclude public from planning
- Pattern: Similar to Hermantown: secrecy prevents informed city council decision-making
- Lesson for Woodbury: NDA patterns are widespread. Interim ordinance study should include disclosure requirements.
- Source: Regional reporting on Minnesota data center secrecy pattern
⚪ Becker & Pine Island (Limited Transparency)
- Status: Data center projects reported; limited public records available
- Issue: Early-stage projects; operator and scope not widely disclosed
- Pattern: Consistent with regional trend toward developer-led secrecy
- Lesson for Woodbury: Other Minnesota cities face same disclosure challenges
Regional Pattern: The NDA Secrecy Problem
Across Minnesota, data center developers use non-disclosure agreements (NDAs) to keep projects hidden during feasibility and early permitting phases. This pattern:
- Prevents public participation: Residents learn about projects only after construction is underway
- Delays council transparency: Cities must approve projects with incomplete public input
- Creates regulatory gaps: No state law requires advance disclosure of data center projects
- Shifts power to developers: NDAs give companies a 12–18 month head start before public scrutiny begins
Woodbury's advantage: The city approved an interim ordinance (Sept 23, 2026) authorizing a comprehensive study through 2027. This delay creates an opportunity to close disclosure gaps before expansion permits are approved.
What Eagan's Denial Means for Woodbury's Expansion
IronGate Capital was denied in Eagan on May 19, 2026 — just 4 months before Woodbury approved its interim ordinance. The timing matters:
| Date |
Event |
Implication |
| May 19, 2026 |
Eagan denies IronGate permit 5-0 |
Same operator; same issues; council on record with findings of fact |
| Sept 23, 2026 |
Woodbury approves interim ordinance |
City can review Eagan findings before 401 & 500 expansions are approved |
| 2027–2028 |
Comprehensive study period |
Opportunity to adopt Eagan's fixes: noise monitoring, equipment nameplate locking, disclosure requirements |
Critical Question for Council: Why did Woodbury not require the same noise study and equipment disclosure that Eagan demanded, given the May 2026 denial was already on record?
Lessons & Questions for Woodbury
What Eagan Required (May 2026):
- Continuous 24-hour noise monitoring (Minnesota Rules 7030, 1/3-octave analysis)
- All equipment permitted BEFORE operation (no retroactive installation)
- Public disclosure of capacity, timeline, and noise mitigation plans
- Applicant must answer factual questions (no "I don't know" on core operations)
What Woodbury Currently Requires:
- ❌ No continuous noise study on file for either facility
- ❌ No formal data center use determination (operating under outdated "office" permits)
- ❌ No equipment nameplate capacity locking (equipment can be upgraded as "repairs")
- ❌ No formal disclosure requirement for expansion capacity or timeline
Questions for Interim Ordinance Study:
- Will Woodbury adopt the same noise monitoring standard (Minnesota Rules 7030) that Eagan used?
- Will mechanical permits be locked to nameplate capacity to prevent "repair" loopholes?
- Will data center use be formally defined in Woodbury Code Chapter 24?
- Will disclosure requirements prevent future "Project Loon" / "Project Bigfoot" secrecy in Woodbury?
Sources & References
Eagan City Council Decision (May 19, 2026): Findings of Fact; ESI Inc. noise study (March–April 2026); applicant transcript (15+ "I don't know" responses)
Regional Precedent: Minnesota Reformer, Minnesota Daily, Woodbury News reports on data center secrecy patterns (2023–2026)
Woodbury Interim Ordinance: Approved September 23, 2026; authorizes comprehensive study through 2027
Minnesota Rules 7030: Noise monitoring standards for industrial facilities; continuous 24-hour, 1/3-octave analysis