Most data centre announcements describe buildings. SpaceX filed a document with the FCC in January 2026 proposing up to one million satellites to do the same job. That document — SAT-LOA-20260108-00016 — is real and you can look it up.
Here’s the interesting tension though: SpaceX’s own S-1 IPO risk disclosures describe orbital data centres as involving “significant technical complexity and unproven technologies.” That gap runs through everything — the FCC filing, the Anthropic deal, the competition, and what it all means when someone at your board table starts asking about it. This is part of our broader look at the alternative computing landscape.
What does SpaceX’s FCC filing SAT-LOA-20260108-00016 actually propose?
SAT-LOA-20260108-00016 was filed by SpaceX in late January 2026 and accepted by the FCC on 4 February 2026. It seeks authorisation to deploy up to 1 million satellites in non-geostationary orbit between 500 and 2,000 km altitude. There’s no dedicated “space data centre” licensing category — this sits within the existing NGSO framework.
That one million figure is a ceiling, not a commitment. Regulatory filings routinely ask for more than operators intend to build. SpaceX’s actual deployment pace will depend on Starship launch economics and commercial demand.
Some scale context. SpaceX’s active Starlink constellation runs to roughly 7,000–10,000 satellites. The filing’s ceiling is a roughly 70-fold increase over the entire current low Earth orbit population — and Ars Technica put the barebones deployment cost at “at least $1 trillion.”
The filing covers infrastructure authorisation only. Per-satellite compute hardware was outlined separately at the AI Sat Mini announcement on 21 March 2026: a satellite carrying 100 kW of power for onboard AI processors. These are complementary documents, not the same plan. The AI Sat Mini’s 100 kW power budget connects to the hardware constraints explored in our NVIDIA Space-1 analysis.
For comparison, Blue Origin filed its own application — SAT-LOA-20260310-00118 — on 19 March 2026 for a 51,600-satellite orbital data centre network called Project Sunrise. That one’s still pending FCC approval as of mid-2026.
Why is SpaceX betting on orbital compute — and what do Grok, Tesla, and Anthropic have to do with it?
SpaceX acquired xAI on 2 February 2026 in an all-stock deal valuing xAI at $250 billion. Grok and Tesla’s autonomous driving AI became the primary internal workloads the whole orbital compute bet is designed to serve.
Elon Musk hasn’t been shy about the strategic logic. At the World Economic Forum in January 2026, he called space-based AI data centres a “no-brainer” and predicted more AI capacity would sit in orbit than on Earth within five years. Those are leadership positioning statements, not operational commitments — and they sit in sharp contrast to what SpaceX put in its SEC filings.
Then in May 2026, Anthropic expressed interest in partnering with SpaceX for multiple gigawatts of orbital AI compute capacity. For context: SpaceX’s entire Starlink constellation produces roughly 200 MW of total power. Gigawatt-scale orbital compute would require five to fifteen times that. Alongside this, Anthropic signed a near-term deal to take the full capacity of SpaceX’s Colossus 1 terrestrial data centre — 222,000+ Nvidia GPUs and 300+ MW of compute — for a reported $15 billion per year.
SpaceX is simultaneously platform provider and major customer. Whether future third-party enterprise customers get priority access or competitive pricing is a practical question that hasn’t been answered. Orbital compute economics are part of the wider alternative infrastructure picture.
Who else is filing for orbital compute — and how does Starcloud compare to SpaceX?
Starcloud (formerly Lumen Orbit) raised a $170 million Series A on 30 March 2026 at a $1.1 billion valuation. Benchmark partner Chetan Puttagunta nailed the investment thesis: “The cost of power on Earth is rising faster than the cost of launch is falling. That crossover is the entire investment case.”
Starcloud plans 88,000 satellites and has positioned itself as infrastructure-for-others from day one. AWS, Nvidia, Crusoe Energy, and the US Department of Defense are early customers. SpaceX is building primarily for Grok and Tesla. Starcloud is the AWS of orbital compute.
The staging tells the economic story. Starcloud-1 launched in November 2025 and ran the first in-orbit LLM training in December 2025. Starcloud-2 (~100 kW, Nvidia Blackwell) is planned for Q4 2026 as the first satellite expected to generate more revenue than it costs to build and launch. Starcloud-3 (3 tonnes, 200 kW) is designed for Starship deployment. Johnston has been direct about the dependency: “Until Starship is flying we can basically tread water launching on Falcon 9.”
Blue Origin’s Project Sunrise proposes 51,600 satellites with FCC approval still pending. Google’s Project Suncatcher plans two test satellites carrying Google TPUs by early 2027. All four players — SpaceX, Starcloud, Blue Origin, Google — share the same structural constraint. Axiom Space’s first commercial orbital nodes represent a different entry point: kW-scale edge compute already operational while SpaceX plans at the million-satellite horizon.
What does SpaceX’s own S-1 filing say about the risks of orbital data centres?
The most interesting counterpoint to SpaceX’s orbital compute ambitions comes from SpaceX itself. The S-1 states directly: “Our initiatives to develop orbital AI compute and in-orbit, lunar, and interplanetary industrialization are in early stages, involve significant technical complexity and unproven technologies, and may not achieve commercial viability.”
Risk disclosures carry legal weight. As The Next Web put it: “The gap between Davos in January and the SEC in April is the gap between a pitch and a prospectus. Both are real. Only one carries legal liability.”
The specific technical risks are real and worth understanding. Radiation causes permanent circuit damage and radiation-hardened chips lag multiple generations behind commercial processors. Hardware cannot be replaced or upgraded once in orbit — operators have a 3–5 year window before the compute is obsolete. Heat rejection is a hard physical constraint: radiating one megawatt at 20 degrees Celsius requires roughly 1,200 square metres of radiator. You can’t negotiate with thermodynamics.
ABI Research estimates that an orbital data centre costs upward of 78 times more than a terrestrial equivalent today. That gap only closes if launch costs fall dramatically, power-per-kg ratios improve, and manufacturing reaches scale — all projected, not current.
How does the Starship dependency define the commercial timeline for orbital compute?
Current Falcon 9 launch costs run approximately $1,400–1,500/kg to LEO. Starship, at scale, is designed to reach $100–500/kg — a 3–14 times reduction that hasn’t been demonstrated yet. Until Starship reaches commercial operational cadence, all orbital compute operators face Falcon 9 economics, and at those prices orbital compute can’t compete with terrestrial hyperscalers.
Starcloud’s staged approach makes the dependency concrete. Falcon 9 launches are proof-of-concept, not commercial economics. Johnston expects commercial Starship access in the “mid- to late-2028 timeframe,” with commercial payloads following 18–24 months after that. Google’s feasibility threshold is $200/kg, projected by the mid-2030s.
The AI Sat Mini signals SpaceX’s near-term hardware approach — a proof-of-concept unit, not a deployment-ready commercial product. There’s also a chip supply dependency: SpaceX’s Terafab project targets 1 terawatt of processors annually — roughly 50 times all current AI chip production. Both are pre-commercial. The energy economics that make orbital compute viable are examined in detail in our orbital solar analysis.
How should your organisation frame SpaceX orbital compute announcements?
SpaceX’s FCC filing and the Anthropic agreement are real signals. They show serious capital and regulatory effort going into orbital compute infrastructure. They are not planning factors for the next 3–5 years for most organisations.
ABI Research identifies the near-term use cases for 2026–2029 as Earth Observation, kW-scale Compute-as-a-Service, and space traffic management. General-purpose enterprise AI workloads are firmly a 2030s conversation.
Here’s what would need to happen for orbital compute to move from watch-list to planning factor: Starship achieving commercial launch cadence, a published enterprise pricing model with contractual SLAs, and at least one regulated-industry customer — SOC 2, HIPAA, FedRAMP — running production workloads with verifiable uptime data. None of these currently exist.
Board questions about SpaceX or Google orbital compute most often reflect investor enthusiasm rather than near-term supply chain risk or competitive displacement. This is a 2030s infrastructure conversation, not a 2026–2028 decision.
What to actually track: Starship commercial launch cadence and per-kg cost announcements, FCC final approval or denial for SAT-LOA-20260108-00016 and SAT-LOA-20260310-00118, and whether any regulated enterprise customer publishes a case study for orbital workloads. That last one is the clearest signal that compliance blockers have been resolved — and right now, no such case study exists.
For a full decision framework on when alternative data centres become a planning factor, see our infrastructure planning guide. The alternative computing landscape continues to attract genuine investment, but in 2026 the question is what to track, not what to act on.
FAQ
What is SAT-LOA-20260108-00016?
SAT-LOA-20260108-00016 is the FCC application filed by SpaceX in late January 2026, accepted by the FCC on 4 February 2026, seeking authorisation to deploy up to 1 million satellites in low Earth orbit for orbital data centre purposes. It sits within the existing non-geostationary satellite orbit (NGSO) licensing framework — no dedicated “space data centre” regulatory category exists. The filing can be searched on the FCC’s International Communications Filing System.
Is the million-satellite figure a commitment or a regulatory ceiling?
It’s a ceiling — the maximum SpaceX is requesting permission to deploy, not a committed launch schedule. Regulatory filings routinely ask for more than operators intend to build to preserve future flexibility. SpaceX’s actual deployment pace depends on Starship launch economics and commercial demand, not FCC approval.
What is SpaceX’s AI Sat Mini and how does it relate to the FCC filing?
The AI Sat Mini is SpaceX’s proposed initial orbital compute satellite, outlined on 21 March 2026. It’s designed to carry 100 kW of power for onboard AI processors. The FCC filing covers the broader constellation authorisation; the AI Sat Mini describes the hardware approach. They’re complementary documents covering different layers of the same plan.
Did Anthropic sign a contract with SpaceX for orbital compute?
No. The May 2026 development is a compute agreement indicating Anthropic’s interest in partnering with SpaceX for multiple gigawatts of orbital AI compute capacity. It’s a demand signal and expression of intent, not a binding commercial contract.
How does SpaceX’s approach differ from Starcloud’s?
SpaceX’s orbital compute plan is internal-first — primarily serving Grok (xAI) and Tesla workloads, with external customers secondary. Starcloud is infrastructure-for-others from day one, with AWS, Nvidia, Crusoe Energy, and the US DoD as early customers. SpaceX plans up to 1 million satellites; Starcloud plans 88,000. Both share a Starship dependency for commercial unit economics.
What are the main technical risks SpaceX itself has acknowledged?
SpaceX’s S-1 IPO risk disclosures identify: significant technical complexity and unproven technologies; the unpredictable space environment making commercial viability uncertain; radiation effects that corrupt hardware; and the inability to upgrade or replace hardware once it’s in orbit. These are material risk disclosures that carry legal weight as investor information.
Why does the Starship launch cost matter so much for orbital compute economics?
Current Falcon 9 launch costs are approximately $1,400/kg to LEO. Starship, at scale, is projected to bring that down to $100–500/kg — a 3–14 times reduction. ABI Research estimates orbital data centres cost upward of 78 times more than terrestrial equivalents today. That gap only closes if launch costs fall dramatically. Google’s feasibility threshold is $200/kg, projected around 2035.
Should I include orbital compute in my infrastructure planning for the next 3 years?
For most organisations, orbital compute is a watch-list item, not a planning factor, for 2026–2029. The evidence for putting it on the watch list is strong: $3 billion-plus in ODC ecosystem funding, credible operators, real FCC filings, and the Anthropic demand signal. The evidence for making it an active planning factor isn’t there yet: no commercial enterprise SLAs exist, no regulated-industry workload case studies have been published, and Starship launch economics remain a 2028–2030 prospect at best.
