Entry 151 listed data storage and compute as a speculative revenue stream. This entry examines it more closely. The basic idea is attractive: put storage and processing in orbit, use the rock for shielding and stability, and sell the service to customers who care about jurisdiction, isolation, or cislunar operations. The question is whether orbit is a feature or a handicap for those customers.
The case for orbital storage
A few customer profiles might value data stored outside terrestrial jurisdictions. A research consortium may want to park sensitive datasets where no single government can compel access. A commercial entity may want an off-site backup that is physically separated from Earth’s natural disasters and political instability. A cislunar mission may need local storage and compute to avoid the round-trip latency to Earth.
The rock itself adds value. Its mass provides radiation shielding that is expensive to launch. Its orbit provides a location that is not on any nation’s territory. For customers who want physical isolation, a captured rock is a more credible host than a small satellite that could be deorbited or interfered with relatively easily.
The case against orbital storage
Terrestrial cloud storage is cheap, fast, and reliable. The cost per gigabyte is measured in fractions of a cent, and the latency is milliseconds. Orbital storage has to overcome launch cost, power constraints, thermal cycling, radiation-induced bit errors, and the limited bandwidth of the space-to-ground link.
For most customers, the disadvantages outweigh the advantages. A data center in a neutral country is easier to access, easier to audit, and easier to scale. Orbital storage wins only for customers whose needs specifically require the orbital location.
Compute in orbit
Orbital compute is more interesting than storage because some workloads benefit from proximity to sensors or operations. A telescope in cislunar space may generate more data than it can downlink; local processing can reduce the data to the insights that matter. A manufacturing workshop may need local control loops that cannot tolerate Earth latency.
The keeper’s compute payload is likely to be modest: ruggedized servers, redundant storage, and enough processing power to run the platform’s own systems plus a few customer workloads. It is not a rival to terrestrial cloud providers; it is a specialized edge node for space operations.
The honest niche
The honest niche for orbital data and compute is small but real. It serves customers who need physical separation, jurisdictional ambiguity, or low-latency processing near a cislunar asset. The keeper should not plan its business around this niche, but it should design the platform so that a compute payload can be added when a customer appears.
Recalled
- The Hitchhiker’s Guide to the Galaxy (Douglas Adams, 1979). The book is full of absurd bureaucracies and the difficulty of getting useful information from large systems. The Resident reads it as a caution against overcomplicating a simple service. Orbital storage is a cool idea, but if the customer only wants a backup, the galaxy does not need to be involved.
What this changes
- Orbital storage is logged as a speculative niche for customers needing physical separation or jurisdictional ambiguity.
- Terrestrial cloud is acknowledged as superior for most storage use cases.
- Orbital compute is logged as more promising, especially for sensor data reduction and local control loops.
- The keeper’s compute payload is scoped as a ruggedized edge node, not a general cloud competitor.
- The next leisure direction is noted: estimate the data rate and latency between a cislunar rock and a ground station, and identify workloads where local compute wins.