01. The Cloud
Also known as someone else's computer. This book will discuss
01. Datacenters
02. Space Datacenters
1. Why ?
1. Terrestial Energy shortage/queues
2. Solar power efficiency
Space offers near-continuous solar power at roughly 1,361 W/m² at the top of atmosphere — 5x to 10x more usable flux than the best terrestrial sites — along with free radiative cooling and zero water consumption.
Philip Johnston: Most orbits aren’t suitable because satellites spend roughly half their time behind Earth’s shadow, which would require batteries, similar to the challenge of harnessing solar power on Earth.
We use a specific orbit called a dawn–dusk sun-synchronous orbit. In this approach, the satellite essentially follows the Earth’s terminator line and remains in continuous sunlight. That eliminates the need for large-scale energy storage and creates a highly stable power environment, arguably more stable than on Earth, since you don’t have weather, humidity, or other environmental variability.
So if a sun-synchronous orbit is configured properly, the satellite would theoretically never enter Earth's shadow, and batteries wouldn't be necessary to compensate for darkness during half the orbit—which is exactly your point.
The skeptics' argument about needing batteries for the "no sunlight half" of the orbit doesn't actually apply to sun-synchronous orbits in the way it would for a standard circular orbit around Earth's equator. A sun-synchronous orbit solves that specific problem.
3. Community opposition of new data centers
2. Optimists
1. Starcloud
Source: The case for data centers in space (May 8, 2026)
3. Challenges
TLDR: The more corporations that want own space the more satellites we will have in space
-
If multiple companies (Starcloud, SpaceX, Amazon Kuiper, Google, and potentially others) all launch massive satellite constellations for space-based computing/data processing, you're looking at potentially hundreds of thousands of satellites in low Earth orbit (LEO).
-
This creates several real problems:
- Orbital debris and collision risk: More satellites = higher collision probability = more debris = Kessler syndrome risk
- Spectrum congestion: Limited radio frequencies for inter-satellite links, satellite-to-ground comms
- Orbital slot congestion: Certain orbital altitudes (especially 600-1200 km LEO) are getting crowded
- Regulatory/coordination issues: Who manages all this? International Space Agency? National governments?
- End-of-life management: What happens when these satellites deorbit after 5-15 years?
-
This is actually a legitimate criticism that skeptics SHOULD be raising more about space-based compute. It's not just about the thermodynamics or cost - it's about whether we can actually have multiple mega-constellations operating simultaneously without creating a debris catastrophe.
-
The user is right to flag this. This is a "tragedy of the commons" problem - each company individually pursuing orbital infrastructure makes sense economically, but collectively they could make LEO unworkable.
I should:
- Validate this concern as legitimate and under-discussed
- Explain the specific orbital congestion/debris issues
- Discuss Kessler syndrome risk
- Note that this IS a serious bottleneck that skeptics should emphasize more
- Mention regulatory frameworks (or lack thereof)
- Discuss what happens to decommissioned satellitesYou've identified a critical and under-discussed problem that skeptics should emphasize far more than they do. The orbital congestion nightmare is arguably a bigger show-stopper than thermodynamics or cost.
The Kessler Syndrome Risk
If Starcloud, Amazon Kuiper, Google, SpaceX, and others all launch mega-constellations simultaneously, Low Earth Orbit (LEO) becomes a debris minefield.
Currently, there are roughly 8,000 active satellites in orbit. Starcloud alone plans 88,000. Amazon Kuiper is targeting 3,200+ satellites. SpaceX's Starlink already has ~7,000+. If each of these companies adds 50,000+ satellites for orbital computing purposes, you're looking at 200,000+ objects in the most valuable orbital zones (600-1200 km altitude).
The physics is brutal: higher satellite density exponentially increases collision probability. One major collision creates thousands of debris fragments, each traveling at 25,000 km/h. Those fragments then collide with other satellites, creating more debris in a cascading chain reaction—Kessler Syndrome. Once triggered, it renders entire orbital zones unusable for decades.
Spectrum and Bandwidth Gridlock
Orbital communications are already fighting for radio spectrum. Inter-satellite links, satellite-to-ground uplinks, ground-to-satellite downlinks—they all share limited frequency bands (Ku, Ka, mmWave).
If 200,000 satellites are simultaneously trying to transmit AI inference data, satellite telemetry, and command signals, spectrum becomes the hard bottleneck, not physics. The FCC and ITU have limited spectrum allocation, and they're already struggling to coordinate Starlink, Kuiper, and Chinese megaconstellations. Adding orbital datacenters on top makes coordination nearly impossible.
Regulatory Chaos
There is no global coordination mechanism for this. The Outer Space Treaty (1967) says no nation can claim space, but it doesn't address:
- Who approves mega-constellations when they overlap?
- What happens when debris from one company's satellites damages another company's hardware?
- How long can dead satellites remain in orbit before forced deorbit?
- Who pays for active debris removal?
Currently, there's a gentlemen's agreement that satellites should deorbit within 25 years. But:
- Not all nations follow this rule
- 25 years means 88,000 Starcloud satellites would persist until ~2050+
- If each satellite fails earlier (solar panels degrade, electronics fail), they become uncontrolled debris
The End-of-Life Nightmare
Each satellite in Starcloud's constellation has a lifespan of ~5-15 years. That means:
- Every 5-10 years, thousands of decommissioned satellites must be deorbited simultaneously
- If deorbit burns fail (rocket misfires, computer glitches), the satellite becomes debris
- Managing the continuous recycling of a 88,000-satellite constellation is an unprecedented operational challenge
- One major failure cascade could disable the entire constellation mid-service
Why Skeptics Underemphasize This
Honestly, orbital congestion is the strongest argument against space-based AI compute, but it's politically sensitive. Raising it too loudly makes you sound like you're opposing the entire space economy—which companies like SpaceX, Amazon, and Google actively lobby against through industry groups and regulatory capture.
It's easier for skeptics to stick with thermodynamics and cost arguments (which sound technical and neutral) than to say: "This entire vision requires assuming the space industry will magically solve coordination and regulation problems that they've actively avoided solving for the past 15 years."
What Would Actually Need to Happen
For 200,000+ orbital satellites to coexist safely:
- International binding agreement on constellation size, orbital altitude zones, and operational standards (currently doesn't exist)
- Mandatory active debris removal systems on every satellite (expensive, adds weight)
- Real-time collision avoidance network tracking every object to sub-meter precision (technically possible, organizationally hard)
- Severe financial penalties for nations/companies that create uncontrolled debris
- Spectrum sharing standards that actually prevent interference (technically solvable, politically unsolved)
None of these coordination mechanisms exist or are being built. Companies are racing to launch first and ask forgiveness later—a tragedy-of-the-commons dynamic.
You're right: orbital congestion might kill space-based AI compute long before cost or thermodynamics does. It's the coordination failure problem, not the engineering problem.