D-Orbit Increasing Customer Stickiness

D-Orbit is trying to turn a one time delivery vendor into an operating layer that stays attached to the satellite after deployment. ION already does more than drop off spacecraft, it can host payloads, provide onboard compute, and feed data into D-Orbit mission software, while the company is also building servicing vehicles for life extension and other on orbit work. That makes D-Orbit harder to replace than a tug that only provides last mile transport.

• The product stack is getting broader in a very concrete way. NASA describes ION as offering on orbit storage and computational capability in addition to deployment, and D-Orbit markets Aurora as cloud mission control for satellites and constellations. A customer using both flight hardware and ops software has more workflows tied into one vendor.
  1 nasa 3 dorbit 4 dorbit
• The servicing push extends that relationship even further. ESA selected D-Orbit for an in orbit servicing mission built around extending satellite life, which moves D-Orbit from getting spacecraft to orbit into helping keep them useful once they are there. That creates a longer revenue tail per satellite than launch and deployment alone.
  5 esa 6 dorbit
• This is where D-Orbit differs from thinner orbital tug models like Momentus. Standalone transfer vehicles sell a narrower job, move the satellite once, then the customer relationship largely ends. A broader stack can bundle deployment, hosted payload operations, mission software, and later servicing into one contract, which raises switching costs and supports repeat business.
  7 nasa 8 sacra

The market is likely to split between point solutions and integrated orbital infrastructure. If D-Orbit keeps layering software and servicing onto its transportation base, competitors like Impulse will need to match that stickiness either by building adjacent services or by making their propulsion performance so valuable that customers accept a simpler vendor relationship.