Is a $2 Billion Data Center Campus Right for Indy?
Discover how a $2 billion data center could reshape Indianapolis—community voices, economic impact, and more!
A tech developer wants to plant a $2 billion data center campus on Indianapolis's east side. For city officials eyeing tax revenue and tech-sector credibility, that sounds like a win. For residents living near the proposed site, it's a harder sell — and they're showing up to say so.
Community meetings are rarely packed unless something feels personal. When neighbors start filling folding chairs to ask questions about zoning, noise, and power consumption, that's a signal worth paying attention to.
What's Being Proposed
The project centers on a large-scale data center campus on the east side of Indianapolis — the kind of infrastructure investment that doesn't just occupy a parcel of land but fundamentally reshapes a neighborhood's character. At $2 billion, this isn't a single building with a few server racks. Campuses at this price point typically involve multiple facilities, significant electrical substation infrastructure, cooling systems running around the clock, and a physical footprint that can span dozens of acres.
A $2 billion data center investment is the kind of anchor project that cities compete hard to attract — but winning the bid doesn't automatically mean winning the community.
For context: hyperscale and large-scale data center campuses in the $1–3 billion range have become increasingly common in markets like Northern Virginia, Phoenix, and Columbus, Ohio. Indianapolis hasn't traditionally been in that tier. If this project moves forward, it signals something meaningful about how investors view the city's power infrastructure, connectivity, and land costs relative to saturated coastal and Sun Belt markets.
What Residents Are Actually Saying
The community meeting wasn't a rubber-stamp session. Residents came with concerns — and that matters because data center development often moves through approval processes with less public scrutiny than, say, a highway expansion or a new stadium.
The east side of Indianapolis has its own history, demographics, and economic pressures. Longtime residents in similar situations in other cities have raised consistent objections: industrial-scale facilities that bring relatively few permanent jobs while driving up land values, increasing truck traffic, straining local utility infrastructure, and generating noise from industrial cooling equipment that runs 24/7.
None of those concerns are irrational. They're grounded in what actually happens when hyperscale infrastructure lands in a residential-adjacent area without adequate community input or binding commitments from developers.
The question residents deserve answered isn't just "how many jobs" — it's "what kind of jobs, for whom, and at what cost to the people already here?"
At the same time, not everyone in the room is opposed. Economic development on the east side — a part of the city that has seen disinvestment over the decades — is something many residents genuinely want. The tension isn't simply between growth and no growth. It's about who controls the terms of that growth.
The Economic Math — and Its Limits
Supporters of the project will point to job creation, and they're not wrong that data centers generate employment. But the numbers require some unpacking.
Construction phases create significant short-term employment — electricians, ironworkers, concrete crews. For a campus of this scale, that could mean hundreds of construction jobs over a multi-year build. That's real economic activity.
The permanent employment picture looks different. A $2 billion data center campus typically operates with somewhere between 50 and 200 full-time employees once it's running — a surprisingly lean number for a facility of that size. These positions tend to be well-compensated (network engineers, facilities technicians, security personnel), but the aggregate job count rarely matches the scale of the investment.
Where the math gets more interesting is in secondary effects: property tax revenue, increased demand for local contractors and suppliers, and the potential to attract ancillary tech businesses that want proximity to major infrastructure. Indianapolis has been building its tech ecosystem steadily, and a campus of this scale could accelerate that trajectory — if the project is structured to actually benefit local businesses rather than importing everything from outside.
Local officials should be negotiating community benefit agreements with teeth: commitments on local hiring, vendor preference, infrastructure contributions, and long-term tax arrangements that don't simply defer revenue for decades.
Infrastructure: The Unglamorous Deciding Factor
Here's what often gets overlooked in the public debate around data center development: the infrastructure requirements are massive, and they don't land in a vacuum.
A $2 billion data center campus will consume electricity at a scale that challenges local grid capacity. Facilities of this type routinely draw 100–500 megawatts of power — enough to supply tens of thousands of homes. That doesn't mean the grid can't handle it, but it does mean significant substation upgrades, transmission line investments, and coordination with utility providers that can take years to execute.
Power availability, not land cost, is increasingly the binding constraint on where major data centers get built — and Indianapolis's answer to that question will determine whether this project actually happens.
Water is the other variable. Cooling systems for large-scale data centers are thirsty. Depending on the cooling technology selected, a campus of this size could consume millions of gallons of water annually. In a city without the drought pressures of Phoenix or Las Vegas, this is a solvable problem — but it's not a trivial one, and it should be part of the public conversation.
The east side's existing infrastructure will also need evaluation. Road networks, utility corridors, fiber connectivity — each of these requires assessment before a campus of this scale can operate. Some of those upgrades will be funded by the developer; others may shift costs to the city or utility ratepayers. Residents deserve clarity on who pays for what.
What Other Cities Have Learned
Indianapolis isn't the first mid-sized American city to face this question, and the experiences elsewhere offer useful signals.
Columbus, Ohio, went deep on data center recruitment and became one of the fastest-growing data center markets in the country. The tax abatements offered to attract those investments drew criticism for their generosity, and some communities felt the job creation promises were overstated. Columbus is now revisiting its incentive framework.
Northern Virginia's data center boom in Loudoun County created a sprawling industrial corridor that generated enormous tax revenue — and fundamentally altered the character of communities that were once semi-rural. Residents there have spent years fighting for tighter development controls, with limited success once the market momentum was established.
The lesson isn't that data centers are bad neighbors. It's that the terms set at the beginning of a development relationship are very hard to renegotiate later. Front-loading community protections — before approvals are granted, not after — is how cities avoid becoming cautionary tales.
What Comes Next
The Indianapolis data center campus proposal is still in the early stages, and community meetings represent exactly the right moment for residents and officials to shape its outcome. That window doesn't stay open indefinitely.
For the developer, demonstrating genuine responsiveness to community concerns isn't just good optics — it's practical risk management. Projects that generate sustained neighborhood opposition face delays, permit challenges, and political complications that erode the investment case.
For Indianapolis, the strategic question is larger than this single project. The city has an opportunity to establish a framework for technology infrastructure development that attracts investment without ceding community influence. That means binding agreements, transparent infrastructure cost accounting, and real commitments on local economic participation — not just press releases about job numbers.
The $2 billion figure gets the headlines. What happens in the community meetings determines what kind of deal Indianapolis actually gets.
**Explore more about InfraSale Marketplace and how it can benefit your community.**