A fridge-sized satellite just put Google's TPU in orbit
On October 1, 2026, Google's Project Suncatcher prototype satellite launched aboard SpaceX's Transporter-18 rideshare mission on a Falcon 9, reaching low Earth orbit. The whole satellite is roughly the size of a refrigerator. Its payload: four Trillium TPU chips running a lightweight variant of Google's open-weight Gemma model, answering only simple queries. Built with Planet, the mission has one clear goal — find out whether AI silicon can survive the long-term rigors of space.
Why run AI in space at all
Ground-based AI data centers are running into a wall on power and cooling. Google's math is straightforward: in low Earth orbit, solar irradiance is up to eight times higher than on the ground. Move the rack upstairs and you side-step both the grid and water cooling. TPUs are already the workhorse of Google's on-prem inference fleet, so lifting the same silicon onto an orbital bus means the TF compiler, XLA kernels, and model weights all carry over without a rewrite.
Three gauntlets before silicon ever flies
The team ran almost every pre-flight test on the ground. During the 10-minute ride to orbit, the bus sees sustained accelerations above 10g; small components like the TPU can see localized loads of 50–100g. They shook the whole satellite on a three-axis vibration table, and the hardware held. For radiation, Trillium TPUs were zapped with a proton beam at UC Davis's Crocker Nuclear Laboratory running live AI workloads — measured total ionizing dose tolerance exceeded five years of on-orbit exposure, with bitflip error rates inside acceptable bounds under AI traffic. Vacuum cooling, though, cannot be fully simulated on Earth. With no air convection, heat has to leave via radiator panels. Google used a heat-pipe-plus-radiator stack, validated the prototype in a thermal-vacuum chamber, and is now recalibrating in orbit.
The 15-minute ceiling
Even with only four TPUs on board, heat rejection in vacuum is the bottleneck. Google publicly admits the prototype can run for at most 15 continuous minutes per power-on before it has to cool down. This is not a "space data center" yet — it is an in-orbit testbed: power on, load Gemma weights, fire a handful of inference requests, then shut down and dump heat. The real deliverable is not a benchmark number but a failure curve and an error-rate trace under real space radiation plus vacuum.
Next up: laser-linked dual-satellite test in 2027
The roadmap's next milestone is launching two satellites in early 2027 to validate inter-satellite laser links. The hard part is not raw bandwidth — it is relative positioning. Each satellite has to know exactly where it is and where its neighbors are, and the laser beam must stay locked onto a coin-sized target moving at orbital velocity across tens to hundreds of kilometers. Once that link is solid, multiple satellites can stop being isolated boxes and start acting as one distributed inference cluster.
Sober take: orbital AI is still orders of magnitude away
Industry skepticism toward "space data centers" centers on launch cost, in-orbit servicing cost, and per-satellite compute ROI. Google itself concedes in its paper that getting this approach cost-competitive with terrestrial data centers requires launch prices to drop by roughly two orders of magnitude — a curve that demands simultaneous exponential improvements in hardware, software, and launch services. In the short term, Suncatcher is Google's "fourth option" hedge for next-generation compute, alongside grid, power, and geography. For teams building domestic inference infrastructure, the actionable signal is not "Google is going to space" — it is the engineering data on vibration, radiation, and vacuum cooling, and the existence of a compact TPU node capable of running Gemma in orbit.
Sources: Google's official blog posts Project Suncatcher overview, prototype satellite in orbit announcement, and Behind Project Suncatcher engineering details; Solidot's Google testing space AI data center independently confirms the four-TPU count and the 15-minute runtime cap.