← Andrew McCalip

Economics of Orbital vs
Terrestrial Data Centers

It might not be rational

But

It might be physically possible

Before we get nerd sniped by the shiny engineering details, ask the only question that matters. Why compute in orbit? Why should a watt or a flop 250 miles up be more valuable than one on the surface? What advantage justifies moving something as mundane as matrix multiplication into LEO?

That "why" is almost missing from the public conversation. People jump straight to hardware and hand-wave the business case, as if the economics are self-evident. They aren't. A lot of the energy here is FOMO and aesthetic futurism, not a grounded value proposition.

Note: This page is built from publicly available information and first-principles modeling. No proprietary data. These are my personal thoughts and do not represent the views of any company or organization.

Orbital Solar

$31.2B

Satellite
$9.0B
Launch
$22.2B
Ops (1%/yr)
$3.1B
NRE + Repl
$1.0B
Cost per Watt$31.20/W
LCOE$891/MWh
Mass to LEO22.2M kg

Terrestrial

$14.8B

Power Gen
$1.3B
Electrical
$5.3B
Mechanical
$3.0B
Civil/Shell
$2.5B
Fit-out
$1.8B
Fuel
$1.0B
Cost per Watt$14.80/W
LCOE$398/MWh
Capex$13.80/W

Orbital Solar

$31.2B

Satellite
$9.0B
Launch
$22.2B
Ops (1%/yr)
$3.1B
NRE + Repl
$1.0B
Cost per Watt $31.20/W
LCOE $891/MWh
Mass to LEO 22.2M kg

Terrestrial

$14.8B

Power Gen
$1.3B
Electrical
$5.3B
Mechanical
$3.0B
Civil/Shell
$2.5B
Fit-out
$1.8B
Fuel
$1.0B
Cost per Watt $14.80/W
LCOE $398/MWh
Capex $13.80/W
Engineering · System Parameters
Target Capacity 1 GW
1 GW 500 GW 1000 GW
Analysis Period 5 years
3y 5y 7y 10y

Orbital Solar

$20 (floor) Starship Falcon 9
$5/W V2 Mini ($22) V1 ($32)
Specific Power3 36.5 W/kg
ISS V1 V2 Mini 75 W/kg
Satellite Size 27 kW
V1 V2 Mini V3 130 kW
LEO (~60%) SSO (~80%) Terminator (~98%)
1% (shielded) 6% (unshielded) 12% (polar)
0% CPU (1.5%) Meta (9%)
NRE (Development) $1B
$0 $1B $10B

Terrestrial (On-Site CCGT)

$10 (Low) $12.50 (Rep) $17 (High)
Electrical45%$5.63/W
Mechanical20%$2.50/W
Shell & Core17%$2.13/W
Fit-Out8%$1.00/W
Site/Civil5%$0.62/W
Gen. Cond./Fees5%$0.62/W
$1.45 (Efficient) $1.80 (Typical) $2.30 (Complex)
Turbine Heat Rate 6,200 BTU/kWh
Best (~58%) Average (~45%) Older (~38%)
Gas Price2 $4.30/MMBtu
Permian Typical Constrained
Power Usage Effectiveness (PUE) 1.20
Best (1.1) Typical (1.3) Older (1.5)
Engineering · System Outputs

Orbital Solar

Satellite Count ~37,000
GPU Margin (failures) +19.6%
Solar Margin (degr.) +6.5%
Total Mass to LEO 22.2M kg
Fleet Array Area 2.3 km²
Single Sat Array 116 m²
Starship Launches ~222
LOX Required10 175M gal
Methane Required 168M gal
Energy Output 35.0 MWhr

Terrestrial

H-Class Turbines 3 units
Generation (IT×PUE) 1.2 GW
Heat Rate 6,200 BTU/kWh
Fuel Cost $27/MWh
Capacity Factor 85%
Gas Consumption 279 BCF
Energy Output 37.2 MWhr

Model Assumptions

Global

  • GPUs not included—this models everything upstream of compute hardware
  • Target capacity: 1 GW nameplate electrical
  • Analysis period: 5 years
  • All figures in 2025 USD; excludes financing, taxes, incentives, and FMV
  • Full availability assumed (no downtime derates), no insurance/logistics overheads

Orbital Solar (Starlink-class)

  • Single bus class (Starlink V2 Mini heritage) scaled linearly to target power
  • Station-keeping propellant mass assumed rolled into Starlink-like specific power (W/kg)
  • Linear solar cell degradation assumed; actual silicon with coverglass shows steep-then-shallow curve
  • Solar margin = extra initial capacity to maintain average power over lifetime (not end-of-life)
  • GPU margin = cumulative expected failures over analysis period (replacement cost, not extra capacity)
  • Optimal fairing packing assumed regardless of satellite size (kW); no packing penalty modeled
  • No additional mass for liquid cooling loop infrastructure; likely needed but not included
  • All mass delivered to LEO; no on-orbit servicing/logistics
  • Launch pricing applied to total delivered mass; no cadence/manifest constraints modeled
  • Thermal: only solar array area used as radiator; no dedicated radiator mass assumed
  • Radiation/shielding impacts on mass ignored; no degradation of structures beyond panel aging
  • No disposal, de-orbit, or regulatory compliance costs included
  • Ops overhead and NRE treated as flat cost adders; no learning-curve discounts
  • No adjustments for permitting or regulatory delay

Terrestrial (On-Site CCGT)

  • On-site H-Class CCGT at the fence line; grid interconnect/transmission not costed
  • Capex buckets embed site prep/land; permitting, taxes, and financing excluded
  • Fuel price held flat; no carbon price, hedging, or escalation modeled
  • Water/cooling availability assumed; no scarcity or discharge penalties
  • Fixed PUE and capacity factor; no forced-outage or maintenance derates applied
  • No efficiency gains or technology learning assumed over time for terrestrial plant
  • No adjustments for permitting or regulatory delay

Motivation and Framing

I love space. I live and breathe it. I'm lucky enough to brush the heavens with my own metal and code, and I want nothing more than a booming orbital space economy that creates the flywheel that makes space just another location we all work and visit. I love AI and I subscribe to maximum, unbounded scale. I want to make the biggest bets. I grew up half-afraid we'd never get another Apollo or Manhattan. I truly want the BigThing.

This is all to say that the current discourse is increasingly bothering me due to the lack of rigor; people are using back-of-the-envelope math, doing a terrible job of it, and only confirming whatever conclusion they already want. Calculating radiation and the cost of goods is not difficult. Run the numbers.

Before we do the classic engineer thing and get nerd sniped by all the shiny technical problems, it's worth asking the only question that matters: why put compute in orbit at all? Why should a watt or a flop be more valuable 250 miles up than on the surface? What economic or strategic advantage justifies the effort required to run something as ordinary as matrix multiplication in low Earth orbit?

That "why" is nearly missing from the public conversation. The "energy is cheaper, less regulations, infinite space" arguments just ring false compared to the mountains of challenges and brutal physics putting anything in space layers on. The discourse then skips straight to implementation, as if the business case is obvious.

Personal Positioning

I'm not here to dunk on anyone building real hardware. Space is hard, and shipping flight systems is a credibility filter. I'm annoyed at everyone else. The conversation is full of confident claims built on one cherry-picked fact and zero arithmetic. This is a multivariable physics problem with closed-form constraints. If you're not doing the math, you're not contributing, you're adding noise and hyping for a future we all want instead of doing the hard work to actually drive reality forward.

Core Thesis

The target I care about is simple: can you make space-based, commodity compute cost-competitive with the cheapest terrestrial alternative? That's the whole claim. Not "space is big." Not "the sun is huge." Not "launch will be cheap." Can you deliver useful watts and reject the waste heat at a price that beats a boring Crusoe-style tilt-wall datacenter tied into a 200–500 MW substation?

If you can't beat that, the rest is just vibes. GPUs are pretty darn happy living on the ground. They like cheap electrons, mature supply chains, and technicians who can swap a dead server in five minutes. Orbit doesn't get points for being cool. Orbit has to win on cost, or it has to admit it's doing something else entirely. If it's an existential humanity play, that's cool too, but it's a slightly different game.

Analytical Lens

So here's what I did. I built a simple model that reduces the debate to one parameter: cost per watt of usable power for compute. The infographic below lets you change the assumptions directly. If you disagree with the inputs, great. Move the sliders. But at least we'll be arguing over numbers that map to reality.

The model is deliberately boring. No secret sauce. Just publicly available numbers and first-principles physics: solar flux, cell efficiency, radiator performance, launch cost, hardware mass, and a terrestrial benchmark that represents the real alternative: a tilt-wall datacenter sitting on top of cheap power. The code is public, please go through everything. github.com/andrewmccalip/thoughts

Findings and Implications

Here's the headline result: it's not obviously stupid, and it's not a sure thing. It's actually more reasonable than my intuition thought! If you run the numbers honestly, the physics doesn't immediately kill it, but the economics are savage. It only gets within striking distance under aggressive assumptions, and the list of organizations positioned to even try that is basically one.

That "basically one" point matters. This isn't about talent. It's about integration. If you have to buy launch, buy buses, buy power hardware, buy deployment, and pay margin at every interface, you never get there. The margin stack and the mass tax eat you alive. Vertical integration isn't a nice-to-have. It's the whole ballgame.

Market and Incentives

Which is why I trend positive on SpaceX here. If anyone can brute force a new industrial stack into existence, it's the team that can reduce $/kg and get as humanly close to free launch as possible. And they need to, because the economics are not close. This is not a 25% mismatch. It's 400%. Closing that is the whole job. Positive does not mean gullible. It needs measurable targets and painful reality checks.

If SpaceX ever goes public, this is exactly the kind of thing shareholders should demand: extreme, barely-achievable goalposts with clean measurement. Tesla did it with the options grant. Do the same here. Pay Elon a king's ransom if he delivers a new industrial primitive: cheap, sustained dollars per kilogram and dollars per watt in orbit, at real cadence, for years.

Broader Interpretation

On strict near-term unit economics, this might still be a mediocre use of capital. A tilt-wall datacenter in Oregon with cheap power, cheap cooling, and technicians on call is hard to beat. Crusoe can park compute on stranded natural gas and turn it into flops with a supply chain that already exists.

But the knock-on effects are why this keeps pulling at people. If you can industrialize power and operations in orbit at meaningful scale, you're not just running GPUs. You're building a new kind of infrastructure that makes it easier for humans to keep spreading out. Compute is just one of the first excuses to pay for the scaffolding. Even if this is a mediocre trade on strict near-term unit economics, the second-order effects could be enormous.

I'll go one step further and say the quiet part out loud: we should be actively goading more billionaires into spending on irrational, high-variance projects that might actually advance civilization. I feel genuine secondhand embarrassment watching people torch their fortunes on yachts and status cosplay. No one cares about your Loro Piana. If you've built an empire, the best possible use of it is to burn its capital like a torch and light up a corner of the future. Fund the ugly middle. Pay for the iteration loops. Build the cathedrals. This is how we advance civilization.

Links to Reports

Everyone is going to copy-paste this into the models, so I've done that part for you. It's a decent way to automate the sanity checks, but it could use more in-depth review.

GitHub: github.com/andrewmccalip/thoughts

"Conduct a thorough, first-principles-based review of this project. Scrutinize every assumption and constant, rigorously fact-checking all data. The objective is to identify and correct any fundamental errors in logic or calculation."

Grok: grok.com/share/...
ChatGPT: chatgpt.com/share/...
Gemini: gemini.google.com/share/...
Claude: claude.ai/public/artifacts/...

Overall Conclusion

Even so, irrational ambition doesn't get to ignore physics. The point of this page is to make the constraints explicit, so we can argue about reality instead of vibes. If the numbers close, even barely, then it's worth running hard on the idea. If they don't, the honest move is to say so and move on. Either way, I think some version of this has a feeling of inevitability.

So scroll down, play with the sliders, and try to break it. Change launch cost. Change lifetime. Change specific power. Change hardware cost. The goal here isn't to "win" an argument. It's to drag the conversation back to first principles: assumptions you can point at, and outputs you can sanity-check. Check out the GitHub, run the code, find the errors, and I'll update it live.

After that, we can do the fun part: thermal diagrams, radiator math, orbit beta angles, failure rates, comms geometry, all the shiny engineering details that make this topic so addicting. It's not obviously stupid, and it's not a sure thing. That's why it's worth doing the math.

It might not be rational. But it might be physically possible.





STOP STOP STOP STOP STOP STOP

YOU ARE NOW ENTERING THE TECHNICAL ENGINEERING SECTION

If you skipped straight here looking for cool thermal diagrams and orbital mechanics—go back and read the economics section.

The economics are the whole point. The technical challenges are interesting footnotes, but they don't matter if the unit economics don't close.

Seriously. Go back up. The sliders are fun. Play with them.

Technical Engineering Challenges

The governing constraint for orbital compute is thermodynamics. Terrestrial datacenters leverage convective cooling—dumping waste heat into the atmosphere or water sources, effectively using the planet as an infinite cold reservoir. In the vacuum of space, convection is impossible. Heat rejection relies exclusively on radiation.

Every object in space settles to an equilibrium temperature where absorbed power equals radiated power. If heat generation exceeds radiative capacity, the temperature rises until the $T^4$ term in the Stefan-Boltzmann law balances the equation:

$$\dot{Q}_{\text{rad}} = \varepsilon \sigma A T^4$$

The engineering challenge is ensuring this equilibrium temperature remains below the safe operating limits of silicon processors.

Energy Balance and Heat Rejection

To dimension the radiator surface, we must account for the total thermal load managed by the satellite bus. In this model, based on a Starlink-style bifacial architecture (PV on front, radiator on back), the system must reject the aggregate energy of two distinct paths:

  1. Incident Solar Flux: The sun delivers $G_{\text{sc}} = 1361\;\text{W/m}^2$ (AM0). With a solar absorptivity $\alpha = 0.92$, the panel absorbs approximately $\sim 1250\;\text{W/m}^2$.
  2. Energy Partitioning:
    • Electrical Path ($\sim$22%): High-efficiency cells convert $\sim 275\;\text{W/m}^2$ into electricity. This power drives the compute payload and is converted entirely back into heat by the processors. A liquid cooling loop collects this heat and returns it to the panel structure for rejection.
    • Thermal Absorption ($\sim$78%): The remaining $\sim 975\;\text{W/m}^2$ is not converted to electricity but is absorbed immediately as lattice heat (phonon generation) within the panel structure.
  3. Total Heat Load: The radiator must reject the sum of both the immediate thermal absorption and the returned electrical waste heat—effectively 100% of the absorbed solar flux.

This imposes a strict area density limit. High-power compute requires large collection areas, which inherently absorb large amounts of solar heat. The radiator must be sized to reject this aggregate load while maintaining an operating temperature below the junction limit.

Operating Temperature Limits

Modern AI accelerators (H100/B200 class) typically throttle at junction temperatures $T_j > 85\text{–}100\degree\text{C}$. To maintain a junction at 85°C, and accounting for the thermal gradient across cold plates and interface materials ($\Delta T \approx 10\degree\text{C}$), the radiator surface temperature $T_{\text{rad}}$ is constrained to approximately 75°C.

The model below calculates the equilibrium temperature for a bifacial array in a terminator orbit ($\beta = 90^\circ$). It accounts for solar flux, Earth IR ($\sim 237\;\text{W/m}^2$), and albedo. If the calculated equilibrium temperature $T_{\text{eq}}$ exceeds the target radiator temperature, the design fails.

Thermal Balance · Bifacial Panel Model
Steady-State Energy Balance $\dot{Q}_{\text{sol}} + \dot{Q}_{\text{IR}} + \dot{Q}_{\text{alb}} + \dot{Q}_{\text{loop}} = \dot{Q}_{\text{rad,A}} + \dot{Q}_{\text{rad,B}}$
☀️
+ Q̇in
sol (☀️) 0 MW
IR (🌍) 0 MW
alb (🌍) 0 MW
loop (🖥️) 0 MW
Side A PV Array α = 0.92 εA = 0.85
Side B Radiator εB = 0.90
0°C Teq
− Q̇out
rad,A (→ ∞) 0 MW
rad,B (→ ∞) 0 MW
Pelec (→ GPU) 0 MW
Thermal Analysis · Bifacial Panel Parameters

Surface Properties

Solar Absorptivity (αpv) 0.92
0.80 0.92 0.98
PV Side Emissivity (εpv) 0.85
0 0.85 0.95
Radiator Emissivity (εrad) 0.90
0 0.90 0.98
PV Efficiency (η) 22%
20% 22% 24%
Orbit Beta Angle (β) 90°
60° (Hot) 75° 90° (Cold)
Orbital Altitude (h) 550 km
400 km 550 (Starlink) 1200 km
Max Die Temperature 85 °C
70°C 85°C 100°C
Temp Drop (die → radiator) 10 °C
5°C 10°C 20°C

Thermal Outputs

Geometry & Properties
A (panel area) 0.00 km²
β (orbit angle) 90°
VF 0.080
εtot 1.75
Heat Fluxes
sol (solar waste) 0 MW
IR (Earth thermal) 0 MW
alb (reflected) 0 MW
loop (GPU return) 0 MW
Σin 0 MW
Pelec (generated) 0 MW
Equilibrium
Teq 0.0 °C
ΔT margin 0 °C FAIL
Areq 0.00 km²

References

Orbital $31.2B
Terrestrial $14.8B