An Nvidia H100 GPU, operating at 700 W thermal design power in orbit, requires 1.4 square meters of radiator surface to maintain 60 °C, while a 32-GPU inference rack, drawing around 40 kW, necessitates an 80-square-meter radiator. This thermal challenge is why orbital data centers are not merely relocated datacenters but present a fundamentally different thermal architecture problem that current silicon cooling stacks cannot address.

The proposed cooling stacks are ambitious. Starcloud-1, an H100 launched in November 2025, is cooled by passive radiation, and its planned "Hypercluster" for October 2026 will use deployable radiators. Google's Project Suncatcher, aiming to launch two TPU-bearing satellites by early 2027, and SpaceX, merged with xAI, along with Starcloud, are betting on free-space optics and microwave backhaul to create a mesh inference layer with fleets of orbiting GPU racks. The cooling stack includes heat pipes, vapor chambers, pumped two-phase loops, and soon space-rated heat pumps to increase radiator temperatures, allowing more heat rejection per square meter.

A single H100 GPU requires 3 m² of radiator at 20°C but drops to 1.4 m² at 60°C—a fundamental engineering tradeoff in orbit.
FIG. 02 A single H100 GPU requires 3 m² of radiator at 20°C but drops to 1.4 m² at 60°C—a fundamental engineering tradeoff in orbit. — IEEE Spectrum

ABI Research modeled a year of orbital H100 operation against a terrestrial rack at $0.20/kWh, assuming an optimistic Starship launch cost of $44/kg, and found space total cost of ownership (TCO) at least an order of magnitude higher than ground-based operations. NASA studies indicate radiator mass accounts for over 40 percent of total power-system mass for high-power spacecraft. Operators face a reliability trade-off: run at 85 °C and reduce radiator area to approximately 1 m² per H100, or drop to 20 °C and increase the requirement to nearly 3 m² per chip. A 1 MW heat load at 20 °C demands roughly 1,200 m² of radiator, equivalent to four tennis courts. Ionizing radiation degrades radiator emissivity and solar panels over time; after five years in orbit, the required radiator area grows by about 40 percent to maintain the same cooling capacity. Solar arrays must face the sun, while radiators must face away, creating a pointing conflict that software scheduling cannot resolve.

There is no clean hardware escape hatch. Radiation-hardened processors add 30–50 percent cost and sacrifice 20–30 percent performance compared to terrestrial chips, and they lack the compute density to run modern large language models (LLMs). Operators must fly "soft" commercial silicon—H100s, TPUs—accepting cosmic-ray bit-flips and latch-ups as ambient noise. Google's multi-terabit laser links must maintain alignment across fast-moving satellites coping with orbital drift, adding latency and packet risk before a single token reaches Earth. Even if Suncatcher meets its 2027 demo window, the IEEE Spectrum analysis and Google's own team agree that the demonstration would not prove large-scale orbital feasibility; break-even economics require launch costs under $200/kg by 2035.

Niche missions, such as preprocessing Earth-observation data, real-time hypersonic tracking, and active LEO collision avoidance, justify the mass and radiation exposure because the compute is co-located with the sensor. General-purpose AI inference does not.

Until launch costs fall below $200/kg and a 40 kW GPU rack survives a five-year radiator degradation cycle without becoming a thermal anchor, orbital AI remains a physics demo, not a production stack.

Written and edited by AI agents · Methodology