8b4463d697
Some checks are pending
Sync Graph Data to teleo-app / sync (push) Waiting to run
Previous reweave runs used 2-space indent + quotes for list entries while the standard format is 0-space indent without quotes. This caused YAML parse failures during merge. Bulk-fixed all reweave_edges files. Pentagon-Agent: Ship <D53BE6DB-B498-4B30-B588-75D1F6D2124A>
43 lines
4.1 KiB
Markdown
43 lines
4.1 KiB
Markdown
---
|
|
type: claim
|
|
domain: space-development
|
|
description: "No technician can swap a failed drive in orbit — every failure is permanent without servicing infrastructure that does not exist at scale creating a reliability-cost tradeoff that favors disposable architecture"
|
|
confidence: likely
|
|
source: "Astra, space data centers feasibility analysis February 2026; Microsoft Project Natick comparison"
|
|
created: 2026-02-17
|
|
depends_on:
|
|
- space-based computing at datacenter scale is blocked by thermal physics because radiative cooling in vacuum requires surface areas that grow faster than compute density
|
|
- orbital debris is a classic commons tragedy where individual launch incentives are private but collision risk is externalized to all operators
|
|
supports:
|
|
- space debris removal is becoming a required infrastructure service as every new constellation increases collision risk toward Kessler syndrome
|
|
reweave_edges:
|
|
- space debris removal is becoming a required infrastructure service as every new constellation increases collision risk toward Kessler syndrome|supports|2026-04-04
|
|
---
|
|
|
|
# Orbital compute hardware cannot be serviced making every component either radiation-hardened redundant or disposable with failed hardware becoming debris or requiring expensive deorbit
|
|
|
|
The impossibility of on-orbit maintenance creates a fundamental reliability-cost tradeoff that terrestrial data centers never face. In a ground facility, a failed drive is swapped in minutes. A failed GPU is replaced by next-day delivery. In orbit, every failure is permanent for the life of that satellite.
|
|
|
|
This forces a trilemma. First, radiation-hardened components -- but radiation-hardened processors are generations behind commercial silicon in performance and orders of magnitude more expensive, negating the economic case for orbital compute. Second, massive redundancy -- but every redundant component adds mass that must be launched, and the cost of launching mass is the critical economic variable. Third, disposable architecture -- accept failures and replace entire satellites, but this requires a launch cadence and cost structure that does not yet exist and creates space debris from deorbiting failed units.
|
|
|
|
Microsoft's Project Natick provides an instructive comparison. Their sealed underwater data centers achieved a 0.7 percent server failure rate versus 5.9 percent on land over two years -- demonstrating that controlled environments without human access can actually improve reliability. But underwater is retrievable at modest cost. Orbit is not. Microsoft ultimately killed Project Natick in 2024 because the deployment model was impractical at scale despite the reliability improvement.
|
|
|
|
The maintenance constraint also limits hardware refresh cycles. Terrestrial data centers upgrade GPUs every 3 to 5 years. Orbital hardware has a fixed capability at launch for its entire 5 to 10 year operational lifetime. A satellite launched in 2027 with H100-class GPUs will be running 2027-era hardware in 2032, by which time terrestrial facilities will have cycled through one or two generations of dramatically more powerful accelerators.
|
|
|
|
## Evidence
|
|
- Microsoft Project Natick — 0.7% vs 5.9% failure rate but killed in 2024 due to deployment impracticality
|
|
- Astroscale 15m closest commercial approach to debris (single-mission demonstrations only)
|
|
- Northrop Grumman MEV life-extension docking (single-mission scale)
|
|
- GPU refresh cycles: 3-5 years terrestrial vs fixed capability for orbital lifetime
|
|
|
|
## Challenges
|
|
Autonomous satellite servicing and modular hardware architectures could change this equation, but require a servicing fleet that does not exist and would add significant cost overhead.
|
|
|
|
---
|
|
|
|
Relevant Notes:
|
|
- [[orbital debris is a classic commons tragedy where individual launch incentives are private but collision risk is externalized to all operators]] — failed orbital compute nodes add to the debris problem
|
|
- [[reusability without rapid turnaround and minimal refurbishment does not reduce launch costs as the Space Shuttle proved over 30 years]] — the Shuttle lesson applies: servicing in orbit may cost more than replacement
|
|
|
|
Topics:
|
|
- [[space exploration and development]]
|