What exactly is a strategic government WAN in a satellite context?

A strategic government WAN is a private wide-area network linking ministry headquarters, military commands, border posts, embassies and critical infrastructure sites — all running over dedicated satellite capacity rather than the public internet. 'Strategic' denotes that the network is resilient by design, encrypted end-to-end, and controlled exclusively by the sovereign operator so no foreign entity can intercept, throttle or deny it.

Why not just use Starlink or Inmarsat for government connectivity? It's faster to procure.

Leased commercial capacity gives the provider full visibility of traffic metadata and, in some cases, payload if encryption is managed by the provider. Starlink's terms of service explicitly allow SpaceX to suspend service in jurisdictions where it determines legal or regulatory conflicts exist — a clause that has real operational meaning for governments in contested regions. Inmarsat and Viasat are subject to US ITAR and UK export-control regimes. A sovereign constellation places control of the kill-switch firmly with the government itself.

How many satellites does a viable sovereign government WAN constellation need?

For a mid-sized nation (roughly 500,000–2 million km² footprint), a minimum viable LEO constellation is typically 6–12 microsatellites in complementary orbital planes, providing 2–4 simultaneous passes per site per day with ground-diversity design filling coverage gaps. Nations requiring continuous uninterrupted coverage — not store-and-forward — need 18–24 satellites or a hybrid LEO/GEO architecture. ESA's Connectivity studies and World Bank infrastructure financing frameworks both use 12 satellites as a planning baseline for national government WAN programmes.

What encryption standards should a sovereign WAN mandate?

The baseline is AES-256 for payload encryption and NSS Suite B (now CNSA Suite) for key exchange, as specified in NIST SP 800-56B. For nations handling classified traffic above RESTRICTED, Type 1 encryption devices — or their national equivalent certified by the domestic SIGINT authority — should encrypt traffic before it ever reaches the satellite link. ITU-T X.805 provides the architectural zoning framework most national CERTs reference when segmenting government WAN security domains.

Can a sovereign WAN constellation also carry civilian government traffic, or must it be military-only?

Dual-use architectures are both technically feasible and fiscally sensible. Many programmes — France's Syracuse IV, Australia's JP9102 — reserve dedicated high-assurance transponder capacity for defence while routing civilian ministry traffic over a logically separated but physically co-located beam. Traffic separation is enforced through virtual LAN tagging, separate encryption keys, and gateway-level firewall segmentation, not separate hardware. This approach materially reduces cost-per-bit for the sovereign operator.

How does a nation file for orbital slots to protect its sovereign WAN constellation?

Orbital slot coordination is governed by the ITU Radio Regulations, Articles 9 and 11. A nation must submit an Advance Publication of Information (API) filing to the ITU Radiocommunication Bureau, followed by a Request for Coordination (RfC) and ultimately a notification for registration in the ITU Master International Frequency Register (MIFR). The process is public and adversarial — other operators can file interference claims. Nations should engage ITU coordination specialists at least 8 years before intended launch, and consider filing placeholder positions immediately even if launch timelines are uncertain.

What is the realistic procurement timeline from decision to first operational satellite?

For a first-generation sovereign WAN microsatellite constellation procured via competitive tender, the realistic timeline is 5–8 years: 18–24 months for requirements definition and procurement, 24–36 months for satellite manufacture and testing, 6–12 months for launch campaign, and 6–12 months for in-orbit commissioning and WAN integration. Nations that piggyback on an existing allied constellation or purchase a commercial constellation shell can compress this to 3–4 years, at the cost of some sovereignty over the platform.

How does a sovereign WAN satellite programme interact with existing terrestrial fibre government networks?

Satellite WAN is most powerful as a resilience layer, not a replacement for fibre. The recommended architecture is a hybrid WAN: primary fibre routes carry bulk traffic at low cost, while the satellite layer provides automatic failover within 30–90 seconds, continuity for sites unreachable by fibre (remote installations, mobile command posts, embassies), and an independent path that cannot be severed by the same physical event — earthquake, sabotage, or submarine cable cut — that might take down terrestrial links.

1.2.6Live

Strategic Government WANs

Civil servants at computer terminals inside a government network operations center in Kenya — Reliable government connectivity fosters confident leadership and collaboration, as this laughing manager and his staff demonstrate.

Sovereign Satellite WAN Linking Government Sites

1
Satellite Relay
GEO/MEO satellite routes encrypted traffic
2
Hub Earth Station
National teleport authenticates all government links
3
Core Network
Sovereign MPLS backbone, classified enclave separation
4
Ministry Nodes
Remote offices, border posts, embassies connected

Encrypted signals hop via satellite through a national teleport, binding dispersed government sites into one sovereign network.

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

1.2.5 · Previous

National Emergency Connectivity

All in sovereign digital infrastructure

1.2.7 · Next

Election Communications Infrastructure

Bring this into your sovereign programme.

All solutions Speak with engineering