01 / The perspective
The question behind the signal.
Our planning proposition: connectivity sovereignty becomes useful to an organisation when it can specify the control, continuity and service access it needs. Satellite ownership alone does not answer those questions. A procurement team might need a workable transition; a supplier might need a defined interface and qualification route. Map those dependencies before treating a programme milestone as a reason to commit. The scenarios below explore different paths, without ranking their likelihood.
02 / Dated evidence
What the sources establish.
Read each observation with its original date. Announcements and programme intentions do not by themselves establish an operational service.
An expanded programme baseline
On 7 August 2026, ESA reported an implementation agreement for a main IRIS² constellation of 348 satellites. It described first launches targeted for 2029 and work still ahead on detailed design, ground infrastructure and deployment. These are programme intentions, not evidence of available service.
Responsibilities are becoming specific
OHB announced an award for eighteen MEO satellite platforms on 31 August. SES’s 7 August statement places payload production and satellite assembly, integration and testing at its Luxembourg facilities. Together, the releases identify distinct delivery responsibilities.
A service target still needs qualification
SES targets MEO service entry in 2030. ESA describes progressive operational deployment from 2029 onwards. These statements concern different scopes; neither establishes when a particular customer can obtain a qualified service on acceptable terms.
03 / Open questions
Keep the uncertainty visible.
- Which terminals, integration requirements and service terms will apply to your intended use? The reviewed announcements do not settle them.
- How will manufacturing, launch, ground readiness and customer qualification interact if one workstream moves more slowly?
- What combination of operational control, geography and recovery capability would satisfy your organisation’s actual sovereignty requirement?
04 / Possible futures
Three paths to think with.
These scenarios are authored thinking prompts. They are neither exhaustive nor assigned probabilities.
Scenario 01
A coordinated transition
If space infrastructure, ground systems and user qualification become ready in a compatible sequence.
Customers could move selected workloads through trials into routine use while retaining existing links during acceptance. Suppliers with tested interfaces could find an opening before large operational commitments. The useful advantage would be readiness to integrate, rather than simply being early to express interest.
- What this could mean
- Prepare a narrowly defined use case and acceptance checklist that can be tested when an appropriate service becomes available.
- Evidence to watch
- Published user trials that connect technical performance to a named service and onboarding route.
Scenario 02
An extended overlap
If infrastructure enters use in stages and customer transition takes longer than expected.
Organisations could operate old and new arrangements together for several budget cycles. Integration work, retraining and duplicated support might matter more than the nominal service start. Decisions made around a single switch-over date could become difficult to unwind even if the underlying programme continues progressing.
- What this could mean
- Examine contract flexibility, migration effort and the resources needed to support two arrangements at once.
- Evidence to watch
- Changes to customer migration windows, compatibility requirements or the scope of early services.
Scenario 03
Different routes to service
If public and commercial users require different assurances, interfaces and purchasing arrangements.
A single programme could support several distinct markets. A proposition designed for one user group might need substantial adaptation elsewhere. Demand for assured emergency communications, for example, could create different integration questions from routine enterprise connectivity, without either route becoming the universal model.
- What this could mean
- Choose the user problem and assurance requirement your organisation can credibly address before broadening the proposition.
- Evidence to watch
- Separate qualification pathways and service descriptions for different customer groups.
05 / What to watch
Look for a change in the evidence.
Demonstrated interfaces
A documented handover between components helps test whether your own integration assumptions remain workable.
Acceptance evidence
A launch or factory milestone answers a different question from a customer’s ability to operate a service.
A practical route to purchase
Named requirements and usable terms turn a broad opportunity into a decision your team can assess.
06 / Your next decision
Make the question your own.
- Write down one critical connectivity dependency, its owner and the consequence of an interruption.
- Choose one reversible preparation step, such as mapping an interface or documenting an acceptance requirement.
- Define the evidence that would justify a larger commitment, and a review date before that commitment becomes difficult to change.
Source register
Follow the evidence.
Source publication dates and access dates are recorded separately. The editorial review date describes this synthesis.
- Source esa-iris2 · ESA · primary sourceIRIS² reinforced and accelerated as implementation advances ↗
Published 2026-08-07 · Accessed 2026-09-12
- Source ohb-platforms · OHB · supplier announcementIRIS² award for eighteen satellite platforms ↗
Published 2026-08-31 · Accessed 2026-09-12
- Source ses-meo · SES · operator announcementSES MEO strategy after IRIS² Rendez-vous 1 ↗
Published 2026-08-07 · Accessed 2026-09-12
- Source si-connectivity · Space Insights · separate analysis publicationBuses from Bremen, Payloads in Luxembourg ↗
Published 2026-09-08 · Accessed 2026-09-12