Putting solar power and data centers in orbit sidesteps night, weather, and land — but adds launch mass and thermal challenges. This planner sizes an orbital solar-plus-compute installation: power collected, compute supported, mass, and the flights to build it.
It's for reasoning about space-based solar power and orbital compute as one integrated facility.
Orbital arrays enjoy near-continuous sunlight, so collected power per unit area is high, but thermal rejection and mass constrain how much compute you can run. The planner balances generation against the load and converts the hardware into a flight manifest.
It shows the appeal and the catch of orbital compute: abundant power and no night, paid for with launch mass and heat rejection — the trade that cheaper launch keeps shifting toward feasibility.
Sizing an orbital data center to a target compute load reveals both the generous solar it can collect and the dozens of flights its mass implies — quantifying why orbital compute waits on cheaper heavy lift.
Continuous sunlight and no land or weather constraints — at the cost of launch mass and cooling.
Thermal rejection and mass, more than power availability.
The planner computes it from total mass and per-flight payload.
No — a first-order planning estimate with open assumptions.
Yes — 25 languages, browser-based.