Power and water are where most large-scale artificial intelligence infrastructure projects run into trouble. Grid capacity constraints have delayed campuses, drawn regulatory scrutiny, and produced community opposition that no amount of economic development messaging has reliably defused. Water consumption at evaporative-cooled data centers has created friction with municipal suppliers and agricultural users in regions where every megalitre is contested. Every hyperscaler building at gigawatt scale is watching how these constraints play out and trying to determine what a sustainable design answer looks like. Oracle has one, and the evidence for how it performs is accumulating across the Stargate buildout.

In January 2026, Oracle Senior Vice President Josh Pitcock published a framework covering four commitments to communities hosting Oracle data centers: self-funded energy, water conservation, local jobs and investment, and site design standards. On March 4, Oracle joined six other technology companies at the White House to sign the Ratepayer Protection Pledge, giving the energy commitment a formal federal name. The pledge requires signatories to build, bring, or buy their own power generation, fund grid upgrades, and negotiate separate rate structures with utilities so that data center costs do not pass to residential electricity bills. Then Project Jupiter in Doña Ana County, New Mexico, showed what the energy pillar looks like when it is fully resolved. Oracle and BorderPlex Digital Assets replaced the original gas turbine and diesel generator design with a fuel cell microgrid contracted for up to 2.45 gigawatts of Bloom Energy solid oxide fuel cell capacity, allocated from a master services agreement covering up to 2.8 gigawatts across Oracle's portfolio. Compared to the prior design, the fuel cell configuration reduces nitrogen oxide emissions by approximately 92% and eliminates water use from power generation entirely.

The Ratepayer Protection Pledge addresses one objection communities raise: that data center load will drive up residential electricity bills. Oracle's commitment to fund its own transmission lines, battery storage, and dedicated substations satisfies that objection regardless of fuel source. What communities in areas with air quality concerns or clean energy positioning raise next is a different question, one about what the generation burns.

The Doña Ana County community, combined with BorderPlex's clean energy identity for the region, made that question explicit early. Oracle and BorderPlex resolved it by redesigning the power architecture before construction locked it in. The outcome is a campus that addresses both objections: ratepayers are protected by the self-funding commitment, and the surrounding community gets generation without combustion. Both of those outcomes were available within the January framework. Project Jupiter produced both of them.

Oracle's expanded partnership with Bloom Energy, reaching up to 2.8 gigawatts of contracted fuel cell capacity across the portfolio, signals that the fuel cell approach is now a strategic direction, not a site-specific accommodation. The demand signal came from Doña Ana County. The strategic response scaled up from there.

Water consumption is the second major friction point in data center siting, and Oracle's cooling architecture addresses it at the system level. The direct-to-chip, closed-loop, non-evaporative liquid cooling system is filled once and then operates as a sealed, recirculating system. There is no evaporation in normal operation, which means daily cooling does not require additional draws from local water supplies. What remains is office building consumption: kitchens, restrooms, breakrooms.

The significance is in the sequence. Communities raise water consumption concerns after hearing about large-scale cooling requirements. A sealed recirculating system has a concrete, mechanically specific answer: the water system is filled at commissioning and does not need replenishment during operation. That answer is available before the conversation about resource impact begins. Oracle's February 2026 technical post on closed-loop cooling documents the system design, and Project Jupiter confirmed it holds at campus scale.

Most evaporative cooling systems at large data centers draw millions of gallons annually. This design draws none for cooling.

State legislatures are not waiting for voluntary pledges to settle the power and water questions. In 2025, more than 200 data center bills were introduced across all 50 states, with over 40 enacted (WilmerHale; 2026). In just the first six weeks of 2026, more than 300 bills were filed across 30 states, a pace that signals the legislative activity is accelerating, not plateauing (MultiState; 2026).

The enacted laws cover both resource constraints Oracle's framework addresses. On energy, Oregon's House Bill 3546, known as the Protecting Oregonians with Power Energy Responsibility Act, signed in August 2025, requires a separate rate class for large energy users above 20 megawatts and mandates 10-year power purchase agreements. Texas Senate Bill 6 regulates loads above 75 megawatts, requires developers to fund interconnection studies and infrastructure upgrades, and establishes disconnection protocols during grid stress events. Alabama Senate Bill 270 requires contracts above 150 megawatts to pass a ratepayer benefit test before execution. Florida's Senate Bill 484, effective July 1, 2026, prohibits utilities from passing data center infrastructure costs to residential and small-business ratepayers and preserves local government authority over zoning and permitting. California, Ohio, and Utah have enacted laws that go further than the federal Ratepayer Protection Pledge on cost allocation and reporting (MultiState; 2026).

On water, Minnesota enacted House File 16 in 2025 requiring non-potable water use where feasible. Utah's House Bill 76, enacted in 2026, requires water use disclosure and reporting. Idaho, South Dakota, and West Virginia have enacted similar measures. At least 16 states have active water-related data center bills in their 2026 sessions (Climate XChange; 2026).

The cost of not resolving water at the design level arrived at congressional hearing scale in May 2026. Meta's Stanton Springs data center in Newton County, Georgia, accounts for approximately 10% of the county's daily water consumption. Residents in neighboring Morgan County reported discolored tap water and appliance damage following construction. Representative Alexandria Ocasio-Cortez brought two jars of brown water from Morgan County to a House Energy and Commerce subcommittee hearing on May 20 and asked the Environmental Protection Agency's assistant administrator for water to review the situation. The EPA agreed to contact Georgia environmental regulators. Meta disputes the causal link and points to an independent groundwater study it commissioned, which found no impact from data center operations. What is not in dispute is the sequence: construction preceded the complaints, the complaints reached Congress, and the industry is now navigating federal scrutiny over a resource question that a sealed recirculating cooling system makes structurally irrelevant. At least 48 data center projects representing $156 billion in investment were blocked or stalled by local opposition in 2025 (Fortune; 2026). The water question is generating more of that opposition, not less.

The sector-wide message in that sequence is direct. Water consumption resolved at the design level, before community opposition forms and before construction begins, does not produce congressional hearings. A sealed recirculating cooling system is not a sustainability gesture. It is operational insurance.

Maine passed LD 307, a construction moratorium for data centers above 20 megawatts, through both legislative chambers in April 2026, but Governor Janet Mills vetoed it, citing a conflict with a specific redevelopment project. Mills did sign LD 713, which bars data centers from Maine's business equipment tax exemption and Dirigo business incentive programs. New York, Oklahoma, and South Dakota have introduced pause legislation that remains active.

The Ratepayer Protection Pledge Oracle signed in March is non-binding and has not slowed this legislative activity. States are treating it as a floor, not a ceiling, and some are building mandatory requirements around the same issues the pledge addresses voluntarily. Oracle's design framework, fuel cell generation, sealed recirculating cooling, community engagement before construction, and site design standards, maps closely to what these laws require or will require. That alignment matters as the Stargate buildout expands into states with active regulatory environments.

The Stargate program now encompasses 4.5 gigawatts of capacity under development across campuses in Texas, New Mexico, Wisconsin, and Michigan. Oracle's actual capital expenditure for fiscal year 2026, which ended May 31, came in at $55.7 billion, exceeding its own $50 billion guidance. The January framework applies across all of those sites. The four-pillar structure, energy, water, jobs, and site design, is consistent. What varies is the local context that determines how each pillar is fulfilled.

Doña Ana County has air quality priorities and a developer in BorderPlex whose regional brand depends on clean energy positioning. That combination produced a full fuel cell design. Abilene, Texas has a different regulatory environment, different community priorities, and a different development timeline. The framework is the same. The outcome of applying it will differ by site.

That is not a weakness in the framework. It is how site-specific infrastructure development works. The more relevant question is whether Oracle's engagement process is robust enough to surface local constraints before they become design conflicts, as it did in New Mexico, and do so consistently across a portfolio of this scale.

Of the four pillars, local hiring is the one with the least verifiable near-term signal. Oracle's commitment covers a range that runs from high school graduates to military veterans to experienced technology professionals, with Oracle Academy providing the workforce development infrastructure: internships, scholarships, and career training in partnership with local educational institutions. The framework is there. What is not public is local sourcing rate data for construction workforces already on-site.

The January post said campuses using around one gigawatt of energy would require more than 1,000 permanent employees, with tens of thousands during construction. Those are large numbers tied to operational phases that have not arrived at most campuses. Oracle Academy has published workforce development commitments for specific sites, but aggregate local-hire percentages have not been released.

Oracle's community framework includes a building design pillar that addresses noise and visual impact directly. Sites are required to use extensive landscape screening and setbacks, often with large areas of untouched natural land surrounding the buildings. The noise specification is precise: technology at these sites is designed to operate at levels equivalent to everyday farming operations. Road planning and traffic infrastructure upgrades are also committed before construction begins.

This is worth noting because it addresses one of the most common community concerns about data center development that does not appear in energy or water coverage. A 250-acre campus in a rural county is a visual and acoustic fact. Landscape screening and setback requirements add cost and limit density. Oracle naming it as a commitment, with a decibel-equivalent specification tied to farming operations, suggests the intent is to institutionalize it as a design standard across sites.

Enterprise buyers choosing Oracle Cloud Infrastructure for artificial intelligence workloads benefit from the infrastructure stability that the community framework is designed to create. A campus that has resolved power sourcing, water consumption, local workforce integration, and site design before community opposition forms is a campus less likely to face delays, regulatory intervention, or the kind of operational uncertainty that surfaces when a large infrastructure project becomes a local controversy.

Oracle's framework creates the conditions for the buildout to proceed on schedule. Power and water are the two constraints that have derailed competing programs. Oracle has design answers to both, demonstrated at operating scale. The CIO question is whether the campuses serving specific workloads have applied those answers, and at what stage of development the engagement process that produces them was initiated.

Prior Oracle coverage on this site examined the database availability tiers announced at Oracle AI World Tour in April. The infrastructure buildout is what makes those database capabilities accessible at enterprise scale, and the community framework is what makes the buildout sustainable.