Indiana data center projects

What these public records establish

A preliminary committee action is a starting point for finding the final decision and its conditions. Match the local applicant and phase before combining project aliases.

22 published public records on this page; 20 include the current field-level source report. Other previews retain their narrower published scope. These counts are records in Radar, not unique campuses, statewide totals or active bids.

• Amazon Data Services — Portage, IN data center (AWS "ORD" Portage): reported facts, supporting source and date limits
• Amazon Web Services — New Carlisle North Campus (SBN100), Project Rainier: reported facts, supporting source and date limits
• Amazon Web Services — New Carlisle South Campus (SBN201 / SBN210 expansion): reported facts, supporting source and date limits
• DC BLOX Thunderbird Commerce Center data center, Indianapolis: reported facts, supporting source and date limits
• Google Fort Wayne data center campus (Project Zodiac): reported facts, supporting source and date limits
• Google Morgan County / Monrovia campus (Project Louie): reported facts, supporting source and date limits
• Google Project Maize, Michigan City: reported facts, supporting source and date limits
• Heartland Industrial Park, Sullivan County (Potentia / Fluidstack): reported facts, supporting source and date limits
• Hobart Data Center Campus — Amazon Web Services (Hobart Devco LLC / Hobart Owner LLC): reported facts, supporting source and date limits
• Karis Critical Merrillville data center campus (101st Avenue): reported facts, supporting source and date limits
• Meta Jeffersonville Data Center campus, River Ridge Commerce Center: reported facts, supporting source and date limits
• Meta Lebanon Data Center campus (LEAP District, Lebanon, IN): reported facts, supporting source and date limits
• Metrobloks Indianapolis IND-A1: reported facts, supporting source and date limits
• Microsoft Granger Data Center (St. Joe Farm site): reported facts, supporting source and date limits
• Microsoft La Porte data center campus: reported facts, supporting source and date limits
• Prologis Shelbyville data center campus (State Road 44 / I-74 interchange): reported facts, supporting source and date limits
• RadiusDC Indianapolis (Indy I & II) / AllPoints 18 and 19, Plainfield: reported facts, supporting source and date limits
• Sabey Data Centers — Decatur Technology Park campus, Indianapolis: reported facts, supporting source and date limits
• Vantage Data Centers — Pittsboro Campus: reported facts, supporting source and date limits
• Western Hospitality Partners — South Bend Campus: reported facts, supporting source and date limits

Use the recorded-stage filters to choose a lead, then match a dated decision to its exact site, phase, authority and conditions. Check later amendments, withdrawals and restrictions. Missing public fields remain unknown; membership does not turn an uncertain claim into a verified fact.

Record the decision and unresolved questions · Check company roles and official research routes · Identify the purchasing route

Researching Indiana data center construction opportunities

Use the public previews to identify a lead, then establish its site, phase and next decision before committing pursuit time. These records describe Radar's coverage; a recorded stage does not establish an available contract, a contractor award or a complete statewide facility map.

Keep local land-use decisions separate from state environmental records

Indiana's Business Owner's Guide identifies zoning as generally local. Establish the city or county responsible for the site's land-use decision before treating a state environmental record as permission for the proposed development.

IDEM's e-Services directory links authorization-status searches and its Virtual File Cabinet. Use the status search to identify an environmental record, then retrieve the applicable application, decision and later documents. Match the facility, permit identifier and work scope; an application, a final permit and a subsequent amendment answer different questions. The repository is a source collection, not confirmation that every permission for the project is complete.

Turn a source match into a qualified next step

Record the authority, reference, decision date, phase, conditions and date checked. For a hearing, read its outcome and adopted text. For a withdrawal, identify the request or phase withdrawn. Keep local power, water, access or noise concerns tied to dated evidence before describing their effect on a project.

Use the permit-check workflow, then the procurement-route checklist to confirm purchasing responsibility and a current route for your package. Browse Indiana public previews without treating separate phase records as unique campuses.

Official resource descriptions checked October 13, 2026. This guidance does not verify individual project permits or refresh project source-check dates.