Firefly vs Impulse: Control vs Reach
Impulse Space
The real split here is control versus reach. Firefly is building a one stop mission stack where the same company can sell the rocket, the transfer vehicle, the lunar delivery system, and related mission services, which lets it line up hardware and launch slots inside one program. Impulse is building the transport layer instead, with Mira and Helios designed to fly on many rockets, which widens its addressable market but leaves launch timing and availability in other companies hands.
-
Firefly’s integrated offer is concrete, not conceptual. Its IPO filing says Elytra vehicles are available on Alpha and Eclipse, and Blue Ghost Mission 2 pairs a Blue Ghost lander with Elytra Dark as a relay. That is a bundled mission architecture, not just a tug attached to someone else’s launch.
-
Impulse has pushed the opposite model far down into product design. Helios is presented as launcher agnostic and lists compatibility with Falcon 9, Falcon Heavy, New Glenn, Vulcan, Neutron, Ariane 6, H3, Eclipse, and others. That makes Impulse easier to slot into many missions, especially for customers that already buy launch elsewhere.
-
The tradeoff shows up in how missions get sold and scheduled. Impulse can act as an upper stage prime and package transport with partners, but its own materials still frame Helios as paired with a medium lift launch provider, and partnerships like Exolaunch and SES reinforce that the launch piece is coordinated across companies rather than owned in house.
This market is moving toward fuller mission bundles. If Firefly keeps proving Alpha, Eclipse, Elytra, and Blue Ghost together, it can win buyers that value one accountable contractor. If Impulse keeps adding launcher relationships and flying Helios regularly, it can become the neutral transport layer that sits on top of the whole launch market.