A Subscription to the Moon’s Communications Network

Part 7 of 60 · Series date: September 7, 2026

A scientist should be able to concentrate on the experiment. If that scientist must also design a lunar communications system, the project becomes much larger before it collects its first measurement.

Shared communications could remove part of that burden. Picture a future instrument arriving with a compatible radio, connecting to an available service, and sending its first results through gear already in place. The scene is hypothetical, but the economic logic is straightforward: buy access to a network instead of building the whole network yourself.

ESA’s Moonlight program pursues lunar telecommunications and navigation services. The existence of such initiatives shows development toward shared services, not universal coverage already available on the surface. ESA’s Moonlight program.

What would a subscription actually buy?

For one buyer, it might mean a small daily data transfer. Another might need a large stream of instrument readings. A vehicle operator could need navigation support and timely messages. A missed emergency message could have far more serious consequences than a delayed panoramic photograph.

These differences create potential service levels. A buyer could pay for routine delivery within a certain period, reserved capacity, or priority during specified operations. The terms would need to describe coverage, outages, support, and what happens when gear fails.

The best analogy is not a magical lunar Wi-Fi cloud. It is a transport network for information, with routes, capacity limits, and places that are harder to reach. A connection between a rover and its base is one link. A relay to Earth is another. A failure anywhere along the route can interrupt the buyer’s result.

Compatibility could make this market much more useful. If several providers accept common interfaces, an instrument may have more options. If each network needs unique hardware and software, changing providers becomes costly. A low introductory price can hide a long commitment.

Security belongs in the product. A network must check who sent a command and whether that sender has permission to act. Separate checks must detect unsafe or mistaken commands, including those sent by an authorized user. Buyers also need to know which data can be shared and which must remain private. The objective is dependable operation, not just keeping a password secret.

Picture a small research team with limited funding. It can afford a small instrument, but not a complete relay mission. A shared network could make its work possible. That would widen participation—if the service is priced and documented in a way the team can actually use.

Now picture the network has only one major buyer. Even with many small subscribers, it may remain dependent on that buyer’s contract. Investors and public agencies should examine that dependence openly. A subscription page does not by itself create a stable market.

People on Earth could benefit through easier access to measurements, work in network operations, and more groups able to run experiments. These are plausible pathways, not automatic benefits of launching communications hardware.

A missed picture and a missed command are different products

Imagine that two customers request a connection at once. One wants to download a detailed landscape image. The other needs confirmation that a vehicle has stopped near a worksite. The first can probably wait. The second may need an immediate answer.

This is why a communications business cannot describe its entire product with one impressive data rate. Customers care about when a message arrives, how often the service is available, and how confidently they can tell that a command was received. A large file transferred tomorrow and a small command delivered on time solve different problems.

A shared network could offer scheduled transfers for flexible work and reserved capacity for time-sensitive tasks. It could store data when a route is unavailable and forward them later. Customers would need to know which behavior to expect before they build their operations around it.

The cheaper mission that never appears in the network’s accounts

Suppose a fictional university plans a small instrument. Without a shared network, it must include more communications equipment, more engineering, and more testing. With a suitable service, it can use a standard connection and devote more of its budget to the experiment.

The network operator records a subscription sale. The university sees a larger gain: a project that became affordable. That difference matters when we assess infrastructure. Some of its value appears in the activities it enables, rather than in its own earnings.

We should avoid counting the same benefit twice. If the university’s total project saving already includes the reduced communications bill, adding that bill again as a separate social gain would inflate the result. Good accounts can trace the chain without turning every link into new wealth.

Shared access also depends on documentation. An affordable connection is of little use if a small team must hire specialists merely to understand how to join. Clear technical guides, test tools, and a responsive support desk could be as important to participation as another increment of capacity.

Trust travels with the data

A scientist needs to know where a measurement came from and whether it changed in transit. An operator needs to know that a command came from an authorized source. A customer may need to keep business information private while sharing scientific results publicly. These needs should be designed into the service.

The network also needs a plan for failure. Which tasks can continue locally? Which must stop? How will customers learn that a route is unavailable? A system that fails clearly can be easier to manage than one that appears to work while quietly losing messages.

For Earth, the most immediate return would be access. A small team could receive measurements from a place it could never staff on its own. Students could work with real observations. Engineers could monitor equipment and improve it between missions.

The far-reaching promise is a Moon where every new instrument does not arrive alone. It would join a growing web of services, people, and knowledge. A dependable connection could turn a remote machine into an active part of a research community on Earth.

The first message from our imagined instrument is small: a status report, a temperature reading, and confirmation that the experiment can begin. Its value lies in the work that follows.

A successful lunar network would make an extraordinary site easier to use. Its strongest advertisement would be buyers who stop worrying about the connection and start doing something worthwhile with it.

Back to contents