Nate Jones’s recent characterisation of orbital data centres as a purely speculative “debate-stage proposal” understates activity already underway in low Earth orbit and the concrete steps several firms are taking to test , and soon commercialise , compute in space. According to the original report supplied by NextBigFuture, Starcloud and partners have already placed Nvidia hardware on orbit and are moving rapidly from single-satellite experiments toward larger, revenue-facing deployments. [1][2]
In November 2025 Starcloud launched Starcloud‑1, a 60 kg test satellite that carries an Nvidia H100 GPU and is currently operating in orbit. The mission was explicitly framed as a technology demonstration with a limited on‑orbit lifetime, designed to validate the basic premise that high‑performance AI chips can function in the space environment. Industry reporting describes Starcloud‑1 as a proof of concept that could inform far larger designs , including proposals for multi‑megawatt, solar‑powered “data centre” satellites. [2]
That private test dovetails with announced industry partnerships. Crusoe, a cloud infrastructure operator, plans to deploy its cloud platform on a Starcloud follow‑on satellite slated for launch in late 2026 and expects to offer limited GPU capacity from orbit as early as 2027. Crusoe’s engagement illustrates the move from single‑chip experiments to commercial offerings that combine space‑native hardware with cloud service models familiar to terrestrial customers. The company has publicly positioned the work as an incremental roll‑out: test payloads first, limited capacity afterwards, with scale contingent on test outcomes. [3]
Google is pursuing a parallel path. Project Suncatcher, described in company materials as a research “moonshot”, proposes deploying Tensor Processing Units (TPUs) in fleets of small satellites and includes a planned partnership with Planet Labs to launch two prototype satellites by early 2027. Google’s public summary frames the programme as an engineering exploration , focusing on inter‑satellite communications, formation control, thermal management, radiation tolerance and the economics of launch and scale , rather than an immediate commercial roll‑out. [4]
Radiation tolerance and memory integrity have been singled out by technical teams as key constraints. Ground proton‑beam testing of Google's V6e Trillium Cloud TPU and associated host systems was performed to emulate the sun‑synchronous low‑Earth orbital environment; those tests indicate the highest sensitivity is in High Bandwidth Memory (HBM) subsystems, where total ionising dose produces uncorrectable ECC events at measurable rates. Shielding and architectural mitigation can reduce error rates to levels that industry sources judge acceptable for inference workloads, but the same error characteristics present a steeper challenge for large‑scale training jobs. Those distinctions inform why many current programmes aim first at inference and caching use cases. [1][4]
Communications and integration with existing satellite constellations are another practical focus. Rather than supplanting radio‑frequency links, most published plans envision compute‑bearing satellites operating as part of a mixed architecture: localised compute nodes in orbit that can exchange data via existing Ku/Ka/S‑band links or via laser inter‑satellite links with relay constellations. Project Suncatcher and the Starcloud proposals both contemplate tightly coordinated formations and high‑bandwidth inter‑satellite networking to support distributed workloads and to avoid duplicating ground‑station infrastructure. [1][4]
Regulatory and launch‑scale logistics remain decisive variables. Modifying satellite payloads, increasing on‑board power, or changing electromagnetic emissions typically require filings with national regulators; in the United States that means amendments or new applications to the FCC and associated public comment periods. Industry observers note these reviews can range from months for minor payload changes to a year or more for major technical or spectrum modifications. Similarly, the cost curve for mass deployment is sensitive to the pace of launch‑vehicle reusability and the economics of high‑volume manufacturing in space. Those constraints will determine whether orbital compute remains an experimental niche or becomes a broadly available service. [1]
Taken together, the available evidence suggests orbital AI compute is moving from conceptual debate into staged demonstration and early commercial experiments. Starcloud‑1’s in‑orbit H100, Crusoe’s announced deployment plans for 2026/27, and Google’s prototype ambitions under Project Suncatcher all point to near‑term trials focused on inference, caching and special‑purpose workloads, with larger scale ambitions contingent on successful radiation‑management strategies, regulatory clearances, and continued reductions in launch cost. Industry data shows these steps are deliberate: experiments first, limited commercial services next, and only then a possible transition to terawatt‑scale visions. [2][3][4][1]
##Reference Map:
- [1] (NextBigFuture) - Paragraph 1, Paragraph 5, Paragraph 6, Paragraph 7, Paragraph 8
- [2] (DataCenterDynamics) - Paragraph 2, Paragraph 8
- [3] (DataCenterDynamics) - Paragraph 3, Paragraph 8
- [4] (DataCenterDynamics) - Paragraph 4, Paragraph 5, Paragraph 6, Paragraph 8
Source: Noah Wire Services