Why water is the real bottleneck in Canada’s AI boom

AI doesn’t live in the digital cloud. It lives in concrete, copper, and massive, thirsting cooling systems. The boom is fueling a challenge for our freshwater security, but that’s only half the story. This bottleneck is sparking a wave of Canadian innovation, with sustainable practices like greenhouses warmed by server heat and snow-based cooling systems proving we can grow our tech sector while protecting our most precious resource. But this transition requires more than just new technology, it demands a commitment to developing the forward-thinking policy frameworks that will ultimately set us up for success.

The municipal governance gap

“There are good and bad ways to move forward technological transitions, especially if they have substantial impacts on people’s quality of life and the built environment,” says Dr. Anne Pasek, an Associate Professor at Trent University who studies environmental climate politics and the tech sector. “You want to move slowly, and you want substantive community participation. But that hasn’t been how we’ve done this in Canada.”

Instead, federal initiatives, like Ottawa’s top-down AI adoption strategy, presume that existing municipal zoning and environmental regulations designed for generic light industry will simply stretch to absorb hyperscalers.

The friction created by this regulatory absence was thrust into the national spotlight in Hamilton, Ont. City Council recently debated a first-in-Canada interim control moratorium on data centres after an application surfaced for a massive 400-megawatt hyperscaler on local harbour lands.

“Our current zoning codes are permissive under industrial land use, relying on a 15-year-old definition for a ‘data processing establishment,'” explains Hamilton Ward 3 Councillor Nrinder Nann. “That definition was written long before AI data centres. It was intended for archive facilities where you store back-up drives, not facilities doing continuous supercomputing.”

While Hamilton’s interim moratorium ultimately fell in a tight 10–6 vote, the council directed city staff to push forward with a comprehensive review of all municipal bylaws, sewer discharge rules, and land-use definitions.

The situation reveals a glaring jurisdictional gap across Canadian environmental governance:

• Water Intakes: Provincial ministries grant raw water-taking permissions.
• Municipal Utilities: Local councils are left with limited tools—primarily regulating municipal sewer discharge, absorbing infrastructure strain, or updating land-use bylaws.

“If an application wanted 20 per cent of a smaller city’s daily water capacity, that would be an immediate red flag,” notes Dr. Pasek, referencing how municipal water managers analyze incoming requests. “In Alberta, where water is severely stressed, hyperscalers are trying to lock up priority water access. When peak drought hits, who gets curtailed? There’s a fundamental issue of ratepayer equity when public utilities shoulder the capital cost of infrastructure upgrades for deep-pocketed tech entities.”

The technological & physical bottleneck

Water sits at the core of the data centre debate because of one hard truth: forced evaporation.

“Servers generate an enormous amount of heat, and historically, the cheapest way to remove that heat is to evaporate water and let it carry the heat into the atmosphere,” explains Soula Chronopoulos, President of AquaAction. “Most traditional cooling towers do exactly that. The crucial detail most people miss is that 80 per cent to 90 per cent of the water running through these systems is treated, potable, drinking-quality municipal water. It is paid for, treated at public expense, evaporated into the air, and lost to the local watershed for good.”

For watershed managers already dealing with climate-induced droughts in the Prairies and aging distribution lines in Eastern Canada, using drinking water for industrial server cooling represents an existential threat to community water security.

However, alternative thermal management strategies are already operating globally:

• Direct-to-Chip & Immersion Liquid Cooling: Transfers heat away at the circuit level using sealed dielectric fluids, eliminating evaporative loss.
• Free-Air & Thermal Energy Storage: Taps cold outdoor ambient air to cool systems.
• District Energy Circularity: Facilities like QScale’s Q01 campus in Lévis, Quebec, use Hydro-Québec’s clean power grid and cold climate for free-air cooling 80 per cent of the year, while capturing spent server heat to warm neighboring commercial greenhouses producing 80,000 tons of food annually.
• Snow-Based Infrastructure: The White Data Center in Bibai, Japan, stores winter snowfall under insulated mounds of wood chips to cool server pipes all summer, cutting energy costs in half.

“None of this is waiting on a technology breakthrough,” states Chronopoulos. “Every single one of these approaches is operational today. The gap isn’t invention, it’s the courage to adopt them and write them into municipal policy.”

The myth of the “clean” closed loop

Closed-loop cooling systems represent a significant leap forward in sustainable data infrastructure, offering the immense promise of reducing water consumption by upwards of 90 per cent. While these advancements are a vital part of the industry’s evolution, it is prudent for municipalities to recognize that they are not a universal silver bullet. To ensure long-term watershed security, policymakers must balance this water efficiency against three critical technical trade-offs that accompany closed-loop operations.

1. Concentrated chemical blowdown

Recirculated water degrades over time as minerals and thermal stress accumulate. To prevent bio-fouling, corrosion, and Legionella growth, operators dose closed systems with non-oxidizing biocides, anti-scalants, and synthetic corrosion inhibitors.

Eventually, this fluid must be flushed—a process called blowdown. It’s essentially a chemical concentrate. When dumped into municipal sewers, it can disrupt the delicate biological treatment processes at Wastewater Treatment Plants (WWTPs), especially in smaller communities that lack specialized industrial pretreatment.

2. Thermal pollution & off-gassing

Closed systems dissipate internal heat either by discharging high-temperature liquid effluent into local sewers, altering aquatic ecosystems downstream, or through dry cooling stacks.

As Councillor Nann points out from Hamilton’s industrial legacy, off-gassing micro-particles during heat dissipation raises localized public health questions. “If chemicals are used to keep closed-loop water cool and you have to off-gas, that particulate matter goes into the air,” warns Nann. “On a windy day, where do those particulates settle? Right back into our drinking water supply or natural water bodies.”

3. Energy-for-water swaps

While closed-loop systems dramatically conserve water, they require secondary mechanical chillers and fans to cool the recirculating loop, significantly increasing the facility’s overall electricity footprint.

Policy roadmap: A water-first framework for Canada

Canada cannot reconcile its AI ambitions with water security if federal and provincial governments treat them as separate portfolios.

Experts and municipal leaders recommend four urgent policy shifts:

• Condition public funds on watershed circularity: Any tech enterprise accessing federal AI compute subsidies or slush funds must be legally mandated to meet strict environmental standards, submit verified water balance reports, and present a circularity plan before breaking ground.
• Mandatory sub-metering & standardized metrics: Municipalities must require mandatory, real-time water metering for all data infrastructure. Tech companies should be legally required to publicly report their Water Usage Effectiveness (WUE), water sources (potable vs. reclaimed), and discharge composition.
• Streamline reclaimed (greywater) permitting: Provinces must establish clear, standardized permitting pathways that allow data centres to draw treated municipal wastewater effluent instead of default potable drinking water.
• Modernize municipal land-use definitions: Cities across Canada must update 15-year-old zoning definitions to explicitly separate “dry warehouses” from “high-density computing facilities,” giving local councils clear authority to evaluate water taking, noise, and thermal discharge.

A path to regulatory courage

“Humanity is at its most ingenious when our backs are against the wall,” says Chronopoulos. “We have the technology, cold climate advantages, and engineering capability in Canada. What we need now is the regulatory courage to protect our water before the pipe runs dry.”

This “regulatory courage” is the essential ingredient for Canada’s path forward, requiring municipal leaders to move beyond outdated industrial frameworks and take ownership of their local water security. For councils, the roadmap is clear: modernize land-use zoning to distinguish between simple warehouses and high-density compute facilities, end the use of NDAs that obscure environmental impact, and shift infrastructure costs from ratepayers to developers. By enforcing strict pretreatment standards and demanding transparency in water usage, municipalities can ensure that the AI boom does not come at the expense of our most critical resource. The technology for sustainable, water-conscious data centres exists today, it is now up to local and provincial policymakers to ensure that the pipe does not run dry.

MUNICIPAL PRACTICE GUIDE

THE UTILITY MANAGER’S CHEAT SHEET: 3 QUESTIONS TO ASK EVERY DATA CENTRE DEVELOPER

Developers will walk into your office with a pre-packaged “Sustainability Pitch.” Don’t buy the gloss. Ask these three questions to clarify their impact before a single permit is signed:

1. “Can you provide a mass balance of water inflow vs. outflow, and specifically, what is the expected TDS (Total Dissolved Solids) concentration in your blowdown effluent?”

• Why it matters: Developers often focus on how much water they don’t evaporate. But you need to know what they are putting into your sewers. High-TDS water can be toxic to the bacteria in your wastewater treatment plant. If they cannot answer this, they have not modeled their impact on your facility’s biological health.

2. “Beyond ‘closed-loop’ cooling, what is your secondary backup mechanism for thermal rejection during peak summer drought conditions or power grid stress?”

• Why it matters: “Closed-loop” systems often fail to mention their fallback protocols. If the power spikes or the mechanical chillers go down, do they revert to potable water-intensive evaporative cooling? You need to know if your infrastructure is being used as their emergency insurance policy.

3. “Will you agree to full, real-time sub-metering of makeup water versus blowdown discharge, and commit to making this data available via a public-facing dashboard?”

• Why it matters: Transparency is your best defense against ratepayer backlash. If they are confident in their “water-neutral” or “water-positive” claims, they should have no objection to public, real-time monitoring. If they resist this, assume their water footprint is larger than they are admitting.

Developing a data centre water bylaw: Actionable tools for local councils

As high-density AI data centres expand into mid-sized and peri-urban Canadian municipalities, local planning departments and water managers face severe information asymmetries.

To prevent stranded municipal infrastructure assets and protect local watersheds, councils can adopt this four-step municipal regulatory framework.

Step 1: Establish standardized zoning & definition overhauls

• Action: Repeal legacy zoning terms (e.g., “Data Processing Establishment” or “Light Industrial Warehouse”).
• Implementation: Amend Land-Use Bylaws to create a specific tier for High-Density Compute & Hyperscale Facilities (defined as facilities drawing >10 MW of power or requiring >50,000 L/day of thermal management cooling intake).

Step 2: Enforce NDA bans & transparent application timelines

• Action: Refuse municipal Non-Disclosure Agreements (NDAs) that conceal water intake, chemical use, or energy requirements from the public.
• Implementation: Require developers to submit a static, public Environmental Impact Profile at least 180 days prior to committee review, creating clear timelines for public engagement, environmental scrutiny, and Indigenous consultation.

Step 3: Implement ring-fenced development tariffs & bonding

• Action: Shift the financial burden of infrastructure upgrades from local ratepayers to the developer.
• Implementation: Enact specialized capital cost recovery tariffs to pay upfront for utility expansions. Require long-term decommission bonding so that if market bubbles burst, municipalities are not left holding stranded concrete assets or unserviced utility debt.

Step 4: Institute pre-treatment & sewer discharge protocols

• Action: Protect municipal Wastewater Treatment Plants (WWTPs) from chemical blowdown and thermal pollution.
• Implementation: Mandate on-site industrial pretreatment units for any closed-loop cooling system discharging chemical biocides, glycol, or high-TDS (Total Dissolved Solids) blowdown. Enforce maximum temperature caps on liquid sewer discharge to prevent biological disruption at municipal facilities.

Featured image: (Getty Images)