Sovereign gateways for leased constellations

Leasing capacity from a global constellation is commercially rational. Routing that traffic through a foreign-controlled gateway is a sovereignty problem. A national gateway shifts control of encryption, lawful intercept and traffic policy back to the state.

The dependence this ends: Foreign-controlled gateways carrying national traffic

The problem is not the satellite. It is the gateway.

Most governments that lease broadband capacity from a GEO or LEO constellation do so through a gateway the operator controls, often located in a third country. That arrangement is commercially convenient and technically invisible to end users. It is also the point at which the operator, or the jurisdiction hosting the gateway, holds the keys: to encryption, to traffic logs, to the ability to throttle or terminate service.

Post-2022, the risk calculus has shifted. The suspension of commercial satellite services over contested territories, disputes between operators and regulators in multiple jurisdictions, and the demonstrated vulnerability of undersea cables have all made governments reconsider what 'leased capacity' actually means in a crisis. The satellite link may survive. The gateway may not cooperate. Those are different failure modes, and only one of them is addressed by a sovereign gateway programme.

What a gateway does, and what it does not

A national gateway is the ground-side node through which traffic passes between the satellite and the national network. Building your own means the encryption keys are generated and held in-country, lawful-intercept obligations are met under national law rather than a foreign operator's compliance framework, and traffic routing decisions sit with your own engineers. For a government running critical services over leased capacity, that is a meaningful shift.

Be precise about what it does not protect you from. The constellation itself remains foreign-owned. If the operator suspends service, shuts down a beam, or is compelled by its home government to act, a national gateway cannot override that. The gateway controls the ground side of the link. It does not control the space side. Governments that need protection from operator-level decisions need a different programme entirely: a sovereign GEO or LEO communications satellite. This page covers the minimum-viable independence play, not the full one.

There is also a spectrum and licensing dimension. Operating a Ka-band gateway requires ITU-coordinated frequency assignments and a national licensing framework that permits the facility to function as a gateway rather than merely a receive terminal. Without that, the antenna is a large and expensive paperweight. Antenna siting, radio-frequency coordination and national space-law alignment are not afterthoughts; they are prerequisites.

The pathfinder level: what gets built

A sovereign gateway programme at pathfinder scale typically comprises one or two high-throughput Ka-band stations, in-country network operations and processing infrastructure, and the legal instruments that establish the facility as the authorised national gateway under the relevant operator agreement and domestic law. The physical footprint is modest. The institutional work is not.

Programmes of broadly this class have been delivered in the low tens of millions of dollars, though costs vary significantly with site preparation, power infrastructure, redundancy requirements and the complexity of the operator agreement being renegotiated. There is no single published benchmark that fits every case, and any figure given before a site survey and operator-agreement review is an estimate, not a commitment. What the public record does support: this is the least capital-intensive entry point in the sovereign-connectivity stack, and it can be operational within twelve to thirty months of contract signature, depending on licensing timelines in the host country.

The pathfinder level is the honest ceiling here. A single national gateway does not become an operational constellation or a full sovereign programme; it is a ground-infrastructure intervention. Governments that subsequently want to own the space segment should treat this as a first step toward a hybrid or fully sovereign architecture, not as a destination in itself.

What you own when the programme closes

Handover is structured around the facility and the people who run it. At programme close, the national team holds the gateway hardware and software under source-access terms agreed before contract signature, the frequency coordination filings registered in the country's name with the ITU, the encryption key-management infrastructure, and the operational procedures and documentation produced during the programme.

The limits are worth stating plainly. The operator agreement governing use of the constellation's capacity remains a commercial relationship between the government and a private entity. Satellize does not own that relationship and cannot guarantee its continuity. The gateway gives the government control over its end of the link. Sustaining the link requires an ongoing commercial arrangement with the constellation operator, and governments should plan for that dependency explicitly.

Operator readiness and the institutional gap

The technical build is the faster half of this programme. The slower half is institutional: establishing the legal entity or government body that will operate the gateway, training staff to manage network operations and security, and embedding the facility into national emergency and continuity-of-government plans.

Countries that have gone through undersea cable failures, as Tonga did in January 2022, understand this acutely. Restoring connectivity through a satellite link is one problem. Knowing who is authorised to operate the gateway, under what legal framework, and with what escalation path when something goes wrong, is a different problem. Satellize's Tonga sovereign-comms work after the cable break illustrated both sides of that gap. The antenna goes up faster than the governance does. Planning for the governance from day one shortens the overall timeline considerably.

What this mission is built from

Ka-band high-rate stations: Primary ground node terminating the leased constellation's capacity onto the national network, with in-country encryption and traffic management.
Antenna siting and licensing: Site survey, radio-frequency coordination and ITU filing to establish the gateway as a legally authorised, interference-cleared facility.
In-country data processing: Network operations infrastructure ensuring traffic logs, encryption keys and policy enforcement remain within national jurisdiction.
National licensing and space law: Domestic legal framework and space-law instruments designating the facility as the national gateway under both operator agreements and national regulation.

What you end up owning

Ka-band gateway station hardware, installed and commissioned at a nationally controlled site
Encryption key-management infrastructure, held under national custody
ITU frequency coordination filings registered in the country's name
Network operations software under source-access terms agreed before contract signature
Operational procedures, documentation and training materials
A trained national team qualified to operate and maintain the facility independently

Handover proceeds in stages: the national team shadows operations from commissioning, takes primary responsibility during a supervised transition period, and assumes full independent control at programme close. Satellize retains no ongoing operational role after handover; post-programme support, if required, is contracted separately. The operator agreement with the constellation provider remains the government's own commercial relationship throughout.

Programme parameters

Programme level	Pathfinder (ground infrastructure only; no space segment)
Gateway stations	1 to 2 Ka-band high-throughput stations
Frequency band	Ka-band (26.5 to 40 GHz uplink / downlink, subject to ITU coordination)
Indicative delivery timeline	12 to 30 months from contract signature, dependent on licensing and site preparation
National operating team at handover	Typically 4 to 10 trained operators and network engineers
Space segment dependency	Leased capacity from a third-party constellation operator; not eliminated by this programme
Legal instruments required	ITU filing, national gateway licence, source-access agreement, operator gateway agreement
Cost class	Low tens of millions of dollars (indicative; varies with site, redundancy and operator-agreement complexity)

Sources

One contract, one accountable engineer

Commissioned as one programme, not a stack of contracts: spacecraft, launch, ground segment, mission control, training and handover are priced together. Source-access terms and audit rights are agreed in writing before signature. Request a gateway feasibility review.