Suncatcher sends back its first AI result
Google’s prototype ran an AI model on a data-center-class Tensor Processing Unit in orbit and returned the answer to Earth. That moves Project Suncatcher beyond spacecraft health into demonstrated compute, while new designs and supplier engagements begin to define the infrastructure needed around it.
- New projects announced this week
- 1
- New supplier relationships this week
- 3
Distinct verified announcements after 23 October at 5 p.m. through 30 October at 5 p.m. Eastern. Big Iron is counted once as a new project; the relationship count covers SEALSQ–WISeSat, EDGX–NVIDIA and Starcloud–Quindar. Historical backfill and earlier project announcements are excluded.
This week
One new project was announced. Cowboy Space unveiled Big Iron, a rocket whose upper stage is intended to remain in orbit as a megawatt-class AI data center after launch; its first flight is targeted for 2028.
Three supplier engagements were disclosed. SEALSQ signed a letter of intent to acquire WISeSat capacity and operations for its proposed security cloud; closing still depends on definitive agreements. EDGX identified NVIDIA Jetson hardware in its STERNA computers, and Starcloud partnered with Quindar to deploy mission-management software on future orbital infrastructure.
Suncatcher crosses from commissioning into compute
Google said on October 30 that its prototype powered up its Tensor Processing Unit (TPU), ran early machine-learning tests and returned a response generated by the Gemma 4 model during a ground-station pass. The output itself was simple; the useful result is that a data-center-class accelerator, model, spacecraft power system and communications path worked together in orbit.
This advances last week’s watch point: Suncatcher now has a completed workload, not just a healthy spacecraft. Google’s next tests will examine thermal stress and radiation exposure, the conditions that determine whether this can become reliable infrastructure rather than a one-off demonstration.
The surrounding stack is becoming visible
The week’s other announcements sketch the systems around the processor. EDGX reported that one of two STERNA payloads launched in March returned operational data within two weeks, while the second still awaits host commissioning. Quindar’s planned role for Starcloud focuses on telemetry, scheduling and autonomous spacecraft operations. SEALSQ’s letter of intent would add capacity access, ground systems and mission control to its proposed service.
Those layers matter because useful orbital computing depends on more than chips. Power, heat rejection, communications and fleet operations have to function as one service. The evidence is uneven: EDGX’s result is retrospective and does not include a published AI benchmark; Quindar has not yet been deployed on Starcloud; and the SEALSQ transaction is not closed.
A small result changes the evidence more than a large rendering
Suncatcher’s returned answer is modest but observable. It tells readers more about near-term capability than Big Iron’s far larger proposed architecture, because it closes a real loop from uplink to onboard computation to downlink. The market is separating into two paths: small systems processing data where it is collected, and much larger linked data centers. This week strengthened the first path; the second remains mostly design, partnership and schedule.
Reliability and links are the next proof points
Watch for Suncatcher’s thermal and radiation results, then its planned 2027 two-satellite optical-link test; those would show whether compute can remain dependable and work across spacecraft. Also watch for a published STERNA workload result, an on-orbit Quindar deployment, definitive SEALSQ–WISeSat agreements and Cowboy’s promised engine and vehicle tests. Each would convert a different piece of the surrounding stack from intent into measured performance or binding commitment.