Putting machine learning inference in low Earth orbit, Google has flown its first experimental satellite, but a hard physical ceiling — a 15-minute pulse duty cycle per satellite — keeps it in qualification mode rather than as real on-orbit compute. The Project Suncatcher MVP satellite launched October 1 aboard SpaceX Falcon 9's Transporter-18 rideshare mission, carrying four Trillium (TPU v6e) chips, roughly 1 kilowatt of solar power, and a lightweight Gemma variant answering short prompts — the first hardware step toward an orbital AI data center.

Ground Validation Before Going to Space

Trillium is Google's sixth-generation v6e Cloud TPU, already serving production Gemini inference workloads in terrestrial data centers, repurposed for orbit instead of waiting for a bespoke space-qualified chip. The trade-off is that the silicon must survive three hazards that simply do not exist on the ground:

  • Vibration: Falcon 9 sustains roughly 10 g throughout ascent, with individual TPU components experiencing 50–100 g transients. Google shook the payload across all three axes on a vibration table at rocket-launch frequencies and reported the hardware held up "surprisingly well."
  • Radiation: at UC Davis's Crocker Nuclear Laboratory, Trillium was irradiated with a 67 MeV proton beam while running live AI workloads and monitored for bit flips. Core TPU logic survived a cumulative total ionizing dose of 15 krad(Si), versus the 750 rad(Si) requirement for a five-year shielded mission — a 20x margin. The HBM subsystem proved the most sensitive component, only showing irregularities past 2 krad(Si), still roughly 3x the mission requirement.
  • Thermal: in a thermal vacuum chamber, the team validated heat-pipe-plus-radiator architecture against the vacuum and thermal cycling of orbit. This is where the 15-minute pulse duty cycle comes from.

Only after ground validation was the MVP allowed onto the rocket.

15 Minutes Is Physics, Not Policy

Google Senior Director Travis Beals' early-October framing — that the chips can only run "for about 15 minutes at a time" — is not a scheduling choice. It is a hard upper bound set by vacuum heat rejection.

Terrestrial data centers rely on forced air or chilled liquid cooling. In a vacuum, neither works. Heat must travel by heat pipe to a radiating surface, and Stefan-Boltzmann scaling kicks in: rejection power scales with the fourth power of temperature and with radiator area. Futurum's math: a single Trillium dissipates roughly 333x the heat flux that a current radiator panel can continuously shed, so continuous operation would need about 1.3 square meters of radiator per chip.

What the 15-minute ceiling means in practice:

  • Short-form workloads are feasible: Gemini-class Q&A, embeddings, and document summarization — inputs and outputs on the order of thousands of tokens — can finish inside a single cooldown window.
  • Training and long-context inference are essentially impossible: any workload that needs minutes of sustained compute will hit the thermal wall.
  • The system must run in batch bursts: the satellite is not "always running AI" — it wakes up, processes a burst, sleeps to radiate heat, then wakes again.

MVP's design life is roughly one year (it will deorbit within six years under atmospheric drag). The single most important number from this mission is how the radiator architecture holds up under real orbital day/night thermal cycling.

End-State: 81 Satellites and 10 Tbps Optical Inter-Satellite Links

A single satellite is not the architecture. Google's research pre-print "Towards a future space-based, highly scalable AI infrastructure system design" maps out the path past 2027:

  • 81 satellites in a 1 km radius cluster at 650 km altitude in dawn-dusk sun-synchronous orbit: nearest-neighbor spacing oscillates between roughly 100 and 200 meters, and the simulations show only modest station-keeping is required to keep the formation stable.
  • Optical inter-satellite links: a bench-scale demonstrator using commercial off-the-shelf DWDM transceivers already hit 800 Gbps one-way and 1.6 Tbps bidirectional on a single transceiver pair, with the target of pushing effective per-link throughput into the 10 Tbps range to support all-reduce style distributed ML.
  • Two more satellites in early 2027: to prove that two satellites flying at 28,000 km/h relative velocity can keep a laser link stable. That is the make-or-break test for whether the architecture can scale at all.

$200/kg Launch Cost Is the Economic Tipping Point

Google's own math puts the threshold at $200 per kilogram to LEO. Today's reusable Falcon 9 sits near $3,600/kg — an order of magnitude away. To close that gap by the mid-2030s, Google's model assumes Starship hits a 20% learning curve and flies roughly 180 times per year, an un-precedented launch cadence.

Once that number holds, the annualized launch-and-operations cost of a Starlink v2-class satellite approaches the power bill of a terrestrial AI data center (roughly $570–$3,000 per kilowatt per year). Futurum's deeper estimate: current on-orbit compute runs about $72.1 billion per gigawatt excluding compute silicon, versus $16.2 billion for off-grid terrestrial — a 4.5x premium that only launch cadence and satellite manufacturing scale can collapse.

Not Replacing the Ground — Capturing the Solar Quota

Read against Google's broader compute footprint, Project Suncatcher is not aimed at replacing terrestrial TPU pods. It is a bet on a quota the ground cannot replicate — sunlight.

In a dawn-dusk orbit, satellites sit in nearly continuous sunlight, with photovoltaic output up to 8x more productive per unit area than the same panel at mid-latitudes on Earth, and without the need for large battery storage. Futurum projects AI compute demand could swell to roughly $1 trillion in capex by 2030, with over 33% of data centers forced off-grid by interconnection queues — and once you are off-grid, the solar quota is a real, money-saving edge.

In the short term, this is still qualification phase. MVP in orbit, 15-minute pulses, four TPUs answering Gemma questions — that is nowhere near replacing ground-side GPU or TPU pods. But Google has put a timeline on the table: a two-satellite formation in 2027 to validate optical inter-satellite links, then an 81-satellite, eventually gigawatt-scale orbital compute cluster in the years that follow.

So what? Terrestrial hyperscale data centers are bumping into a wall on power, land, and cooling simultaneously. The L4–L5 sun-synchronous solar quota, the moment Starship hits commercial cadence, shifts from a research curiosity into an investable source of compute. No one is canceling terrestrial TPU pods this decade — but in a decade, the math could flip. That is why Google is putting chips on a rocket.