Alberta Data Centre WatchIndependent public-interest tracking
← Alberta data centre project list

Verified project profile

Beacon Chestermere AI Data Center Hub

Chestermere Council passed Bylaw 014-25 on April 1, 2025, redesignating approximately 310 acres and making a Data Centre Campus a permitted use on the site. That decision establishes land-use eligibility only. No development permit, servicing or development agreement, building permit, AUC approval, or construction start was verified.

Beacon Data Centers
How to read this profilePublic recordProponent statementProponent projectionADCW context

Project facts

Core scale, approval, employment, and schedule information, labelled by the type of evidence available.

Public record

Site

Approximately 310 acres

The affected lands are Pt. N ½ 35-23-28-W4 in southern Chestermere.

Sources [5], [4]
Public record

Land-use decision

Bylaw 014-25 passed April 1, 2025

Council gave second and third reading after the public hearing.

Sources [5], [7]
Public record

Permitted use

Data Centre Campus

The bylaw added the defined use to the Business Park / Light Industrial district for the affected site. A separate development permit is still required.

Sources [5]
Proponent statement

Full-build scale

Approximately 400 MW

Beacon's phased proposal, not an approved or operating load.

Sources [2], [8]
Proponent projection

Investment

More than CA$4 billion claimed

Beacon and the City repeated this estimate. It is not a verified expenditure.

Sources [2], [1]
Proponent projection

Employment

1,200 construction; 300+ operating jobs claimed

Proponent projections, not observed job counts.

Sources [2], [1]
Public record

Provincial registry status

Proposed

Alberta Major Projects lists completion by 2027, but ADCW does not treat that planning date as an approved construction or operating schedule.

Sources [8]

Energy and emissions

Beacon's municipal presentation, its stated AESO application, and the AESO queue entry are evidence of a proposed power path, not a completed or approved connection.

Important distinction: P3107 matches the campus name, Calgary planning area, timing, and 400 MW scale, but AESO does not disclose the applicant. ADCW treats it as a likely match, not independent proof that Beacon holds the request or that the connection is approved.
Proponent statement

Campus demand

Approximately 400 MW at full build

Beacon described a phased campus. No phase schedule, contracted IT load, or operating demand was verified.

Sources [2], [8]
Proponent statement

AESO application claim

Submitted, according to Beacon

Beacon's February 2025 presentation said an interconnection application had been submitted. Submission is not approval.

Sources [2]
Public record

Likely AESO match

P3107: 400 MW DTS request

AESO lists Chestermere Enterprise A.I. Load in the Calgary planning area, initially as two 200 MW stages. The entry aligns closely with the municipal proposal, but AESO does not name Beacon as applicant.

Sources [9], [2]
Proponent statement

Proposed delivery

Transmission extension and dedicated substation

Beacon described this grid-supply concept in the municipal record. A final route, point of interconnection, approved facilities, cost allocation, and energization date are not public.

Sources [6], [2]
Proponent statement

Backup generation

Proposed; design not disclosed

Beacon said backup generation would support the campus. Fuel, equipment count, capacity, emissions, testing hours, and permit path were not identified.

Sources [6]
ADCW context

Final power path

Not confirmed

No completed grid connection, binding supply agreement, AUC facility approval, or confirmed on-site primary generation plan was found for this campus.

Sources [9], [7], [8]
ADCW context

Emissions

Project-specific estimate not published

Bylaw 014-25 requires appropriate emissions controls, but no annual greenhouse-gas estimate or backup-generator air-emissions assessment was identified.

Sources [5], [6]

Water

The municipal bylaw creates a future servicing process but does not approve a water source or allocation. Cooling, water demand, wastewater, and stormwater details remain permit-stage unknowns. [5], [6]

ADCW context

Cooling technology

Not publicly confirmed

No project-specific cooling selection or heat-rejection design was identified.

Sources [6], [8]
ADCW context

Water demand and source

Not publicly confirmed

No daily or annual demand, water source, allocation, withdrawal authorization, or connection capacity was found.

Sources [5], [6]
ADCW context

Wastewater

Not publicly confirmed

No sanitary volume, discharge route, treatment arrangement, or capacity allocation was identified.

Sources [5], [6]
Public record

Stormwater

Professional plan may support higher site coverage

The bylaw caps lot coverage at 60 per cent unless a professional stormwater-management plan supports another figure. This is a planning rule, not an approved project stormwater design.

Sources [5]
Public record

Municipal servicing

Comprehensive development agreement required

The Development Authority must require an agreement with the City covering municipal services and other necessary matters as a development-permit condition.

Sources [5]

Noise

The bylaw requires environmental controls and gives the Development Authority power to require a study, mitigation, and monitoring. These are safeguards for later review, not measured project performance.

Public record

Environmental controls

Heat, noise, and emissions controls required

The bylaw sets the requirement but does not specify project limits, equipment, or demonstrated performance.

Sources [5]
Public record

Noise study

May be required by Development Authority

A qualified professional's attenuation study can be required at permit stage. No completed project-specific assessment was identified.

Sources [5], [6]
Public record

Mitigation and monitoring

May be required

The bylaw allows a mitigation plan and noise-monitoring system if the Development Authority considers them necessary.

Sources [5]

Indigenous context

Data centre projects sit within treaty territories and places with longstanding First Nations and Métis connections. This section brings together the public record on treaty geography, Indigenous ownership, consultation, and community concerns. Treaty boundaries alone cannot tell us which communities may be affected or how they view a project.

ADCW context

Treaty geography

Treaty 7 territory

Geographic context only. It does not establish consultation, consent, or any community's position on the proposal.

Sources [10]
ADCW context

Project-specific consultation

Not established in reviewed sources

No public record identifying participating Nations, issues raised, outcomes, or accommodation measures was found.

Sources [5], [6]

Approval and public process

Rezoning and adding a permitted use do not authorize construction. The project still requires a development permit and comprehensive development agreement, plus any building, servicing, utility, and regulatory approvals that apply.

Public record

Area structure plan

Not required for this site

On March 11, 2025, Council corrected the legal land description and exempted the approximately 310-acre site in Pt. N ½ 35-23-28-W4 from an area structure plan requirement.

Sources [7]
Public record

Public hearing

April 1, 2025

Council opened and closed the hearing before giving Bylaw 014-25 second and third reading.

Sources [4], [7]
Public record

Land-use approval

Approximately 310 acres redesignated

The lands changed from Urban Transition to Business Park / Light Industrial, and Data Centre Campus became a permitted use.

Sources [5]
ADCW context

Development permit

Not verified

ADCW found no public project-specific development-permit decision through September 7, 2026. The absence of a located record is not proof that no application has been made.

Sources [7], [5]
Public record

Development agreement

Required before permit issuance

The bylaw requires a comprehensive agreement concerning municipal services and other matters deemed necessary by the Development Authority.

Sources [5]
Public record

Community-impact measures

Permit-stage discretion

The Development Authority may require mitigation for dust, traffic, noise, and visual effects. Security measures and a fire-safety plan are mandatory.

Sources [5]

Timeline

Observed decisions and future dates are kept distinct; projected milestones may change.

  1. Proponent statement

    Beacon presents the proposed Chestermere Enterprise AI Hub to Council. [2][1]

  2. Public record

    AESO records the application date for P3107 Chestermere Enterprise A.I. Load. AESO does not identify the applicant. [9]

  3. Public record

    Council exempts the corrected site from an area structure plan requirement and gives Bylaw 014-25 first reading. [7]

  4. Public record

    Beacon and the City hold a community open house on the land-use application. [3]

  5. Public record

    Council holds the public hearing and passes Bylaw 014-25 at second and third reading. [5][7]

  6. ADCW context

    ADCW review finds the provincial registry still lists the project as proposed and does not identify a later project-specific development permit or construction approval. [8][7]

What we still don't know

Some details have not been made public or remain unresolved. We keep those gaps visible and update them when reliable information becomes available.

  • A development-permit application or decision, subdivision approval, servicing agreement, development agreement, building permit, or construction approval was not identified in the reviewed public sources.
  • The final campus layout, phase sizes, tenant commitments, IT load, construction schedule, and operating date remain unconfirmed.
  • AESO does not name the P3107 applicant, and no approved connection, final transmission route, substation design, energization date, or binding supply agreement was verified.
  • The final role, fuel, capacity, unit count, operating limits, air emissions, and approval path for backup generation are not public.
  • Cooling technology, water source, allocation, demand, consumption, wastewater, and an approved project stormwater design remain undisclosed.
  • No completed noise assessment, predicted receptor levels, mitigation specifications, or monitoring plan was found.
  • No project-specific greenhouse-gas inventory, local air-quality assessment, heat-rejection estimate, or traffic-impact assessment was identified.
  • Project-specific Indigenous consultation participants, concerns, outcomes, and accommodation measures are not established in the reviewed sources.
  • Beacon's current website does not provide a named Chestermere campus page. That absence is not evidence of cancellation.

Source record

Primary and official sources reviewed for this profile. Company disclosures support what the company said, not independent verification of future outcomes.

  1. Beacon Data Centre

    City of Chestermere · Municipal record · 2025-02-27

  2. Chestermere Enterprise AI Hub presentation

    Beacon Data Centers / City of Chestermere · Company disclosure · Presented 2025-02-25

  3. Beacon Data Centre Community Open House

    City of Chestermere · Municipal record · 2025-03-18

  4. Notice of Public Hearing: Bylaw 014-25

    City of Chestermere · Municipal record · 2025-03-11

  5. Bylaw 014-25: Data Centre Land Use Bylaw Amendment

    City of Chestermere · Municipal record · Passed 2025-04-01

  6. April 1, 2025 Council agenda and engagement summary

    City of Chestermere · Municipal record · 2025-04-01

  7. Resolutions of Council

    City of Chestermere · Municipal record · Updated through 2026-09-01; accessed 2026-09-07

  8. Beacon Chestermere AI Data Centre Hub

    Government of Alberta Major Projects · Government database · Accessed 2026-09-07

  9. Connection Project Reporting

    Alberta Electric System Operator · Regulator · Accessed 2026-09-07

  10. Treaty Boundary dataset

    Government of Canada Open Government Portal · Government database · Modified 2026-06-29