Sovereign Space Capabilities: Australia’s Defence Space Command & European IRIS²Conceptual schematic · not to scale. Labels and connections illustrate the concepts explained in this guide.Authoritywho can decide?Operationswho can administer?Supply chainwho can maintain?Assured accesswhat survives a loss?Trust
FIG. 29 / Conceptual engineering diagram. Not to scale. On small screens, swipe to inspect.

Key takeaways

  • Define sovereignty in operational and contractual terms.
  • Defence capabilities are not ordinary consumer service offers.
  • Treat programme milestones separately from delivered service.

Sovereignty has several layers

A sovereign capability can involve national decision authority, trusted procurement, operational control, domestic industry, assured access and protection of sensitive information. These are related but not identical. A nationally based gateway does not necessarily imply domestic ownership of spacecraft, software or all onward transport. Define the assurance objective before comparing programmes.

Australia established Defence Space Command in 2022. Its public role concerns Defence’s space capability and access, not a retail broadband service for households. Consumer procurement should not infer guaranteed capacity or priority from the existence of a national military space organisation.

European secure connectivity

IRIS² is the EU secure-connectivity programme, with a multi-orbit architecture and governmental as well as commercial ambitions. Programme design and schedules can change; use the Commission’s current programme material for live milestones. This guide deliberately does not present a planned constellation count or future service date as a delivered capacity commitment.

An enterprise evaluating future services should distinguish policy intent, contracted development, deployed assets, accredited operation and orderable commercial products. Each is a different readiness stage.

Build a procurement scorecard

Ask who can authorise service changes, where privileged administration occurs, how encryption keys are controlled and what alternative remains after provider withdrawal. Evaluate supply-chain support, software update authority and access to incident evidence. Geographic coverage is only one dimension of assured connectivity.

Practical near-term architecture

Use currently available, tested services for current obligations and preserve room for future options through standard handoffs and portable application design. Avoid a continuity plan that depends on an announced service not yet activated for the site. For sensitive workloads, involve the responsible security authority before selecting a carrier or claiming national assurance. Commercial redundancy and sovereign assurance should be documented as separate objectives.

From concept to acceptance

Worked design exercise

A procurement team lists domestic gateway location, customer-controlled keys and continuity during provider withdrawal as three requirements. Each needs different evidence: routing and processing commitments, key-management architecture, and an exit or alternate-service plan. A single label such as sovereign cannot establish all three.

Score proposed services against observable controls and contract rights. For a future programme, record which controls are available now and which remain commitments or design goals. Keep current continuity obligations covered by activated services until the new capability passes the organisation's acceptance process.

Regional compliance & specification note

Australia / ACMA. domestic ownership does not waive spectrum authorisation. Defence-related use requires the responsible agency’s separate approvals and handling rules.

Germany / BNetzA. national frequency compliance and EU programme assurance are distinct; consult the competent authority for the intended service and sensitivity.

These are procurement checks, not a determination that a particular installation is authorised. Confirm the current equipment, service, site and operating mode with the relevant authority and provider.

Sources & further reading

Official references for standards, programme context and service terms. Worked examples and design checklists are editorial analysis; verify project-specific inputs before implementation.

References reviewed 03 October 2026. Operator terms and regulatory documents may change.

Ask an engineering questionBack to top ↑