Vendor Concentration Risk in Ship Management Software

A structural feature of ship management software is easy to overlook until it matters: the classification society that certifies a vessel is, increasingly, also the company running its fleet management platform. That overlap changes the concentration risk conversation from a normal vendor question into something more specific to this sector.

The end-to-end fleet management software market has consolidated heavily. Lloyd’s Register acquired Hanseaticsoft, developer of the Cloud Fleet Manager platform, in 2017, and later absorbed Ocean Technologies Group to pair fleet analytics with crew training content. DNV runs its own Nauticus Fleet platform alongside its classification business. ABS operates ABS Nautical Systems’ NS5 platform across roughly 4,800 vessels, integrated with its own classification and certification databases. The vast majority of end-to-end fleet management solutions in the market today are provided by, or owned by, the major classification societies themselves — not a coincidence of market timing, but the dominant structural pattern in the sector. This is what that pattern means for how a ship manager should actually assess vendor concentration.

Who this is for

• The technical director or IT lead at a ship management company assessing whether the fleet’s software concentration is actually understood, not just tolerated.
• The owner evaluating a new ship management platform and weighing a class-affiliated option against an independent one.
• The board member reviewing vendor dependency risk across a fleet that’s grown through acquisition, with inherited platforms across multiple vessels.

The specific overlap this sector has that most others don’t

When a vessel’s classification society is also its fleet management software provider, the platform’s deep integration with class records and certification databases creates a genuine operational benefit — but it also creates switching costs that are structurally higher than a typical SaaS relationship. A ship manager considering a change of maintenance management platform on a DNV-classed vessel using DNV’s own Nauticus Fleet isn’t just migrating data between two commercial products; they’re potentially disentangling operational software from certification record-keeping that the same organisation maintains on both sides. This doesn’t make the arrangement wrong — the integration is often genuinely useful — but it does mean concentration risk here isn’t purely commercial. It touches the vessel’s statutory compliance record in a way a generic vendor relationship doesn’t.

The market is more concentrated at the top than it looks

Broader maritime software market figures show the top five vendors holding under 40% of overall revenue — a picture of reasonable fragmentation. But within ship management software specifically, the top ten vendors hold an estimated 58% of market revenue, and a large share of that concentration sits with the class-affiliated platforms described above. A ship manager operating a mixed fleet across multiple class societies may believe they’ve diversified vendor risk by using different platforms per vessel — when in practice they’ve concentrated exposure across a small number of the same handful of class-affiliated software organisations, just distributed differently across the fleet.

Consolidation is still actively running

The acquisition pattern hasn’t slowed. Beyond Lloyd’s Register’s moves, Kongsberg acquired COACH Solutions in 2020, and ABB expanded its maritime software footprint by acquiring DTN Shipping’s European and Philippine weather-routing operations in January 2024. Independent, well-funded specialist platforms have generally either been acquired by one of the end-to-end providers or forced into channel partnerships to gain distribution — genuine independent traction against the entrenched end-to-end providers has been rare. A ship manager’s current vendor landscape should be assumed to look different in three years, not because of anything the ship manager does, but because the vendor side of the market keeps consolidating around it.

Why switching is harder here than the contract suggests

Fleet management software is, by the industry’s own description, “sticky” — switching providers is a substantial undertaking with implications for the ship’s crew, the class society relationship, and charterer-facing reporting, not just an internal IT migration. This matters directly for exit planning: a ship manager should price the realistic cost and disruption of a platform switch honestly into any vendor concentration assessment, rather than treating contractual terminability as equivalent to practical switchability. A platform that’s contractually easy to leave but operationally very difficult to actually leave is not, in any meaningful sense, a low-concentration-risk arrangement.

The API layer as a partial mitigant

Some of the concentration risk has a genuine, if partial, technical mitigant: platforms like DNV’s Veracity marketplace and Inmarsat’s Certified Application Provider programme allow independent point solutions to integrate via API rather than requiring a ship manager to adopt an entire end-to-end platform from a single vendor. Where a ship manager’s core dependency genuinely can’t be diversified — the primary maintenance management or crewing system, for instance — using an API-based marketplace approach for adjacent functions (weather routing, performance monitoring, specific compliance modules) at least avoids compounding the concentration further across every function the fleet needs.

What an honest concentration assessment includes

1. A fleet-wide map of which vendor runs which system on which vessel, with class-affiliated platforms explicitly flagged as a distinct risk category from independent vendors.
2. A realistic, not contractual, estimate of switching cost and disruption for each critical platform, covering crew retraining, class-record continuity, and charterer reporting continuity.
3. Explicit awareness of where class-affiliation creates a coupling between operational software and statutory compliance records, and what that means if the relationship needs to end.
4. A view on which non-core functions could reasonably move to an API-integrated point solution to avoid further concentrating dependency on the primary platform vendor.
5. A standing watch on the vendor landscape itself, given the pace of consolidation — a diversification strategy built today can be quietly undone by an acquisition the ship manager has no visibility into until it’s announced.

How we engage with this

We read ship management technology dependency with this sector’s specific structural pattern in mind — where class affiliation and software concentration overlap — as a Supplier and Dependency Review. The output is a written concentration risk assessment the board can act on, distinguishing genuine diversification from apparent diversification.

We don’t broker software vendor relationships. We don’t sell fleet management platforms. We don’t represent ship managers to class societies. We read what’s there, identify what’s missing, and write it down for the people who have to decide what to do about it.

Pricing is published at /pricing/. If your fleet’s software vendor concentration has never been mapped explicitly, the place to start is a conversation.

Sixteen Pillars is a technology governance consultancy based in Cyprus. Engagements run remote across the EU, UK, and Middle East, with on-site time where the engagement requires it.