Canadian Sovereign Compute
Canadian Sovereign Compute Infrastructure.
Sovereign Shield Energy Compute Campus is designed for organizations that need Canadian-hosted, Canadian-operated, hydro-powered digital infrastructure with clear controls around data residency, operational access, security, connectivity, and customer governance.
Canadian
Sovereign Jurisdiction
All infrastructure and operations
Hydro
Power Strategy
Clean, stable, Canadian-controlled
1.05 GW+
Planned Campus Capacity
7 phases — Q2 2027 targeted start
3
Customer Control Models
Colocation, Shell, Land
Section 1 of 5
Sovereignty Is More Than Location.
Physical location is necessary but not sufficient for Canadian sovereign compute.
Data residency matters, but physical location alone does not answer every sovereignty question. Organizations evaluating Canadian sovereign infrastructure must also consider operational control, personnel access, encryption and key custody, contractual controls, supply-chain exposure, incident response, audit evidence, and the legal structure of their providers and workloads.
Sovereign Shield Energy Compute Campus is designed with these requirements in mind. The campus is physically located and operationally controlled within Canadian jurisdiction. The operating framework, access controls, documentation standards, and service delivery model are built to support organizations for whom sovereignty is a serious requirement — not a marketing label.
The campus does not guarantee legal sovereignty outcomes — those depend on each organization's workload architecture, contracts, encryption model, and applicable law. What Sovereign Shield provides is a credible, documented, diligence-ready Canadian infrastructure platform designed to support sovereign-grade deployments.
Where is my data physically located?
On campus infrastructure within Canadian jurisdiction. No cross-border data paths required.
Who can access my infrastructure?
Customer-defined access controls, documented visitor management, and vendor access governance per service model.
What happens to my data if there is an incident?
Pre-defined incident response procedures, escalation paths, and evidence records. Customer notification workflows defined in service agreement.
Can I control encryption keys?
Yes — depending on service model. Powered Shell and Powered Land customers have maximum control over their encryption architecture.
Is this a government program or procurement?
No. Sovereign Shield ECC is a commercial infrastructure offering. It is not a government program, grant, or public-sector procurement vehicle.
Designed to Support
What Sovereign Shield Is Designed to Support.
Nine capability areas designed around the real requirements of sovereign, regulated, and data-sensitive workloads.
Canadian Data Residency
Infrastructure physically located and operated within Canadian jurisdiction. Designed to support workloads where data must remain in Canada.
Canadian Operational Access Models
Options for customer-defined access controls, Canadian-personnel requirements, and vendor access governance. Designed around documented access and accountability.
Customer-Controlled Encryption
Support for customer-controlled encryption key strategies and key management approaches, depending on service model and customer architecture.
Regulated Workload Diligence
Diligence packages covering power architecture, physical security, operations framework, connectivity, and compliance controls available for regulated-sector review.
Public-Sector & Institutional Support
Campus design and documentation structured to support public-sector-adjacent and institutional procurement processes, including sovereignty qualification questions.
Carrier-Neutral Canadian Connectivity
GridMetro, TELUS (as a planned campus carrier in a connectivity context only), and a third carrier TBD. Canadian-routed options. Customer-procured carrier relationships. No forced cross-border routing.
Secure Physical Campus Controls
Layered physical security, zone-based access credentialing, CCTV, perimeter control, visitor management, and 24/7 staffed operations.
Evidence-Based Operations
Commissioning records, audit-ready documentation, corrective action tracking, and operational readiness review processes — evidence, not just assurance.
Hydro-Powered Capacity Planning
Canadian hydro-backed power supply. No fossil-fuel exposure. Phased capacity planned across 7 phases to GW+ total campus capacity.
Customer Control Models
Customer-Controlled Architecture.
Three service models with different levels of customer control — from turnkey operations to fully self-operated facilities.
Sovereign Shield supports multiple customer control models. Some customers may choose turnkey colocation under the GridColo framework. Others may choose powered shell or powered land to retain deeper control over facility design, IT architecture, operating procedures, encryption, personnel access, and workload segmentation. Each model has a defined service boundary and explicit responsibilities on each side.
Turnkey Colocation
Full-service colocation under the GridColo operating framework. Power, cooling, security, network access, and 24/7 operations delivered by the campus team. Customer controls their IT equipment and data.
- Physical data residency in Canada
- Canadian campus operations team
- Documented access control workflows
- Visitor and vendor management
- GridColo service boundary defined in agreement
Powered Shell
Customer installs IT into a commissioned, compute-ready building. Deeper control over facility layout, IT architecture, personnel access, encryption, and operational procedures — without managing the full greenfield build.
- Customer-designed IT environment
- Defined facility boundary and access control
- Customer-controlled encryption and key strategy
- Campus power, security, and connectivity services
- Independent facility operating procedures
Powered Land
Maximum customer control. Customer designs, builds, and operates their own facility on a secured campus parcel. Campus delivers power, perimeter security, and connectivity pathways to the parcel boundary.
- Fully customer-designed and operated facility
- Customer-defined personnel and access policies
- Independent encryption and security architecture
- Campus power, connectivity, and perimeter services
- Maximum workload isolation and design flexibility
Sovereignty Diligence Questions
The Questions Serious Evaluators Ask.
Sovereign Shield is designed to be able to answer the questions that regulated-sector buyers, institutional procurement teams, and mission-critical operators actually ask during diligence. We organize our documentation around these questions — not around marketing narratives.
Request Diligence AccessWho owns the land and facilities?
Canadian project vehicle. Site control documentation available to qualified reservation holders.
Who has physical access to my infrastructure?
Defined per service model. Credentialing, visitor management, and vendor access governance documented for each model.
Who has logical access to my infrastructure?
Customer-defined per service model. Powered Shell and Powered Land give maximum customer control over logical access.
Where does my traffic route?
Canadian-routed carrier options. No forced cross-border traffic paths.
Who can compel disclosure of my data?
Legal jurisdiction is Canada. No claim is made about foreign law applicability — consult your legal counsel for workload-specific analysis.
What evidence exists that this is operationally ready?
Commissioning records, test data, supplier contracts, safety documentation, and financial close evidence available in structured diligence room before Call Date.
Diligence Packages
Structured Evidence for Structured Reviews.
Sovereign Shield ECC is structured to support diligence reviews from tenants, lenders, insurers, public-sector procurement teams, and regulated-sector compliance functions. Diligence packages are organized by domain and available to qualified reservation holders during the technical review phase.
The standard is evidence, not assurance. Programs are designed to support diligence readiness and audit-ready documentation — not just program existence.
Request Diligence AccessCampus Overview Package
Site overview, campus model, power strategy, and GridCore framework summary.
Power & Capacity Package
Campus electrical distribution, redundancy approach, phase schedule, and capacity terms.
Connectivity Package
Carrier strategy, campus fiber infrastructure, meet-me-room model, and cross-connect workflows.
Physical Security Package
Perimeter controls, zone architecture, credentialing, CCTV, and visitor / vendor management.
Operations Framework Package
GridColo operating model, domain authority matrix, escalation paths, and SLA structure.
Sustainability / Energy Package
Hydro-electric power strategy, environmental compliance posture, and sustainability positioning.
Compliance Controls Matrix
Controls mapping for ISO 27001 alignment, SOC 2 support, NIST, and Canadian privacy / data residency.
Customer Onboarding Package
GridColo service onboarding, access workflows, ticketing, remote hands, and escalation paths.
Service Boundary / Responsibility Matrix
Explicit RACI covering campus responsibilities versus customer responsibilities across all service models.
Reservation-to-Agreement Package
LOI process, qualification workflow, Call Date mechanics, and definitive agreement framework overview.
Important Boundaries
What Sovereign Shield Does Not Claim.
Accurate sovereign compute positioning requires honest boundaries.
Sovereign Shield Energy Compute Campus is a commercial infrastructure offering. Final data residency, sovereignty, privacy, cybersecurity, procurement, and regulatory conclusions depend on each customer's workload, architecture, provider structure, contracts, encryption model, operating procedures, and applicable law. Sovereign Shield supports customer diligence but does not provide legal advice.
This is not a government program, grant program, or public-sector procurement vehicle.
This is not a securities offering or investment solicitation.
Sovereign Shield does not guarantee legal data sovereignty outcomes — those are determined by your workload architecture, contracts, and applicable law.
TELUS is listed as a planned campus carrier in a connectivity context only. TELUS is not the operator, developer, investor, government sponsor, or anchor tenant.
No official Canadian government logos, endorsements, or procurement approvals are implied or claimed.
All capacity dates and phase schedules are target estimates subject to utility coordination, permitting, equipment availability, and commercial execution.
Reserve Canadian Sovereign Compute Capacity.
Submit a non-binding Capacity Reservation LOI for 1 MW to 150 MW. Initial Call Date expected Q4 2026. Phase 1 first capacity targeted for Q2 2027.