The short version
- Michael Geist published his keynote “Digital Sovereignty: Control, Choice, and Connection” today, delivered last week at CANARIE’s NREN Assembly. The title names the three poles of the debate, and they are landing on procurement desks.
- Bell’s AI Fabric expansion in Saskatchewan, from 300MW to 1.2GW with more than C$50 billion announced September 14, sits under the province’s August 27 Data Centre Framework: Canadian ownership, data and AI sovereignty, self-supplied power.
- Ottawa’s responsible data centre development principles, launched September 8 with 25 industry signatories, set a national baseline. The privacy team’s job is to convert all three moves into contract questions about control, location, staff, model processing, and foreign government access.
The keynote that named the moment
This morning, Michael Geist published Law Bytes Episode 279: his full keynote from last week’s NREN Assembly, hosted by CANARIE for Canada’s research and education networks. The title is the whole argument in miniature: Digital Sovereignty: Control, Choice, and Connection.
I will not pretend to review a talk from a blog post. But the three words arrive at exactly the right moment: sovereignty stopped being a panel topic in Canada this fall. It is a construction project now.
The concrete
September 14, Toronto. At Canada’s first Investment Summit, Prime Minister Mark Carney and Saskatchewan Premier Scott Moe stood with Bell CEO Mirko Bibic to announce Bell is quadrupling its Saskatchewan AI data centre to 1.2 gigawatts. More than C$50 billion in capital, per the Canadian Press, the largest private-sector investment in the province’s history. Carney called it “the largest sovereign AI infrastructure network in Canada.” The 300MW first phase in Sherwood, near Regina, is under construction and reportedly pre-sold to Cerebras and CoreWeave; the extra 900MW runs on a Bell-built off-grid gas plant, per the province’s bring-your-own-power principle.
The ground it sits on, August 27. Saskatchewan released its Data Centre Framework: six principles, Canadian ownership, data and AI sovereignty, Saskatchewan jobs, industry experience, self-supplied power, a centralized intake. “Our government chooses Canada,” said Jeremy Harrison, the province’s minister of Crown Investments. Policy, not law, but every proponent knows what gets graded.
The wrapper, September 8. Ottawa launched its responsible data centre development principles, announced by AI and Digital Innovation Minister Evan Solomon with the Federation of Canadian Municipalities. Five expectations: lasting local benefits, no shifting electricity costs to Canadians, minimized water and environmental impact, transparency about local impacts, strategic value to the country. The signatory list is the signal: AWS, Google, Microsoft, Meta, Anthropic, OpenAI, Cohere, OVHcloud, Bell, TELUS, Equinix, Cologix, eStruxture, ThinkOn, and ten more.
Three moves, one direction: the infrastructure that holds Canadian data is being built, owned, and powered on Canadian terms, and the largest American labs and clouds are signing the federal principles to stay in the game.
Here is the part the press releases skip. The sovereign campus runs on American silicon and pre-sold American compute. Sovereignty here means Canadian ownership and Canadian power, not Canadian tenants. Whether that counts depends on what you think sovereignty is for, which is exactly the debate the keynote names. Practitioners on Reddit are blunter: several describe vendor sovereignty claims as theatre when a CLOUD Act request can reach the same data regardless of where the servers sit.
Three regimes, one questionnaire
Sovereignty now arrives through three rulebooks. Side by side, a pattern: every regime asks the same questions, with different teeth.
| Regime | What it tests | How it bites |
|---|---|---|
| Saskatchewan Data Centre Framework | Canadian ownership, data/AI sovereignty, self-supplied power | Provincial intake and assessment of new projects |
| Federal responsible data centre principles | Local benefits, no cost shifting, transparency, strategic value | Industry commitments; municipal decision baseline |
| EU CADA tiers (see my October 5 piece) | Graded assurance on control, staff, location, access-blocking | Procurement gates; associated-country path for Canada |
The October 29-30 EU-Canada summit in Montreal is where the trade layer gets discussed, if it gets discussed at all. The communique may land associated-country terms, or it may stall. Your contracts are where the control layer gets decided. Do not confuse the two.
What to write into your vendor files
Forget the marketing version of sovereignty. Ask for the operational version, in writing, and keep the answers in the vendor file:
- Control. Who owns and controls the provider, through what corporate structure, and what changes on acquisition? Saskatchewan made this a headline principle for a reason.
- Location of everything. Where does your data rest, get processed, get supported from, and get used to train models? Name the regions, not the marketing.
- Support-ticket access. Who can touch your data in a support ticket, from where, under what access controls? The question most vendor files still cannot answer.
- Foreign government demands. What is the provider’s documented process when a foreign government demands access, and where is it published? An assurance label does not stop a court order.
- Subprocessors and model pipelines. Which subprocessors and AI model providers sit underneath the service, and in which jurisdictions do they operate? Your AI vendor has vendors.
Two of these break deals: support-ticket access and the foreign-demand process. If your file cannot answer them, the file is not done.
Actionable takeaway: Take your five highest-risk vendors by data sensitivity, not by spend, and run the five questions above against them before the October 29 summit. The summit will set the trade terms, or fail to. Your vendor files will decide whether your data is actually sovereign when the lawyers come asking.