Veson IMOS, Kpler and Zeaclub: Understanding Three Different Maritime Software Categories

Three different categories, often compared as one

These three products appear on the same shortlist regularly, and the shortlist is usually wrong — not because any of them is a poor product, but because they answer different questions. Comparing them like for like produces a scoring matrix in which every row is a category error.

Read down the last row. It is the only one that determines whether two products conflict.

Veson IMOS: commercial freight and voyage workflows

Veson positions IMOS as a commercial maritime freight-management platform spanning voyage and freight estimation, planning and operations, exposure management and post-voyage settlement. It is widely associated with structured workflows from fixture through final invoice, and with integrations across the maritime software ecosystem.

The fit is strongest where a company needs a mature commercial system of record, sophisticated voyage economics, trading and risk capability, and has the process maturity to use them. It is a heavier commitment than it first appears: the value is realised through configuration and disciplined use, which means implementation and change management are a real part of the cost.

It is the wrong tool for a company whose problem is that the agent, the superintendent and the crewing team cannot see the same port call.

Kpler: trade and maritime intelligence

Kpler focuses on real-time physical-trade and maritime intelligence. Its maritime offering combines AIS-driven vessel visibility, analytics, cargo and trade-flow context, arrival forecasts and data integrations.

It is used when teams need to understand what is happening across fleets, ports, commodity flows and markets — not only what is recorded inside their own company. The fit is strongest for traders, analysts, charterers, risk teams, governments and operators that depend on external market visibility.

Kpler is not a system of record and does not claim to be. It is an input. A company that buys it expecting workflow will be disappointed, and a company that skips it because "we already have a VMS" has misunderstood what it does. For the underlying data mechanics, see how AIS becomes maritime intelligence.

Zeaclub: connected operational workflow

Zeaclub is built as a Maritime Operating System: a connected workspace for vessels, operations, people and payments. Its role is to reduce the gaps between stakeholders, documents, tasks and decisions, while allowing specialist data and enterprise systems to remain connected rather than replaced.

The differentiation is not a claim to recreate every mature capability of IMOS or every dataset behind Kpler. It is coordination across the wider ecosystem — including the parties who will never hold a licence for a commercial VMS: agents, suppliers, surveyors, crew, counterparties.

Stated plainly, so the comparison is fair: where a company's primary requirement is deep voyage economics and freight exposure management, a mature commercial VMS is the more direct answer. Where the primary requirement is external market data, an intelligence provider is. Zeaclub's case is strongest where the pain is fragmentation between people and systems rather than depth within one function.

Complement, compete or integrate?

A shipping company may reasonably use all three categories at once. Market intelligence informs a voyage decision; the commercial system records the economics; the operating layer coordinates execution with agents, crew, finance and counterparties.

The architecture should be judged on five questions, not on feature counts:

1. Which system is the source of truth for each object — vessel, voyage, port call, document, counterparty? Two systems claiming the same object is the definition of an integration problem.
2. Who needs a full licence and who needs controlled external access? Per-seat pricing on a product that agents and suppliers must use will quietly force those users back into email.
3. How quickly can data be exported, and in what completeness? Test this during evaluation, not at renewal.
4. What is the real implementation burden, including the internal effort that no vendor quotes?
5. Can workflows be reconfigured without a permanent consulting dependency?

Questions to ask before buying

Ask every vendor to demonstrate the same scenario with your own data: a fixture changes, an ETA slips by 40 hours, a certificate expires mid-voyage, a demurrage claim is disputed, an invoice needs approval outside the office. Count the screens, the exports and the manual hand-offs.

Then ask the questions vendors are least comfortable with: how are AI-generated suggestions attributed and audited; what happens to your data if you leave; is customer data used for model training; who is accountable when an automated output is wrong. A full evaluation framework is in the ship management software buyer's guide.