Today, a company can build a data centre in one country, operate cloud infrastructure across several jurisdictions and connect users through a global communications network. Orbital computing adds another jurisdictionally complicated layer. A workload could be generated by a satellite operated in one country, processed by computing hardware in orbit owned by a company from another, routed through ground stations elsewhere and ultimately delivered to a terrestrial data centre elsewhere.
This leaves questions about the jurisdiction over data being processed by an orbital computer, which country’s laws apply to a satellite providing cloud services over multiple regions, or who is responsible when a service fails.
Space is already a contested environment. Satellites support communications, navigation, intelligence, surveillance and military operations. States have developed or demonstrated capabilities to interfere with space systems through jamming, cyber operations, dazzling and other forms of disruption. Orbital computing would add another layer of valuable infrastructure to that environment. Its vulnerability would not necessarily come only from an attack on the computing hardware itself.
An orbital cloud revolves around the chain of systems – satellites, software, optical and radio communications, ground stations, terrestrial data centres, power systems and launch infrastructure – and if any part of it is disrupted, whether via physical harm to a satellite or a cyberattack against an orbiting computing platform, the impact cascades. This is where orbital computing deviates from the conventional data centre. An attack on a terrestrial facility is usually limited to an area, but damage in orbit can spread debris, threatening other satellites –including ones owned by states and businesses not involved in the initial disagreement.
The answer should not be to stop the advancement of orbital computing. It has a lot of potential advantages. Reducing communications bottlenecks, facilitating quicker decision-making, and enabling more complex space-based applications are among potential benefits of processing satellite data in orbit.
Governments should not make the mistake of viewing cloud infrastructure in space as solely commercial. Operators should be obliged to reveal basic information about satellite numbers, orbital locations, ownership, manoeuvrability, communications dependencies, and deorbit plans prior to the widespread use of orbital computing networks. Orbital cloud providers should be subject to the same cyber resilience and incident reporting standards as are increasingly being applied to vital terrestrial infrastructure.
More clarity is also required regarding wartime legal status. International law, where possible, ought to differentiate between systems directly supporting military activities and civilian orbital computer infrastructure. In situations when the loss of one computer platform could put unrelated spacecraft in peril, operators should have explicit responsibilities regarding debris mitigation and collision avoidance. Communication during a crisis will be just as crucial. Mechanisms for quickly identifying if an unanticipated orbital occurrence is accidental, technical, or intentional are needed by governments, satellite operators, cloud firms, and space organisations.
Whether orbital computing is technically or financially feasible is no longer the only concern. It is whether the world is prepared for a future in which cloud infrastructure becomes part of contested space infrastructure.