What exactly is a cross-domain interlink and why does it matter for defence?

A cross-domain interlink (CDI) is a data relay — optical or RF — that connects satellites in different orbital regimes (LEO, MEO, GEO) directly in space, bypassing ground stations. In a contested environment, ground stations are fixed, vulnerable targets. CDIs allow a nation to route command, sensor, and communications data through space even when terrestrial infrastructure is degraded or denied. The architectural leap matters because it converts a collection of independent satellites into a coherent, resilient network.

Can't we just use a commercial relay service like Inmarsat or Viasat instead of building our own?

Commercial services can carry unclassified tactical traffic, and many allied forces already use them for logistics and non-sensitive communications. The problem is that a sovereign defence network requires end-to-end key management, guaranteed priority access, and the ability to operate in a degraded or wartime environment where a commercial operator may suspend service, be compelled to share metadata with a foreign regulator, or simply deprioritise military traffic. For classified ISR relay or nuclear-command connectivity, commercial dependency is a strategic liability no credible defence posture should accept.

How does optical ISL compare to RF ISL for a national programme?

Optical free-space links offer throughput in the tens of gigabits per second with no spectrum licensing burden and virtually zero intercept probability — which makes them strongly preferred for intelligence relay. The trade-off is a highly complex terminal requiring precise pointing, acquisition, and tracking (PAT), and terminals remain expensive at roughly $1–3 M per unit at current production rates. RF ISLs in Ka- or V-band are simpler to build and more tolerant of pointing error, but require ITU coordination and are more susceptible to jamming and interference. A national programme should plan for optical primacy with RF fallback.

What orbits should a national cross-domain interlink architecture use?

The backbone should sit in LEO (typically 700–1,200 km) for latency and global coverage cadence. MEO relay nodes at ~8,000–20,000 km can act as persistent crosslinks for polar and anti-access regions where LEO revisit is unacceptably short. GEO nodes provide continuous coverage over a fixed theatre and are appropriate for strategic command relay, but their 600 ms round-trip latency makes them unsuitable as the primary tactical path. A layered architecture that uses all three, with autonomous route selection, is the target state.

How long does it take to field a credible national CDI capability?

From programme launch to an initial operational capability with 12–18 LEO transport-layer satellites and tested ISLs realistically takes seven to ten years for a nation building the industrial base from scratch, and four to six years if domestic satellite manufacturing already exists. The US Space Development Agency, starting from a mature industrial base, took approximately four years to achieve first on-orbit demonstrations of its ISL mesh. Buying time through allied interoperability agreements while building sovereign capacity is the pragmatic interim approach.

What encryption and security standards apply to ISL traffic?

Traffic traversing CDIs that carries classified content must use NSA-approved Type 1 cryptography (for US and many allied systems) or nationally certified equivalents. NATO interoperability requires compliance with STANAG 4778 for IP-layer transport and STANAG 4406 for military messaging. Nations outside the NSA/COMSEC ecosystem should budget significant time — often two to four years — to develop or procure certified space-rated crypto modules, as commercial off-the-shelf encryption does not meet military classification requirements.

How does a cross-domain interlink architecture support missile warning?

Missile warning sensors in GEO (wide-area infrared stare) and MEO generate large data volumes that must reach decision-makers in seconds. A CDI mesh allows raw or partially processed sensor data to hop from GEO to the nearest LEO relay node — cutting the relay path from a vulnerable fixed ground site to an in-space handoff — reducing the time from detection to command-authority alert by 30–60 seconds in modelled scenarios. This is why Satellize rates the missile-warning application at sovereignty score 10.

What happens to the network if an adversary destroys one of the relay nodes?

A well-designed CDI mesh uses dynamic routing protocols — analogous to OSPF or BGP in terrestrial IP networks — that detect link failure within milliseconds and re-route traffic around the gap. The survivability logic depends on constellation density: SDA modelling suggests that losing up to 20% of transport-layer nodes still preserves end-to-end connectivity at reduced throughput. Nations should design for N+2 redundancy at minimum and conduct regular degraded-constellation exercises to validate that autonomous re-routing actually works under operational conditions.

7.9.4Live

Cross-Domain Interlinks

Military analysts at consoles with multiple screens displaying data feeds in a command operations centre — Soldiers in group discussion embody the human networks that cross-domain orbit interlinks strengthen through shared defence intelligence.

Cross-Domain Orbit Interlinks for Defence Intelligence

1
Multi-Orbit Constellation
LEO, MEO, GEO satellites exchange crosslinks
2
Ground Gateway
Encrypted downlink via hardened ground terminals
3
Fusion Engine
Cross-domain data fused into unified picture
4
Warfighter Node
Commanders receive actionable multi-domain intelligence

Satellite crosslinks across orbital regimes feed a fusion engine delivering unified intelligence to field commanders.

Page in the build queue

This application has its place in the atlas. The full page — short and long descriptions, what-matters bullets, sovereignty rationale, and the eight-field architecture block — is being written next.

Maturity reading: Operational systems exist with paying customers. Phase 1 built §4.1 (Maritime Intelligence) end-to-end as the depth-and-format reference. Section 4 is the next section to graduate from scaffold to full content; the rest follow on the roadmap.

Related applications

7.9.3 · Previous

Resilient Communications Backbones

All in multi-orbit defence architectures

7.9.5 · Next

Distributed Sensor Architectures

Bring this into your sovereign programme.

All solutions Speak with engineering