Week in Space Data, every Friday.
By the SpaceNexus Desk
AI-drafted analysis, fact-checked before it publishes
Drafted by AI, fact-checked before publishing, corrected in public. How the desk works
Three separate announcements on October 12 and 13, 2026 point to the same shift in military satellite communications.
A fourth item adds context: a commentary piece titled "Multi-Constellation Networks Need Multi-Constellation Ground Stations" argued that the Pentagon has rightly decided military satcom should not depend on one network or supplier, but that adding satellites is only half of the problem.
The source summaries do not give contract values for the York task orders or detail the Lyntris scope beyond payload integration. This analysis therefore focuses on architecture and procurement patterns rather than dollar figures.
For years, the policy statement was simple: the Department of Defense wants resilient, multi-orbit, multi-vendor satellite communications. Statements are easy. The hard part is that different constellations use different waveforms, terminals, ground systems and data standards. If they cannot exchange traffic, a multi-vendor architecture is just a collection of single-vendor stovepipes.
The three announcements address three different layers of that problem.
Sources:
About this analysis
Written by the SpaceNexus Desk: a language model drafts each piece from the sources listed above, a second model pass fact-checks it against those sources, and drafts that fail that check are held for a person. No human typed this article. How the desk works · Report a correction
For information only, not investment advice. SpaceNexus is not a registered investment adviser, broker or dealer, and nothing here is a recommendation to buy, sell or hold any security. Data may be delayed, estimated or incomplete; check the source before acting. Full disclaimer
Week in Space Data every Friday: the week in numbers, our own analysis clearly labelled, the chart of the week and next week’s launches. Add SpaceNexus AM for a short brief on weekday mornings.
Week in Space Data on Fridays, SpaceNexus AM on weekday mornings if you tick it. Unsubscribe anytime.
The Space Data Network is intended to move data across a mix of government and commercial satellites. York's task orders, described as supporting interoperability, are about making satellites from different builders and operators talk to each other and to the wider network. Interoperability work is less visible than launches but often determines whether a constellation is useful in an operational setting.
PTS-G is a protected, anti-jam waveform capability. Awarding the first two operational satellites to two different companies, SES and Viasat, is itself a hedge against single-supplier risk. SES's choice of Lyntris as payload integrator shows how prime contractors lean on specialist integrators to deliver complex protected payloads. The pattern is a layered supply chain where operators, integrators and spacecraft builders each hold part of the delivery risk.
The terminal is where interoperability becomes real for the end user. A terminal able to maintain several satellite links at once supports switching or combining paths across orbits and networks. Viasat approving the Hydra MAX on its NextGen Ka-band network, including Mil Ka-band, means a third-party terminal is being integrated into a major operator's service ecosystem. That is an example of the open-terminal approach the Pentagon wants.
Multi-vendor satcom is only as resilient as its seams: the data standards, the payload integration and the terminals. This week's announcements are all seam work.
Builders like York, which compete for Space Force and Space Development Agency work, benefit when interoperability tasks are funded explicitly rather than assumed. For manufacturers, compliance with network standards becomes a competitive qualification alongside cost and schedule. Companies with proprietary, closed architectures may find fewer places to fit.
SES and Viasat, both historically GEO-heavy operators with expanding multi-orbit services, are positioning themselves as providers of protected military capacity rather than only commercial bandwidth. The PTS-G award gives both a role in a program that emphasizes anti-jam protection. It also puts them in a competitive-yet-collaborative arrangement, since the government is buying from both.
All.Space gets a visible commercial win from the Viasat order. More broadly, terminal makers that support multiple links, bands and constellations are likely to see demand rise as defense users avoid being locked to one network. The commentary about multi-constellation ground stations flags the same issue on the gateway side: if ground infrastructure is tied to a single constellation, it becomes a point of failure. The recent report of an arson attack on a Starlink gateway in Poland, with two suspects arrested in Germany, is a reminder that ground segments are physical targets.
For Space Force and allied militaries, the main implication is that integration risk now dominates over launch or satellite count risk. Testing, certification and standards governance need funding and staff. Programs that add satellites faster than they certify interoperability will build capacity that cannot be used coherently.
The same trend appears in civil markets. An opinion piece in Via Satellite argues satellites are becoming part of the mobile economy as proprietary stacks give way to standards-based networks. Gogo's deal to supply 40 Galileo HDX systems to Duncan Aviation shows terminals continuing to proliferate in business aviation. Commercial and military markets are converging on shared standards and multi-link terminals, which could lower costs through scale but also increase cross-dependence.
A budget shift, a program delay or a failed interoperability demonstration could change priorities quickly. Also, commercial constellation operators may resist sharing interface details, creating negotiation friction with government customers.