NORAI: Building Canada's Sovereign AI Platform

Reading time ~5 minutes

Why Build Something That Might Not Succeed?

Every ambitious project starts with a simple question. For us, it was: Why doesn’t Canada have a unified AI platform for science?

The US has one. Just days ago, the Department of Energy launched the Genesis Mission, an initiative to integrate AI capabilities across American national laboratories. It is a bold vision: connect data, compute, and researchers to accelerate discovery in energy, climate, and health.

Canada has the pieces. World-class research institutions. Supercomputing facilities in Montreal, Toronto, and Edmonton. A thriving AI ecosystem. But no unified platform connecting them. Data siloed across provinces. Researchers navigating a fragmented landscape of compute clusters. Potential for AI-driven breakthroughs sitting untapped.

NORAI (Nord/North AI) is our attempt to change that conversation. Not by waiting for government to act, but by building something tangible that shows what could exist.

The Vision

NORAI envisions doubling Canadian scientific productivity within a decade by integrating scientific datasets, laboratories, and supercomputers from coast to coast under one secure, bilingual, Indigenous-consent-aware national platform.

The platform addresses five critical Canadian science priorities:

  1. Permafrost & Northern Infrastructure Resilience - Predicting infrastructure failures 10+ years in advance
  2. Fusion Energy & Critical Minerals - Accelerating research into clean energy and resource independence
  3. Pan-Canadian Cancer & Health Intelligence - Unified health data platforms for breakthrough treatments
  4. Climate & Ice Prediction - 1-km resolution climate modeling
  5. Sovereign Quantum & Semiconductor Design - Canadian-controlled advanced computing

The Project: Start Small, Think Big

Grand visions need concrete starting points. Ours is a web application designed to:

  • Communicate the vision clearly to researchers, policymakers, and the public
  • Gather interest from potential partners and stakeholders
  • Demonstrate what a bilingual, accessible Canadian platform could look like
  • Learn by building rather than just planning

Why These Technology Choices:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                       NORAI WEBSITE                          β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚  Framework:    Next.js 15 (App Router, TypeScript)          β”‚
β”‚  Styling:      Tailwind CSS 4 (Northern/Arctic theme)       β”‚
β”‚  i18n:         next-intl (English/French bilingual)         β”‚
β”‚  Animations:   Framer Motion                                β”‚
β”‚  Charts:       Highcharts                                   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
  • Next.js 15 because a Canadian platform must be fast and accessible from Yellowknife to Halifax
  • next-intl because bilingualism is not optional, it is foundational to Canadian identity
  • Tailwind with a Northern theme because visual identity matters when speaking to government
  • TypeScript because infrastructure code demands reliability

Key Features

Homepage

  • Hero section with animated aurora background
  • Stats showcasing the scale: 17+ Labs, 200 MW Compute, $2.5B Investment target
  • Overview of the 5 Grand Challenges
  • Platform architecture visualization

Challenges Page

  • Detailed breakdown of each scientific priority
  • Impact metrics and potential outcomes
  • Canadian-specific context for each challenge

Platform Architecture

  • 5-layer sovereign architecture:
    1. National Semantic Layer (knowledge graph)
    2. Federated Data Lakehouse (distributed storage)
    3. Secure Multi-Party Compute Enclave
    4. Borealis Model Family (Canadian-trained AI)
    5. NORAI Studio (researcher interface)

Computome Initiative

  • Unified gateway for Canadian HPC resources
  • Routes jobs across national clusters (Cedar, Narval, Niagara, Graham, Beluga)
  • Startup-friendly pricing ($1/GPU-hour vs $3+ on AWS)
  • Free tier for students and Indigenous communities

What Makes NORAI Different

While inspired by the Genesis Mission, NORAI is designed with Canadian values:

  • Federated Model: Makes provincial fragmentation a strength (resilience + choice)
  • Indigenous Priority: OCAP (Ownership, Control, Access, Possession) principles built-in
  • Bilingual Operations: Full English/French/Inuktitut support
  • Carbon-Optimized: Intelligent routing based on queue time, data locality, and carbon footprint
  • Data Sovereignty: PIPEDA compliance with enforced geographic boundaries

The Honest Reality: Why We Build Anyway

Let us be direct: NORAI might not succeed.

Building national infrastructure requires government buy-in, significant funding, and coordination across provinces with different priorities. We are a small team with a website, not a government agency with a budget.

So why build it?

Because the alternative is waiting. Waiting for someone else to start. Waiting for perfect conditions. Waiting while other countries build their AI infrastructure and Canada falls behind.

What we gain regardless of outcome:

  1. Learning by doing - Every line of code teaches us about platform design, accessibility, and bilingual development. These skills transfer even if NORAI never becomes a national platform.

  2. Starting conversations - A working prototype opens doors that a slide deck cannot. Researchers and policymakers can see and interact with the vision.

  3. Demonstrating possibility - Sometimes people need to see something exist before they believe it could exist at scale.

  4. Building in public - Transparency about challenges invites collaboration. Someone reading this might have the connections or resources we lack.

The spectrum of outcomes:

  • Worst case: A well-designed website that showcases Canadian AI ambitions and teaches us Next.js
  • Middle case: A catalyst for conversations that lead others to build something better
  • Best case: A prototype that attracts enough interest to become real infrastructure

All three outcomes are worth the effort.

Development Approach

The project follows a phased roadmap:

Phase 0: Foundation (Current)

  • Website v1 with core messaging
  • Legal and branding setup
  • Initial outreach to potential partners

Phase 1: MVP Platform

  • Partner dashboard
  • Initial dataset integrations
  • Pilot with 1 university + 1 Indigenous group
  • Goal: 1,000 visitors, 50 letters of intent

Phase 2: Government Proposal

  • Submission to ISED Sovereign Compute Initiative
  • Expanded partnership network
  • Technical prototype demonstrations

What We Have Learned So Far

Even in early development, the project has taught us:

  • Bilingual development is harder than it looks - It is not just translation. It is rethinking UI layouts, handling text expansion, and respecting cultural context.
  • Government-friendly design requires restraint - The temptation to add flashy animations fights against the need for accessibility and professionalism.
  • Vision documents are easier than working code - Writing a whitepaper about federated data lakehouses is simpler than actually building one.
  • The Canadian tech community is supportive - Early conversations have been encouraging, even when people are skeptical about outcomes.

Conclusion

NORAI is an experiment in building something ambitious with humble beginnings.

Canada has the talent. The resources. The need. What it lacks is a unified platform connecting them. Maybe NORAI becomes that platform. Maybe it inspires someone else to build something better. Maybe it just teaches us how to build bilingual Next.js applications really well.

All of those are fine.

Sometimes the best way to advocate for an idea is to start building it. The code is open. The vision is clear. The outcome is uncertain.

That is exactly how interesting projects should start.

Ngrok

From Localhost to the World: Using ngrok with Your Flask ApplicationIf you have ever built a Flask application, you are probably familiar...… Continue reading