The Race To Orbit

Executive Summary

The driver is straightforward: terrestrial data centres are hitting hard limits on power, water, and planning consent. AI compute demand is growing rapidly. Space offers uninterrupted solar power, passive radiative cooling, and no land-use politics. The economics are not yet proven at gigawatt scale, but multiple well-resourced actors have concluded that the trajectory justifies investment.

For defence and security audiences, the implications extend beyond energy efficiency. Orbital compute constellations are dual-use infrastructure by design, already attracting interest for missile tracking, ISR data processing, and autonomous space operations. The organisations that establish operational dominance in this layer will hold structurally advantaged positions in both commercial AI competition and future contested scenarios.

Strategic Context

The Terrestrial Bottleneck

AI-related electricity consumption is projected to grow sharply through 2030. Microsoft, Google, and Amazon have collectively committed hundreds of billions of dollars to new data-centre construction, yet power purchase agreements, water rights, grid connection queues, and planning consent are already binding constraints.

The NVIDIA Validation Moment

At GTC 2026, NVIDIA announced the Vera Rubin Space-1 Module: a radiation-hardened AI compute platform for orbital deployment. Six partners immediately confirmed deployment plans. NVIDIA's entry legitimises the market and positions it as the dominant early-entrant vendor, while also creating concentration risk at the compute layer.

The Blue Origin Entry

Project Sunrise proposes up to 51,600 data-processing satellites paired with TeraWave, a 5,408-satellite high-throughput connectivity constellation. Blue Origin's ownership structure gives it a captive hyperscale cloud customer in AWS. No other actor combines rocket capability, broadband constellation, compute constellation, and captive hyperscale cloud in a single ownership structure.

Competitive Landscape

The table below covers twelve organisations with active orbital compute programmes as of March 2026, ranging from operational hardware in orbit to regulatory filings and funded development.

Operational Hardware

Three organisations are already running compute hardware in LEO. Starcloud placed the first NVIDIA H100 GPU in space in November 2025. Kepler Communications launched ten optical compute nodes in January 2026. Axiom Space deployed two orbital data centre nodes on the same flight, explicitly targeting national security workloads including multi-sensor fusion and space threat tracking.

The SpaceX / xAI Full-Stack Ambition

SpaceX merged with xAI in February 2026 and filed an FCC application for up to one million orbital data centre satellites. Terafab, AI Sat Mini, and the D3 custom processor point toward a full proprietary stack: chip design, fabrication, launch, satellite, connectivity, and AI model layer.

China, Energy-Compute Players, And Europe

ADA Space's Three Body Computing Constellation is explicitly state-directed. Aetherflux and Sophia Space are pursuing energy-compute convergence and differentiated cooling approaches. Europe's ASCEND programme is government-backed and sovereignty-focused, but materially behind the commercial trajectory.

Security And Defence Implications

Dual-Use By Design

Orbital compute constellations are not neutral infrastructure. The same systems processing commercial AI workloads can process ISR feeds, support autonomous targeting, and enable in-orbit battle management.

Amplified Attack Surface

The proposed constellation sizes represent a qualitative shift in cyber-physical attack surface. Compromising a compute satellite affects not only communications but active data processing, model inference, and potentially autonomous decision-making pipelines.

Sovereignty And Structural Dependency

The AWS and Blue Origin relationship is a strategic dependency that has not been seriously examined by European or UK defence planners. If AWS becomes the dominant provider for orbital compute, and Blue Origin controls the launch and operational infrastructure, European governments will have limited leverage over a critical node in their AI and ISR architecture.

Regulatory Vacuum

No tailored licensing category yet exists specifically for orbital data centres. The gap is conceptual and environmental: there is no framework calibrated to data-centre-scale constellations in terms of debris mitigation, environmental review, or spectrum allocation for inter-satellite compute links.

Questions For Defence And Policy Planners

1. What doctrine governs commercially operated orbital compute infrastructure during conflict or crisis?
2. How are sovereign AI model training and inference workloads protected in an orbital environment?
3. What are the implications of Terafab for allied chip supply security?
4. What is the UK and European response to the Bezos ecosystem's structural advantage?
5. At what constellation size does orbital debris risk become a compounding strategic threat?
6. Who holds targeting authority over adversary orbital compute nodes processing time-critical ISR data?
7. How should NVIDIA's early vendor position factor into supply-chain security assessments?

Assessment

The orbital compute race is real, accelerating, and under-examined by defence and security institutions in the UK and Europe. The week of 19 to 21 March 2026 alone produced three major developments: Blue Origin's Project Sunrise FCC filing, NVIDIA's Vera Rubin Space-1 announcement, and Musk's Terafab and AI Sat Mini reveal.

The security vulnerabilities of orbital compute infrastructure are an amplified version of those already documented for communications constellations. The difference is consequence: compromising a compute node in orbit is not merely a denial of service. It is potential access to the AI systems, decision pipelines, and intelligence products that depend on that infrastructure.