Project dossier · Fort Wayne, Indiana

Google Fort Wayne Operating

Data center by Google in Fort Wayne, Indiana. Operating.

Key facts

Operator: Google
Owner: Google
Tenant: Google DeepMind
Location: Fort Wayne, Indiana
Stage today: Operating

Source
read 2026-08-14

What to do next

Next step: Already operating — the leverage now is enforcement: noise and water conditions, tax revenue tracking, and any expansion filing, which reopens the record.

Build an action pack for this project →

What has happened so far (20 events)

2023-11-01coverage
Neighbors voiced concerns about 'Project Zodiac,' a proposed data center by an unnamed Fortune 100 company on southeast Fort Wayne land, following an October 25 neighborhood meeting; residents cited noise and health worries. · source
2023-11-16vote
Allen County Plan Commission unanimously approved annexation of 728 acres of county land into Fort Wayne for the Project Zodiac data center; residents expressed frustration at the decision. · source
2023-12-01vote
Allen County Commissioners voted 3-0 to approve the 728-acre Project Zodiac annexation near East Paulding Road and Adams Center Road, the final annexation vote required for the project. · source
2024-04-01announcement
Google was identified as the company behind 'Project Zodiac' at a groundbreaking ceremony in April 2024, announcing a $2 billion investment and approximately 200 jobs at the Fort Wayne data center campus. · source
2024-07-01hearing
IDEM held a public meeting on July 1 at Ivy Tech Community College to discuss the draft Hatchworks LLC air permit for Google's data center; the public comment period closed July 8. · source
2025-08-04filing
Indiana Michigan Power and Google filed a joint demand-response contract with the Indiana Utility Regulatory Commission to manage the data center's electricity load and grid impact. · source
2025-08-28permit
Google filed an application with IDEM to build on approximately 2.47 acres of protected wetlands for Phase 2 of its Fort Wayne data center expansion. · source
2025-09-19permit
IDEM approved Google's permit to build on approximately 2.5 acres of protected wetlands at the Fort Wayne data center site, requiring purchase of mitigation credits. · source
2025-11-13hearing
IDEM held a nearly three-hour public hearing at Ivy Tech on Google's request to expand from 34 to 179 backup diesel generators; the packed auditorium left more than 20 residents unable to speak, and attendees demanded the permit be denied. · source
2025-11-18protest
Residents rallied at Indiana Michigan Power headquarters and Fort Wayne City Council, calling on the council to pressure IDEM to deny Google's diesel generator permit, citing potential annual pollution of 900 tons and rising energy costs. · source
2025-12-04permit
IDEM approved AEP's request to temporarily fill wetlands to build power infrastructure serving Google's Fort Wayne data center. · source
2025-12-11operational
Google announced its Fort Wayne data center is operational and held a community forum at Grand Wayne Center; the company pledged $1.2 million to ACRES Land Trust to protect 22 acres of wetlands and committed to using backup generators only for testing or emergencies. · source
2026-01-13coverage
Fort Wayne City Council reported that Google agreed to pay approximately $200,000 for stormwater drainage improvements at 6015 Adams Center Road near the data center campus. · source
2026-02-17coverage
Google launched a public website to address community questions and concerns about its Fort Wayne data center operations. · source
2026-02-25coverage
Indiana Michigan Power announced plans to lower electric rates, citing revenue from data centers including Google's Fort Wayne facility as an offset for residential customers. · source
2026-03-17permit
Google filed permits with IDEM for Phase 3 of its Fort Wayne data center, proposing three additional buildings that would expand the campus footprint to over 867,000 square feet. · source
2026-04-10permit
IDEM approved Google's request for 140 additional emergency diesel generators (plus 5 smaller units) at the Fort Wayne data center, on top of 34 already permitted in 2024. · source
2026-04-29ruling
Indiana Utility Regulatory Commission approved the Google-Indiana Michigan Power demand-response deal, allowing Google to curtail usage during peak grid stress in exchange for rate discounts, projected to reduce costs for all I&M customers. · source
2026-06-09vote
Fort Wayne City Council member Russ Jehl introduced three resolutions demanding Google demonstrate compliance with tax-break benchmarks, accountability for land-sale proceeds directed to southeast Fort Wayne, and creation of a permanent data center oversight board. · source
2026-08-06environmental
Hatchworks LLC requested IDEM approval to fill 2.13 acres of forested wetlands for Phase 3, proposing a 2-to-1 mitigation ratio; a virtual public hearing is scheduled for August 25, 2026, with construction targeted to begin mid-September if approved. · source

Find the paper trail

Find the paper trail (5 filed · 12 places to look)

Permits already on file (5)

Filings we have a source for — the record, not a place to look for one.

2026-04-10
IDEM approved Google's request for 140 additional emergency diesel generators (plus 5 smaller units) at the Fort Wayne data center, on top of 34 already permitted in 2024. · source
2026-03-17
Google filed permits with IDEM for Phase 3 of its Fort Wayne data center, proposing three additional buildings that would expand the campus footprint to over 867,000 square feet. · source
2025-12-04
IDEM approved AEP's request to temporarily fill wetlands to build power infrastructure serving Google's Fort Wayne data center. · source
2025-09-19
IDEM approved Google's permit to build on approximately 2.5 acres of protected wetlands at the Fort Wayne data center site, requiring purchase of mitigation credits. · source
2025-08-28
Google filed an application with IDEM to build on approximately 2.47 acres of protected wetlands for Phase 2 of its Fort Wayne data center expansion. · source

State environmental permits

Backup generators, water withdrawal and stormwater are permitted by the state, usually earlier and in more detail than anything filed locally.

Indiana IDEM — Office of Air QualityThe program page: which permits this state requires, and the office that issues them.
IDEM Virtual File CabinetSearchable public filings — search the operator, the shell LLC on the deed, and the address.

County & town filings

The rezoning application, site plan, traffic and noise studies, staff report and every revision.

Search Fort Wayne planning filingssearchPlanning departments post application files under many different names. Find the department, then ask the clerk for the application number — that number unlocks everything else.
Search Fort Wayne property records / GISsearchThe parcel record names the buying LLC and the sale date, which is what ties an anonymous filing to an operator.

Utility & grid records

The electricity request is filed with the grid operator and the utility long before the town hears about it — and states the real load.

MISO (Midwest & Gulf) — interconnection queueRequested megawatts, queue position and target in-service date. The MW here is the real number; the one at the town meeting is often phase one.
PJM Interconnection (Mid-Atlantic, Ohio Valley) — interconnection queueRequested megawatts, queue position and target in-service date. The MW here is the real number; the one at the town meeting is often phase one.
Indiana Utility Regulatory Commission — docket searchSpecial contracts, large-load tariffs and rate cases are docketed here. Testimony and exhibits are public, and are usually more candid than the press release.
FERC eLibraryFederal filings: transmission agreements, interconnection service agreements, and co-location disputes.
Search the serving utility for a will-serve lettersearchThe will-serve or load-service letter is the utility's own written commitment. Ask the utility and the PUC for it by name — it is frequently the first document to exist.

Federal databases

Works anywhere, and covers the operator's record at its other sites.

EPA ECHO facility searchEvery federally-reported air, water and waste permit at a facility, plus its inspection and violation history. Search by address or draw a radius around the site. This project's locality centres on 41.030, -85.140 — search that point with a 5-mile radius.
EPA EnvirofactsThe same underlying records, queryable by county — useful for 'what else is permitted near this site' rather than one facility.
EPA Facility Registry ServiceResolves the shell LLC on a permit to the facility it belongs to. Worth a look when the filing name means nothing locally.

These are places to look, not evidence that anything has been filed. Links were checked on 2026-08-21; search links are queries, not records. What to ask for.

Around here

Indiana briefing — rates, grid carbon, PUC contacts.

Other tracked projects in Indiana

Project Riverjump (Marion) — Marion (Grant County), 44 mi Withdrawn
Recore Digital AI data center inquiry — Grant County, 45 mi Rumored
Decennial Group Akron Data Center Campus (proposed) — Fulton County (Akron), 46 mi Blocked by ban
Abei Energy data center proposal (rezoning request) — Starke County, 80 mi Blocked by ban
AWS Northern Indiana expansion (New Carlisle) — New Carlisle (St. Joseph County), 85 mi Operating

Cite this page: GridWatch AI, “Google Fort Wayne”, aigridwatch.com/projects/google-fort-wayne, retrieved 2026-10-11.

As of August 2026 (2m ago) · changes weekly — re-check before citing

A working set of identified proposals a community can track, not a census — most of the country's activity is not in here yet. Pennsylvania is the exception: its rows are synced from PA DEP's own data-center permit tracker, so the state's coverage is close to complete and carries the permit trail with it. **Each row carries its own provenance.** Rows showing a verification date link to reporting or the governing body's own record and were read on that date; rows marked *unverified* have no source on record — a lead to check, not a fact to cite. **Stage is derived, not asserted.** *Hearing scheduled*, *Awaiting decision*, *Approved* and *Withdrawn* are computed from each row's milestone dates on every rebuild, so a hearing date that has passed stops reading 'scheduled'. Hearings get moved and projects re-file under new names — treat a scheduled date as the earliest to act by, and confirm with the clerk before relying on it. Leads are mined into data/project_candidates.json and promoted here only after a human reads a primary source.

Part of the data center project tracker — open data, CC BY 4.0 (JSON · CSV).