Viasat and Space42 are putting up to $1 billion behind Equatys, a proposed direct-to-device venture built around a simple division of labour: the venture would own common satellite and ground infrastructure, while operators keep their own spectrum and customer relationships. The initial system is planned at fewer than 200 satellites, with an architecture designed to scale to 2,800. The scale is eye-catching, but the boundary is the more important part of the proposal. Payload’s account of the Equatys plan makes clear that the two founders intend to be the system’s first clients, not to surrender their retail identities to a new constellation owner.
The hard problem is deciding what gets shared
Satellite infrastructure is expensive enough that shared ownership has obvious appeal. Spacecraft, ground networks, operations teams and the capital behind them all benefit from reuse. Yet the case for pooling those assets is not the same as a case for pooling every commercial right around them. Spectrum access, customer contracts and a carrier’s relationship with its subscribers are often the assets that make the service valuable in the first place.
Equatys is structured around that distinction. Space42 and Viasat say they would each contribute $400 million when the venture forms, subject to regulatory approvals and Viasat’s appointment as prime technology contractor. Space42 is expected to add a further $200 million in a later round that could include outside investors. The companies describe a telecom-tower model: operators share the physical system, but retain their own spectrum and customers. The announced funding structure and operating model are still a proposal, not an operating network. That caveat matters. It is nevertheless a more credible starting point than a generic promise that one large constellation will somehow serve everybody equally.
The claim here is straightforward: shared space infrastructure scales only when the common operating layer is separated from the rights and commercial decisions that need to remain customer-specific. A common spacecraft network may reduce duplicated capital expenditure. It cannot make differences in spectrum, regulation, service commitments or end-user trust disappear.
Standardization is useful when it has a job
The recent EnduroSat financing illustrates the other half of this equation. The company raised $205 million to expand standardized satellite production, and Vantor selected it to provide the buses for 24 satellites in a 40-satellite imaging constellation, with CACI supplying the imaging payloads. Payload’s reporting on the raise and contract shows a familiar but important allocation of responsibility. The bus manufacturer is not trying to own every payload or every data product. It is making a repeatable platform available to a customer with a defined constellation service to deliver.
That is what good standardization looks like. It standardizes the parts that become safer, cheaper or more dependable through repetition, while preserving room for a payload, a service proposition or a customer relationship to remain distinct. A satellite bus, a ground segment or a mission-operations process can be common infrastructure. The value that a customer is trying to create with it often cannot be.
The opposite model is tempting because it sounds tidier. One company owns the spacecraft, the payload, the data, the customer account and every decision in between. Sometimes that is the correct choice, especially when a mission is genuinely novel or the interfaces are still immature. But vertical integration is not a free substitute for operating discipline. It can conceal the real work of defining responsibilities until a programme has already made commitments that are difficult to unwind.
The interface is where shared missions succeed or fail
The practical test is not whether several organizations appear on the same architecture chart. It is whether their interfaces can survive a change in requirements, launch provider, payload configuration or operating model without turning into a fresh integration project each time.
That is why the operating boundary is more demanding than a procurement boundary. A contract can specify who supplies a spacecraft and who supplies a payload. A repeatable mission needs the deeper agreement to hold when engineering assumptions move. It needs clear ownership of configuration control, data paths, anomaly response, acceptance criteria and the evidence each party receives after flight. The work is less visible than a new satellite order, but it is what allows a shared system to remain shared after the first mission.
Hydrosat’s Osiris announcement is another useful signal. Its planned constellation combines a long-wave infrared instrument with visible and near-infrared sensors, then feeds imagery into the company’s Discovery Platform for day-to-day change detection. Payload’s description of the planned five-sensor payload and analytics service points to a market that is increasingly buying an operational result rather than an isolated instrument. The customers care about a usable monitoring service. The spacecraft, sensors, processing and delivery layer have to work together well enough to provide it.
That does not mean every customer needs to own every layer. It means the mission owner must know which layer is responsible for what. If the operator owns the common infrastructure, it needs a disciplined way to carry qualified interfaces and operating knowledge forward. If the payload provider or customer owns the data product, that right has to remain explicit rather than being implied by the shared mission.
A large constellation does not solve governance
Equatys still has meaningful open questions. Its architecture is designed to grow to 2,800 satellites across 60 orbital planes and three altitude layers, while its first phase would have fewer than 200 spacecraft. The service target is the end of 2029, and no operator customers or launch markets had been named in the reporting. Those limits are part of Payload’s report , not an afterthought to the funding headline.
The unanswered question is whether the proposed division of responsibility can survive the move from a founding partnership to a wider operator ecosystem. New investors may join. New carriers may bring different spectrum rights, regulatory obligations and service expectations. A system designed to let each operator keep its own customers has to make those boundaries legible in the ground architecture, commercial agreements and daily operations, not merely in a launch announcement.
That is not an argument against shared infrastructure. It is the standard by which it should be judged. The useful evidence will be the first commercial operating arrangements, the terms under which additional operators connect, and whether the system can accommodate those differences without creating bespoke work every time.
The repeatable asset is the operating model
Space has a habit of treating the satellite as the whole product. It is a visible artifact, expensive to build and easy to count. But a shared system becomes durable through the less glamorous decisions around it: which interfaces are fixed, which responsibilities move with the customer, what evidence is captured after each mission, and how the next participant joins without restarting the programme.
That is also why shared missions have a stronger long-term case than a simple cost-sharing argument. Their value is not just that several participants divide a launch bill. A well-run mission can produce an operating model that makes the next payload, data service or customer deployment less uncertain. The system gains a reusable base while the parties using it retain the rights that make their own businesses distinct.
Equatys has not proven that model yet. It has, however, stated the right problem to solve. Shared infrastructure needs common operations, not forced sameness. The companies that turn that distinction into working interfaces will have built something more useful than a large constellation. They will have built a way to repeat a mission without asking every customer to become the same kind of operator.
SATELYX builds shared missions that validate space technology in orbit and turn what works into reusable capability. More at satelyx.com, and more analysis from Clement Chen.