Who Owns the Power, Data, and Orbits?

Part 29 of 30 · Series date: September 8, 2026

Distance from Earth does not remove ownership, obligations, customer dependence, or the need for trustworthy rules.

A satellite crosses above several countries while serving customers in several more. Its owner is incorporated in one place, its ground stations are elsewhere, and its processors may hold sensitive data. Which rules follow it?

“It is in space” does not mean “no one has jurisdiction.” Orbital infrastructure brings legal and governance questions into a new setting rather than making them disappear.

The international foundation

The Outer Space Treaty prohibits national appropriation of outer space and celestial bodies. It assigns states international responsibility for national space activities, including those of nongovernmental entities, which require authorization and continuing supervision. It also addresses liability, jurisdiction over registered space objects, due regard, and potentially harmful interference. These principles are a framework, not a complete licensing code for every commercial service. United Nations Treaty Series: Outer Space Treaty, Articles II and VI–IX.

A company's ownership of hardware is different from sovereignty over the region through which it travels. Likewise, a treaty principle does not answer every question about a particular customer's data contract.

Spectrum is coordinated, not simply occupied

Radio systems share frequencies and orbital resources. International coordination and national authorization help manage harmful interference. ITU describes orbit-spectrum resources as part of the shared space-sustainability challenge. ITU: Space Sustainability Gateway.

An operator cannot assume that launching first grants unlimited permission to transmit at any frequency or power. A power-beaming proposal and a communications network may raise different approval questions. Exact obligations depend on the design and relevant authorities.

This article offers a public-policy overview, not project-specific legal conclusions.

Data has several addresses

Physical storage location is only one factor in data governance. Corporate control, contracts, access credentials, ground systems, customers, and applicable law can matter too.

Imagine a company advertising orbital storage as independent of every country. Ask who administers the system, where its employees work, what courts can reach its assets, and who controls its encryption keys. Those questions may reveal dependencies that altitude does not change.

The word “sovereign” should be supported by a clear account of control and legal obligations. It should not function as a decorative synonym for remote.

Infrastructure can concentrate power

An integrated operator might control launch, networking, computing, models, and customer distribution. That can reduce contracting friction and support coordinated engineering. It can also create dependency on one organization.

Customers should consider whether data and applications can move to another provider, whether prices are transparent, and whether a dispute in one service affects access to another. Governments may consider competition, security, and public-interest implications.

These are questions for assessment, not proof that integration is inherently good or bad. A fragmented market can also suffer from incompatible systems and unclear responsibility.

Defense use changes the stakes

Orbital computing can support sensing, communications, and analysis. Some applications may serve defense customers. That does not establish autonomous weapons authority, nor does civilian branding eliminate the possibility of dual use.

Responsible descriptions should identify the function actually supported. Image processing, secure storage, and command authority are different activities. Sensitive applications require appropriate access controls, human accountability, and mission-specific validation.

Security also includes routine commercial threats. NIST's guidance addresses the command-and-control systems that connect ground operators with spacecraft. NIST: satellite ground-segment cybersecurity.

Communities need a voice

Ground receivers, launch sites, and support facilities exist somewhere. People nearby have legitimate interests in safety, land use, environmental monitoring, and who pays for infrastructure changes.

Public participation should occur while designs can still change. A finished presentation announcing that all important choices have already been made is not meaningful consultation.

Internationally, access matters too. If useful orbits and services become concentrated among a few wealthy actors, smaller countries and research communities may face barriers. Shared standards and transparent coordination can help, but require deliberate effort.

Follow a customer's file through the organizations

Imagine a research institution sending data to an orbital service. The spacecraft owner operates the hardware, another company runs the customer software, a ground network carries the traffic, and a separate organization controls the encryption keys.

An incident could occur at any of those boundaries. The customer's practical questions are who can read the data, who may change the software, who reports a breach, and who is responsible for recovery.

These questions cannot be answered from altitude alone. They require the actual organizational structure, contracts, technical controls, and applicable law. The hypothetical example is intended to expose the questions, not assign legal obligations to an unspecified provider.

The best service description would make the chain intelligible. A customer should not discover after a failure that several suppliers each believed the missing responsibility belonged to someone else.

Portability matters before a disagreement

A provider may offer excellent service today while becoming difficult to leave tomorrow. Proprietary formats, large transfer charges, incompatible software, and restricted access to operating records can all make a customer dependent.

An orbital service introduces another practical question: how long would it take to retrieve the data if the customer decides to leave? A contractual right to export files is less useful if the available network capacity makes the intended migration impractical.

A prudent customer can test a small export and recovery process before committing important work. It can ask which records, model versions, and intermediate results are included, and whether a second environment can actually use them.

These are proposed procurement safeguards, not statements that every jurisdiction requires them. Their purpose is to keep a technical advantage from becoming unnecessary dependence on one organization.

Shared infrastructure needs a shortage policy

Imagine an orbital provider serving commercial research, government missions, and routine business customers when part of its capacity fails. Which work continues? Which users are interrupted? Can an emergency priority override an ordinary service commitment?

The answers may legitimately differ by contract and authorization. The important point is that users should understand the rules before a crisis. A hidden priority system can turn a promised independent service into a dependency customers did not knowingly accept.

Power networks face a related issue when generation or delivery falls short. Computing and electricity are different products, but both require a clear account of who bears shortage risk.

At a wider level, public authorities will need to consider how private agreements interact with safety and international responsibilities. Those public responsibilities and the customer priority rules need to work together; a commercial contract alone cannot settle both.

Governance can enable investment

Rules are often described only as obstacles. Clear responsibility can also make a project easier to finance and use. Customers can contract more confidently when they know who operates the service, what approvals apply, and how disputes and failures are handled.

Common interfaces can let suppliers enter a market without owning an entire vertically integrated system. Transparent coordination can help operators avoid building incompatible equipment or assuming access they do not possess.

The challenge is to make rules specific enough to protect shared interests without freezing every design around today's technology. That requires ongoing technical knowledge and public accountability.

The eventual orbital economy would need more than freedom to launch. It would need confidence that the organizations using a shared environment will honor responsibilities after the launch celebration is over.

What would prove responsible governance?

Look for clear authorization, accountable operators, published service boundaries, credible incident reporting, data portability where feasible, and funded end-of-life obligations. Review the actual contracts and permissions rather than accepting broad claims about freedom or security.

Humanity does not need to choose between ambitious space infrastructure and rules. Durable infrastructure requires rules people can trust. The difficult task is building them early enough that shared opportunity does not become a preventable source of conflict.

Previous article · Next article