This is partner content, brought to you by Arbor Energy. Brad Hartwig is the company’s CEO and co-founder.
Until recently, the biggest challenge facing AI data center developers was finding enough power. That hasn’t gone away, but communities now want to understand what these projects mean for them before they offer support.
Across the country, proposed data centers face growing scrutiny over electricity demand, water use, and local impacts. Some facilities have been delayed or abandoned as utilities face pressure to explain who pays for new transmission, substations, and grid upgrades. Local officials are asking tougher questions before developments move forward. Building enough power is only part of the challenge now. Projects also have to earn the support of the communities that host them.
The industry often treats those concerns as a communications challenge. It’s time we view community needs as foundational design requirements.
In engineering, a requirement is where the design begins; the work is to satisfy it. The same discipline applies here. Better messaging can’t fix air quality, water usage, noise, traffic, or visual impact. Those concerns are inputs that should shape engineering decisions from the outset, alongside grid constraints and permitting timelines. A project that can’t satisfy them has a design gap.
Microsoft’s recent announcement of a 2-gigawatt AI campus in Pecos, Texas shows how quickly that shift is happening. Alongside the new data centers and power generation, Microsoft emphasized water stewardship, investments in schools and parks, paying for the energy needed to serve the campus, and its long-term commitment to the surrounding community. Those details were deliberate. Residents want to know what a project means for them long after the ribbon-cutting.
We’re seeing the same shift in conversations with hyperscalers, data center developers, and utilities. Discussions once centered almost entirely on generation capacity, transmission constraints, and interconnection timelines. Those issues are still central, but another set of questions now joins them: how early engagement should begin, what the community gains from hosting a data center, and which local concerns belong in the design criteria?
For years, developers treated those questions as something to address after the engineering was complete and a site was chosen. That approach is becoming harder to defend. By the time a polished presentation arrives, many of the decisions that matter have already been made. If community concerns are going to shape a project, they need to be part of the design process from the beginning. The incentive is both practical and principled: even technically sound projects face costly delays when local considerations surface late.
AI infrastructure is being built at a scale most communities have never experienced. A single hyperscaler campus can require hundreds of megawatts of electricity, new transmission infrastructure, and years of construction. Residents want to know what that means for electricity rates, water resources, roads, and the local economy.
Louisiana illustrates why this matters. The state has become an attractive destination for new energy infrastructure because of its skilled workforce, existing energy assets, and carbon management leadership. It also has communities that have spent generations living alongside major industrial facilities. Recent debates around carbon capture and storage show that technical merit and political support don’t guarantee community support. What matters to residents is how risks will be managed and whether the benefits promised on day one will still be there years later.
These are questions of trust, and trust isn’t built in a single public meeting after permits have been filed. Trust requires relationships that begin before construction and continue throughout the life of a facility. Those relationships are also how you learn the community’s requirements in the first place. You can’t design for concerns you haven’t heard.
That same philosophy is shaping our work in Louisiana, where Arbor Energy is building a facility that will use our modular turbines to deliver reliable baseload power. In aerospace engineering — our team’s background — you push back on a requirement before you accept it. Once you accept it, you’re expected to meet it. If you can’t, the design isn’t done.
Air quality is one of the first questions communities ask, so we treat it as a design requirement rather than something to explain later. Our systems are built to operate without emitting criteria pollutants such as nitrogen oxides, allowing us to address one of the most common concerns through engineering instead of mitigation. The same standard applies to water. Arbor Energy’s semi-closed-loop system produces clean water as a byproduct of oxy-combustion, rather than drawing on local supply to run.
Not every concern can be solved in hardware. For those, we’ve written specific, measurable commitments on workforce development, environmental and public health protections, infrastructure investment, and economic outcomes. We’ve defined those priorities at the outset so people know what success looks like and how we’ll hold ourselves to it over time. We’re already working with parish officials and community leaders because those relationships should shape a project, not follow it.
Power will remain the biggest technical challenge facing AI infrastructure. Whether that power gets built will depend on the communities asked to host it. The projects that succeed will be the ones that treat community concerns as requirements from the start.
Arbor is building zero-emission power systems designed to meet the requirements communities are setting. See how at arbor.co.
