Google's AI-equipped satellite transmits first response from space, running Gemma 4 model on TPUs

Posted on Oct 31 • Originally published at pklavc.com • AI-assisted

On 30 October 2026, Google announced that its first AI-equipped satellite, internally referred to as Project SunCatcher, successfully booted its on-board Tensor Processing Units (TPUs) and generated an initial response from orbit. The satellite ran a Gemma 4 model instance and produced a haiku describing its perspective from space, confirming end-to-end operation of the hardware and software stack in the space environment. Both The Verge and TechCrunch reported the milestone on the same day, citing a Google blog post as the primary source.

The event marks the first time Google has operated a data-center-class accelerator in orbit. The satellite is described as the company's first "data center satellite," indicating an architecture intended for general-purpose compute rather than a single fixed payload. The on-board TPUs executed inference for the Gemma 4 model, and the resulting text was transmitted to ground stations and received by Google engineers. No further details about the satellite bus, launch vehicle, orbital parameters, or ground-segment topology were disclosed in the two reports.

TPUs powered on and executed inference in orbit on 2026-10-30.

Model executed was Gemma 4; output was a haiku about being in space.

Satellite designated as Google's first "data center satellite."

First response received by ground stations and confirmed by Google.

No public disclosure of satellite bus, orbit, power budget, thermal design, or communication link specifications.

Running TPUs in low Earth orbit introduces a constellation of engineering constraints that differ fundamentally from terrestrial data centers. The radiation environment—trapped protons in the inner Van Allen belt, galactic cosmic rays, and solar particle events—can induce single-event upsets (SEUs) and latch-up in silicon not hardened for space. Google's ability to boot the TPUs and complete an inference pass implies either that the devices are radiation-tolerant by design, that the satellite operates in a sufficiently low-inclination, low-altitude orbit to minimize exposure, or that system-level mitigation (error-correcting codes, watchdog timers, redundant cores) is active. The public sources do not disclose which approach, or combination, was taken.

Thermal management is a second critical axis. TPUs dissipate tens to hundreds of watts per chip; in vacuum, heat can only leave the payload via conduction to radiators and subsequent radiation to deep space. The satellite must therefore carry deployable or body-mounted radiators sized for the peak compute load plus margin for solar loading and albedo. The fact that a sustained inference run completed without reported thermal shutdown suggests the thermal-control subsystem—heat pipes, loop heat pipes, or pumped fluid loops—functioned as designed. Again, the architecture of that subsystem was not disclosed.

Power generation and storage form a third constraint. A TPU pod plus host processors, memory, and communications payload likely demands several hundred watts continuous. The satellite must therefore carry solar arrays and batteries sized for eclipse periods (roughly 35 minutes per 90-minute orbit in LEO). The successful inference indicates the power budget was met during the demonstration window, but the duty cycle for sustained operation—whether the satellite can run TPUs continuously or only during sunlit passes—remains undisclosed.

Continue reading: Full technical article on PkLavc

Explore more technology articles: PkLavc Tech Blog

Telegram: https://t.me/PkLavcTech Discord: https://discord.gg/zder5EZRK