The ground is the constraint
Strip the building away and a hyperscale facility is two flows. Energy in, heat out. Everything else is plumbing. Both flows are getting harder to serve. Grid interconnect queues in the major markets are measured in years; new generation is gated on transmission that takes longer to permit than to build. Cooling at density has pushed past air, past water, into closed liquid loops that draw potable water at a scale that is now a siting liability. The next generation of training clusters is quoted in hundreds of megawatts, then gigawatts. There is no version of the current trajectory that the existing build-out absorbs quietly.
Consider the four binding constraints. Power is drawn from a grid that must be generated, transmitted, and permitted: contested and slow. Heat is rejected into air or water, both finite, both warm, both shared with everyone else, and the sink is never actually cold. Land must be continuous, zoned, and served by road, fiber, and substation, scarce precisely where power already is. Water is increasingly the first thing a community refuses to give. Each of these is a local accident of the surface. None is a law of computing.
These limits feel fundamental because they have always been present. They are not fundamental. They are properties of building on the ground. Move the same two flows off the surface and the constraint set does not merely loosen. It inverts.
The inversion
In the right orbit, sunlight arrives at roughly 1.36 kilowatts per square meter, continuous, with no atmosphere in the way and no night to design around. There is no land to acquire and no water to draw. The heat sink is the entire sky: deep space sits near 3 kelvin, the coldest reservoir physically available anywhere. The terrestrial constraints do not get easier. They are gone.
What replaces them is smaller and far harder. Heat must be rejected by radiation alone, with no air and no water to carry it off, which makes the radiator the largest structure on the platform and thermal design the discipline the whole system is built around. Power must be generated where it is used, densely, without depending on collecting area. Both are severe problems. Neither is a reason the thesis fails. They are the reason it is a company; easy problems do not need one. The only constraint that was ever truly decisive, the cost of reaching orbit, is the one now collapsing, by roughly an order of magnitude per launch generation.
This is why "data centers in space" is the wrong picture. Nobody is lifting a server rack to orbit for its own sake. The object being built is a power and thermal platform, and the compute is its payload: the densest, most portable, most valuable load it could carry. Get the platform right and the payload is almost incidental. The inversion, from a computer that happens to be in space to a power station that happens to compute, is the whole idea.
The crossover
The physics was never the question. It works. The question is timing, and timing is set by two costs moving toward each other. The first is the price of putting a watt of generation, and the radiator to match it, into orbit. It falls every time launch gets cheaper, and launch is the fastest-falling cost curve in the industry. The second is the price of a marginal watt of compute on the ground. It rises every year, pushed up by interconnect queues measured in years, by water and land that communities increasingly refuse, and by carbon that is finally being priced in rather than ignored.
For now the ground is far cheaper, and for most workloads it stays that way for a long time. But the curves are pointed at each other, and only one of them is under anyone's control. The moment they cross, for even the largest and most power-hungry class of compute, the next unit is cheaper built above the atmosphere than below it. Nothing about that moment is a vision or a launch announcement. It is a line item. It is procurement.
Posture
The work is early and deliberate. The architecture is not described here, and will not be until there is reason to. There is no team to introduce and no roadmap to publish. What is written above is the position. What is being built to meet it is the company.