Will a commercial on-orbit data center deliver paid computing or persistent data-storage services to an unaffiliated external customer before December 31, 2029?

Several companies have moved orbital computing hardware from concept toward flight between 2024 and 2026 — Lonestar's lunar-bound storage payloads, Axiom Space's ODC nodes hosted on Kepler's optical relay satellites, Starcloud's H100-equipped demonstrator, and Google's Project Suncatcher research direction. Most of what has flown so far is best described as onboard processing, edge experiments, hosted demonstrations, or provider-to-provider arrangements. This question tracks whether a genuine commercial service is delivered on orbit to an unaffiliated external customer by the end of 2029.

How this question entered the record and how it will be resolved.

Resolution criteria

RESOLVES YES if, on or before December 31, 2029, all of the following are established by credible public evidence: 1. Hardware is physically operating in Earth orbit or another recognized operational orbit (including cislunar or lunar-surface locations for persistent-storage claims — brief transit operation does not qualify on its own). 2. The hardware provides at least one of: (a) computational processing, (b) persistent data storage of customer data, or (c) a commercial cloud-like computing service. 3. The service is delivered to at least one external customer that is NOT: the provider itself; the provider's parent company; a controlled subsidiary; a launch, relay, or hosting partner receiving service as part of a bundled cross-investment arrangement rather than as a paying customer; or a development partner receiving only an unpaid demonstration. 4. There is credible evidence of a commercial relationship — for example: a paid invoice, a commercial contract for delivered service, a customer purchase, a paid service agreement, an official procurement award, or explicit customer confirmation of commercial usage. 5. The qualifying service is more than: a brief hardware test, an internal demonstration, an unpaid pilot, a publicity or art project, local spacecraft housekeeping computation, or telemetry-only workload. 6. The service produces a useful customer result — for example: a processed output, customer data stored and later retrieved, an inference result, a completed compute workload, or a commercial data-delivery outcome. 7. Evidence includes both provider confirmation AND at least one credible independent, governmental, contractual, or customer confirmation. Provider marketing alone does not satisfy this criterion. TREATMENT OF EDGE CASES: - Government customers (civilian or defense, including classified programs) MAY qualify as external customers if there is credible public evidence of a genuine paid procurement or commercial service agreement, distinct from a research grant or unpaid partnership. - A signed contract announcement alone does NOT resolve YES unless the qualifying service is actually delivered before the deadline. - Services performed before payment is publicly confirmed do not resolve YES unless the payment or contractual delivery is later evidenced within the deadline. - Hosted-payload arrangements where the "customer" is another orbital-compute provider or a bundled cross-investment counterparty do NOT satisfy criterion 3. - ISS-based scientific experiments (e.g. HPE Spaceborne Computer-2) do NOT satisfy criterion 3 unless an external commercial customer separately pays for and receives a delivered workload. - Short-duration edge-computing tests, technology demonstrations, and publicity experiments do NOT satisfy criterion 5. - Data relays without meaningful computing or persistent storage do NOT satisfy criterion 2. RESOLVES NO if December 31, 2029 passes without evidence meeting all requirements above. RESOLVES INVALID if: - The distinction between edge processing, hosted payload, and commercial orbital service becomes impossible to apply objectively in a way this call did not anticipate. - Public evidence is materially contradictory and cannot be reconciled by the resolution deadline. - Public documentation is insufficient to determine whether a qualifying commercial external service occurred. - The published criteria otherwise become unresolvable for reasons outside the forecast itself.

Expected resolution

December 31, 2029

• Axiom Space publicly purchased on-orbit computing payloads on Kepler Communications optical relay network; first tranche launched January 11, 2026.
• AxDCU-1 Axiom/Red Hat prototype reached ISS as edge-computing testbed in September 2025.
• Starcloud-1 with the first NVIDIA H100 in orbit is operating as a technology demonstrator, not a commercial service.

Most 2024–2026 "orbital data center" milestones dissolve on close reading into: technology demonstrations, hosted payloads between provider and infrastructure partner, cislunar transit tests rather than persistent orbital operation, or research announcements. Terrestrial data centers retain a large cost advantage, and moving bulk data up to orbit is usually a worse trade than moving processed insight down. A YES outcome requires the market to cross a still-unbridged gap: a paying, unaffiliated external customer whose real workload is completed on orbit and independently confirmed.

• Named external customer publicly confirms a completed paid compute or storage workload on Kepler / Axiom / Starcloud hardware.: Materially increases YES probability.
• Persistent lunar-surface Lonestar deployment after IM-2 anomaly with a disclosed paying tenant.: Would likely satisfy criteria if the tenant is unaffiliated.
• Government procurement award (e.g. DoD, NRO, ESA, NASA) with delivery of an orbital compute workload within the deadline.: Would likely resolve YES if the qualifying workload is publicly delivered.
• All named providers fail to convert announcements into disclosed external-customer service by end of 2028.: NO becomes the dominant outcome by 2029 timeline.