Start neutral
Both columns start with the same hardware and electrical load. Equal useful output is a baseline assumption, not evidence that orbit performs equally well.
Compare two alternative locations for the same AI hardware — not two fleets growing together.
IT capacity and the Advanced assumptions below. Workload-specific performance has not been measured.
These examples explain what to investigate. They do not change the estimates: there is no verified workload benchmark behind this model.
Independent batch inference: independent requests can be grouped. Communication losses still need measurement; no numeric advantage is assumed.
Interactive inference: response time and ground-link availability matter. Annual throughput does not predict latency or service-level compliance.
Closely coupled training: frequent accelerator exchanges make networking critical. A simple multiplier does not establish whether a training job can run at all.
For a specific workload, enter measured relative efficiency, availability and communication losses under Advanced assumptions. Without those measurements, treat the numbers as scenarios.
All starting numbers are neutral or illustrative. There are no automatic workload-specific performance factors. For real predictions, replace them with measured values for the same model, quality target and hardware.
Installed IT electrical capacity
The same installed IT electrical capacity
No total-cost winner: launch and electricity omit different major costs. Default $200/kg launch is an optimistic future assumption.
Reference units model annual useful work, not real buildings or global compute share. Energy percentages use the IEA’s 950 TWh/year 2030 benchmark.
One reference unit means the annual useful output of hypothetical 100 MW IT hardware on Earth, at full electrical load, 100% service availability, and the same workload and hardware. It is not the output of a named data center, a count of existing buildings, or a share of global AI computing.
This is normalized output, not tokens/second. Orbital efficiency × availability × communication retention is applied once. The same average electrical load applies to both alternatives. The model assumes useful output scales linearly with average electrical draw; real low-load processor behavior may differ. Output penalties do not automatically save electricity: idle, unavailable or failed work may still consume power.
The IEA projects 950 TWh of annual data-center facility electricity in 2030. This fixed benchmark puts energy in context; it is not global compute capacity.
Bars stop at 100%; numerical values remain uncapped.
Neither percentage predicts demand displaced on Earth. Orbital computing could serve new demand instead. The space numerator excludes spacecraft overhead; the Earth numerator includes facility overhead.
No total-cost winner is calculated.
Space costs omitted: spacecraft and chips, communications, ground stations, operations, financing, insurance, failures, spares and disposal. Earth costs omitted: construction, chips, land, grid connections, maintenance and financing. Manufacturing, launch and reentry also have environmental impacts.
Let L = average electrical load / 100, and F = (orbital efficiency / 100) × (availability / 100) × (1 − communication loss / 100). Earth reference units = installed GW × 10 × L. Space equivalent units = Earth reference units × F. The full-load Earth IT power that matches this modeled orbital output = installed GW × L × F.
Annual IT energy (TWh) = installed GW × 8.76 × L. Annual Earth facility energy = IT energy × PUE. Launched mass = installed GW × 1,000,000 × kg/kW. Annualized launch expense = mass × $/kg / useful years. Annual Earth electricity expense = facility TWh × 1,000,000,000 × $/kWh. Straight-line annualization, no financing, inflation or cost of capital.
Availability loss describes unavailable service time; communication loss applies only during remaining available time. Do not count the same failure in both. Reliability and networking assumptions change useful output, not installed mass. At zero load there is no modeled useful output, but installed hardware still has a launch cost.
Both columns start with the same hardware and electrical load. Equal useful output is a baseline assumption, not evidence that orbit performs equally well.
Try 90% service availability and 10% communication loss. Together they retain 81% of useful work, not 80%, because the second loss applies to the remaining work.
For a real comparison, measure the same workload, model quality, hardware, power, recovery time and completed useful work. Peak chip performance alone is insufficient.
Google explores tightly linked TPU spacecraft; SpaceX’s AI1 concept emphasizes localized computing linked through Starlink. Networking demands depend on workload. Radiators, radiation-related errors, storm-driven drag, collision avoidance, safe disposal, cyberattacks and interrupted ground or launch access affect the outcome. No operational-fleet cost advantage is assumed.
Sources checked October 30, 2026. No workload-specific benchmark is supplied. All performance modifiers are user-selected assumptions. The reference Earth system is idealized; a measured Earth baseline may also have downtime and networking losses.