Water availability has become a siting question

Evaporative cooling remains widely deployed because it is effective and inexpensive to build. It is also consumptive: water leaves the site as vapour and does not return. In regions where supply is constrained, where aquifers are under pressure, or where residential and agricultural users are already competing, that consumption has moved from an operating detail to a permitting obstacle.

Several jurisdictions have begun requiring closed-loop or non-potable cooling for new facilities. Others have enacted moratoria while they determine how to evaluate water demand. The direction of regulation is consistent even where the specific mechanisms differ.

Shifting the burden to the grid trades one scarcity for another

Air-based and dry-cooling approaches can reduce or eliminate direct evaporative water use. Depending on climate, facility design, and peak operating conditions, they may require additional electrical capacity or supplemental cooling infrastructure. In constrained markets, those tradeoffs can affect project cost, interconnection strategy, and development timing.

Neither answer is wrong. But both require accepting a cost that is becoming harder to absorb, and the industry has largely treated the choice between them as unavoidable.

Community acceptance is now part of the engineering problem

Public opposition to data-center development has grown substantially, and water use is consistently among the concerns raised. Projects have been delayed, conditioned, or rejected on grounds that would not have been decisive a few years ago.

A facility that can demonstrate reduced reliance on drinking-water resources, minimized routine discharge to local waterways, and a credible community benefit occupies a materially different position in that conversation.

Engineering discipline

The company's work proceeds on the basis that technical propositions should be tested before they are presented as conclusions. Positions are documented, assumptions are declared, and analysis is submitted for independent professional review. Where a question remains open, the company says so.

Site-specific evidence

DepthCore does not offer a standard product specification. Climate, geography, land, permitting, and the presence of a thermal customer differ at every location, and the configuration that works at one site may not be appropriate at another. Evidence is developed per site.

Water resilience

The central design objective is to reduce the dependence of digital infrastructure on drinking-water resources. Water availability is increasingly the constraint that determines where facilities can be built, and the company's work is organised around addressing it directly rather than deferring it.

Community benefit

Where a viable thermal customer exists nearby, recovered heat can be delivered to institutions that serve the surrounding community. The company regards this as a design objective rather than an incidental benefit, and believes infrastructure of this scale should return something to the places that host it.