On 11 January 2026, a SpaceX Falcon 9 lifted off from Vandenberg Space Force Base carrying the first commercially operated standalone compute units in orbit. Not a research experiment. A commercial service offering.
What changed in January 2026 is that Axiom Space crossed the line from announced to operational. The nodes are running on Kepler Communications satellites in low-Earth orbit, and workloads can be submitted right now. Is this real, and should you care? Yes and yes — with caveats. We’ll cover what launched, what workloads are viable, how the hardware and software work, and what the Axiom milestone does and does not prove. For the bigger picture, that sits in the computing beyond the grid story.
What Did Axiom Space Actually Deploy in January 2026?
Two ODC nodes launched aboard Kepler Communications satellites on 11 January 2026. Each Kepler carrier satellite weighs roughly 300 kg and carries multi-GPU compute modules, terabytes of on-board storage, and four optical terminals — compatible with Space Development Agency Tranche 1 standards running at 2.5 Gbps per link.
Here’s the progression: in 2022, AWS Snowcone became the first commercial AI inferencing hardware on the ISS. In August 2025, Axiom deployed AxDCU-1 — a prototype sponsored by the ISS National Laboratory, running Red Hat Device Edge and MicroShift. The January 2026 Kepler-hosted nodes are the standalone successor — commercial infrastructure, not a NASA-hosted experiment.
Operating altitude is around 400 km — low-Earth orbit (LEO) — giving you roughly 5–20 ms round-trip latency versus ~600 ms for geostationary orbit. One transparency note: Axiom hasn’t publicly released per-node performance specs or customer names. Everything here is sourced from ISS National Lab press releases, Axiom product announcements, and Kepler’s technical filings.
What Workloads Are Actually Running on Orbital Data Centre Nodes?
At current kW-scale, the viable categories are: AI/ML inference, Earth observation data fusion, satellite telemetry processing, and sovereign cloud compute. That list is short and deliberate.
AI training is out. Training large models requires roughly 7.2 Tbps of GPU interconnect bandwidth. Current optical inter-satellite links deliver around 100 Gbps — one to two orders of magnitude short. Inference on pre-trained models fits. Training does not.
Earth observation is the primary demand driver. The raw data from a single imaging pass can exceed ground downlink capacity. Process on-orbit — filter, compress, analyse — and you cut result latency from hours to minutes. Planet Labs is already doing this with NVIDIA GPUs on their Pelican satellites.
Sovereign cloud is the use case with the strongest near-term consensus. 141 countries have data localisation laws — orbital nodes can process data during an orbital window over a given territory without touching conflicting terrestrial infrastructure. Defence contractors, national space agencies, and financial institutions in data-sensitive markets are already paying attention. That market doesn’t need hyperscaler scale; kW-scale is enough for the right use case.
Why COTS Hardware and a Containerised OS — Not Exotic Space Chips?
COTS stands for commercial off-the-shelf — standard, commercially available components rather than custom-designed space hardware. The reason you go COTS is straightforward.
Rad-hard ASICs lag multiple chip generations behind commercial processors. LEO’s radiation environment is manageable with selective shielding on COTS hardware, which means you get near-current GPU performance without the custom design overhead. Starcloud-1 validated that NVIDIA H100 silicon can survive and operate in LEO without a custom redesign.
AxDCU-1 runs Red Hat Device Edge with MicroShift — a lightweight Kubernetes distribution stripped to a single-node footprint. Automated rollback is built in: if an update fails validation during a contact window, the system reverts without ground intervention. The abstraction layer is familiar; it’s the contact window scheduling, radiation-induced bit flips, and thermal cycling that require orbital-specific middleware not found in standard Kubernetes.
What Is the SWaP Constraint and Why Does It Define Orbital Compute Today?
SWaP stands for Size, Weight, and Power — the three physical constraints that define what hardware can go on a satellite. Kepler’s ~300 kg satellites have a limited payload envelope; a standard DGX server rack does not fit. Launch costs run approximately 1, 500–2,500 per kilogram to LEO, so every kilogram is expensive. Solar panels on a LEO satellite are limited — current nodes operate at kW-scale while terrestrial hyperscaler racks run at megawatt scale. That gap defines the workload envelope. Everything comes back to SWaP.
ABI Research estimates an ODC can cost upward of 78x more than a terrestrial equivalent. Starcloud-3, contingent on Starship launch economics, is projected to be the first cost-competitive orbital data centre by 2028–2029. The Axiom/Kepler nodes prove the concept is operational. The scale story is what comes next.
How Does an Orbital Node Handle Heat Without Air?
There’s no air in orbit, which means convective cooling — fans, liquid cooling, the majority of heat removal in terrestrial data centres — doesn’t work at all. The only viable mechanism is radiative cooling: passive panels that re-radiate heat as infrared radiation into space.
To radiate just one megawatt at 20°C, an orbital data centre needs roughly 1,200 square metres of radiator surface — four tennis courts. Compute density is thermally limited by radiator surface area, not just power budget.
LEO thermal cycling adds further complexity: ~90-minute orbital periods alternating between direct solar heating and deep cold (~−150°C). For a full treatment of radiative cooling constraints, ART006 covers the physics in depth.
What Does the Axiom Deployment Actually Prove — And What Does It Leave Open?
Here’s what is documented and operational: COTS hardware with containerised software can survive LEO. Earth observation and AI inference workloads are viable at kW-scale. A developer can deploy a containerised workload to orbit using familiar tooling.
Here’s what it does not prove: cost-competitiveness with terrestrial cloud, scale to training capacity, or SLA commitments that match enterprise expectations. The Axiom deployment is one data point within a broader alternative computing landscape that spans underwater facilities, orbital solar concepts, and purpose-built hardware platforms.
SpaceX’s own S-1 pre-IPO filing states orbital AI compute “involve[s] significant technical complexity and unproven technologies, and may not achieve commercial viability” — from the same company that called space data centres a no-brainer at Davos three months earlier. That tension isn’t noise. It’s an accurate description of where orbital compute sits on the maturity curve.
No operator has published per-inference or per-GB cost figures. The honest planning frame: put orbital compute on a 3–5 year watch list. It’s not an immediate procurement option.
Where Does Orbital Compute Go From Here?
The Axiom/Kepler deployment is Tier 1: kW-scale, single-node inference, OISL relay. It proves the concept is operational.
Tier 2 is announced but not deployed. Starcloud’s planned 88,000-satellite constellation raised $170 million in April 2026, with AWS, Google Cloud, NVIDIA, and Crusoe flying hardware on Starcloud-2. SpaceX filed for up to 1 million orbital data centre satellites. The hardware signal is NVIDIA’s Space-1 Vera Rubin Module — up to 25x more AI compute than an H100 for space-based inferencing. See the NVIDIA Space-1 article for the full picture.
The concrete re-evaluation triggers are: Starcloud-3 deployment (2028–2029), any operator publishing real SLA commitments, and per-workload cost dropping to within 10x of terrestrial cloud. When any of those land, move orbital compute from watch list to evaluate. Until then, keep an eye on the broader planning question — not whether orbital compute arrives, but when it becomes a factor for your specific use cases. For a complete overview of orbital, underwater, and alternative computing environments, see our guide to computing beyond the grid.
FAQ
What is an orbital data centre node?
A purpose-built compute unit on a satellite in low-Earth orbit — processing, storage, and network relay independent of terrestrial infrastructure. Think of it like edge computing: you’re processing at the data source rather than shipping everything to a remote centralised facility. No convective cooling, no persistent power grid, no physical access.
Is the Axiom Space orbital data centre actually operational or still experimental?
Operational. Two nodes launched 11 January 2026 on Kepler Communications satellites as a commercial service offering. The January 2026 nodes are the first standalone commercial deployment. “Operational” means workloads can be submitted — it does not mean published SLA commitments or cost parity with terrestrial cloud.
What software runs on an orbital data centre node?
Red Hat Device Edge with MicroShift — a lightweight Kubernetes distribution for resource-constrained environments. Workloads are deployed as containers, the same way you’d deploy to a terrestrial edge node. Automated rollback and delta updates work over-the-air.
Why can’t you just put a standard GPU server in orbit?
SWaP constraints. A standard DGX server weighs hundreds of kilograms and requires active liquid cooling — neither fits a ~300 kg satellite payload envelope or a vacuum environment. Launch costs of 1, 500–2,500/kg make every kilogram expensive, and passive thermal radiators limit compute density.
What is the latency of an orbital data centre compared to a terrestrial one?
LEO nodes at ~400 km altitude have round-trip latency of roughly 5–20 ms. GEO at ~36,000 km has ~600 ms, making it unsuitable for latency-sensitive workloads. Persistent low-latency connections aren’t available from a single node without a constellation relay architecture.
Can you train AI models in orbit?
Not at current kW-scale. Training requires ~7.2 Tbps of GPU interconnect bandwidth; current optical inter-satellite links run at ~2.5–100 Gbps — a gap of one to three orders of magnitude. Inference is viable. Training is not.
What is the sovereign cloud use case for orbital data centres?
141 countries have data localisation laws. Orbital nodes can process data during an orbital window over a given territory without routing through conflicting terrestrial infrastructure. This has the strongest near-term commercial consensus among defence contractors, national space agencies, and financial institutions in data-sensitive markets.
How is an orbital node different from a satellite with onboard processing?
Commercial access and software abstraction. Purpose-built satellites are designed for one mission. ODC nodes are general-purpose compute infrastructure that any authorised customer can submit workloads to — the containerised OS layer enables multi-tenant, multi-workload operation.
Who are the main competitors to Axiom Space in orbital data centres?
Starcloud: 88,000-satellite constellation, $170M Series A in April 2026, AWS/Google Cloud/NVIDIA/Crusoe on Starcloud-2. SpaceX: FCC application for up to 1 million ODC satellites. Google Project Suncatcher: TPU clusters in orbit, test satellites planned early 2027. OrbitsEdge: first orbital demonstration planned 2026. Blue Origin: FCC application for 51,600 data centre satellites.
What happens to an orbital node if a software update fails?
Red Hat Device Edge supports automated rollback: if a delta update fails validation, the system reverts to the previous known-good state without ground intervention. Contact windows are limited to minutes per pass — a failed update could leave a node in an inconsistent state for hours.
What is the contact window constraint for orbital data centres?
A LEO node at ~400 km is within line-of-sight of any given ground station for approximately 5–10 minutes per ~90-minute orbital pass. Workloads must be queued before the window and results relayed via optical intersatellite links (OISL). Kepler’s OISL constellation partially addresses this by relaying between nodes.
How does heat dissipation work on an orbital data centre node?
Convective cooling doesn’t work in vacuum. Thermal radiators — passive panels that re-radiate heat as infrared radiation — are the only viable cooling mechanism. LEO thermal cycling (solar heating to ~−150°C cold over ~90-minute orbital periods) adds engineering complexity. Waste heat, not power, is described as the binding constraint on high-density orbital compute.
