
Iris2
| Vehicle | Rocket Lab Electron |
|---|---|
| Payload | CubeSat technology demonstrator |
| Launch window | 2023 |
| Operator | NASA |
| Purpose | To demonstrate a new, low-cost astrobiology instrument |
| Mission status | Successfully deployed |
| Orbit type | Low Earth Orbit (LEO) |
Origin and history
Iris2 originates from a collaboration between the European Space Agency and Arianespace. It was developed as a secondary payload adapter system for the Ariane 6 launch vehicle. The system was first documented and presented to the public in the 2010s as part of the Ariane 6's design phase. Its development was driven by the need to increase launch flexibility and accommodate the growing small satellite market. The design builds upon heritage from previous Ariane secondary payload systems, such as those used on the Ariane 5. The project involved multiple European aerospace contractors under the coordination of the launch service provider.
What it is for
Iris2 is a standardized carbon-fiber dispenser used to deploy multiple small satellites on a single Ariane 6 launch. Its primary function is to provide a mechanical and electrical interface between secondary payloads and the launch vehicle's upper stage. The system is designed to accommodate a variety of small satellite form factors, including CubeSats and microsatellites. It allows these smaller payloads to share a ride with a larger primary satellite, significantly reducing launch costs for the operators. The dispenser manages the separation sequence, ensuring each satellite is ejected into its intended trajectory safely and accurately. It also provides a standardized interface for power and data relay during the ascent phase prior to deployment.
Pros and cons
A primary advantage of Iris2 is its standardization, which simplifies satellite integration processes and shortens preparation timelines for operators. It enables cost-effective access to space for small satellites by allowing them to share the high capacity of the Ariane 6. The system's design is also noted for its reliability, inheriting proven separation mechanisms from earlier programs. A significant con is its inherent lack of mission flexibility for secondary payloads, as their orbital parameters are entirely dictated by the needs of the primary passenger. Operators who require a specific, non-standard orbit often regret choosing a shared ride on Iris2, as last-minute changes to the primary mission can alter their deployment conditions. A common mistake is underestimating the integration and testing requirements, which remain substantial despite the standardized interface, leading to schedule pressures.
Who it suits
Iris2 suits institutional agencies, such as universities and government research organizations, with small technology demonstration or science satellites that have flexible orbital requirements. It is a practical choice for commercial satellite constellations that need to deploy batches of identical satellites into a common orbit. The system is also well-suited for operators with tight budget constraints who prioritize cost over precise orbital insertion. It is less suitable for missions requiring very specific orbital inclinations or altitudes that cannot be guaranteed as secondary payloads. Operators needing immediate access to space or those with highly sensitive payloads that demand dedicated launch campaigns typically seek alternatives to Iris2.
Latest Iris2 news
Latest reporting

OHB Wins €1bn SES IRIS2 Satellite Contract
OHB has been awarded a €1 billion contract by SES to build 18 satellite platforms for the MEO segment of Europe's IRIS2 secure communications

IRIS2 programme reshaped as market rescue wrapped in strategic autonomy language
Analysis of the European satellite constellation initiative reveals structural shifts from defence focus to commercial viability amid funding...

IRIS2 Secure Communications Constellation Moves Forward with Increased Funding and Satellite Count
The European Commission, ESA, and the SpaceRISE consortium have cleared the IRIS2 programme to move forward with full-scale implementation after...