Service · Software development

Custom maritime software development.

Custom maritime software for shipping companies, port operators, stevedores, freight forwarders and offshore operators — from voyage and port-call management to bunkering platforms, customer portals for cargo tracking and customs flows via Portbase. We don't replace your CargoWise, Navis N4 or Veson IMOS, but build targeted custom layers where standard packages fall short.

Voyage & port-callPortbase & ICUEAIS data ingestionIMO & SOLAS

Maritime software rarely fits into a single standard package.

The Netherlands is a global player in maritime. Rotterdam is Europe's largest port, Amsterdam, Vlissingen and IJmuiden operate on a large scale, and in offshore the Dutch fleet is a leader. Behind that maritime chain runs a dense stack of enterprise systems — CargoWise for forwarders and freight forwarders, Navis N4 as the terminal operating system for stevedores, Veson IMOS for chartering and voyage management, DAKOSY in the Hamburg and Bremen port hubs, Cassidian Sirius as a port portal, DNV ShipManager for fleet management and Q88 for vessel particulars. At enterprise scope, that layer works well.

We don't replace those packages. We are brought in for the layer around them: a custom Terminal Operating System for a mid-size terminal that doesn't fit a Navis N4 licensing structure, a customer portal for cargo tracking with live AIS data, a bunkering platform that links fuel orders to delivery on board, a voyage management layer for a mid-sized shipping company that doesn't want to commit to IMOS, or a Portbase and ICUE integration that respects your own workflow. For the broader context of what we do in transport software, see our main page.

The target group is broad: deep-sea shipping companies for container, bulk, breakbulk, RoRo and tankers, short-sea and inland shipping operators, port authorities such as Port of Rotterdam Authority, Port of Amsterdam and North Sea Port, stevedores and cargo handlers in every ECT, APMT, RWG, Steinweg and Broekman style, freight forwarders and forwarding agents, offshore services in dredging, heavy-lift, subsea and wind, maritime manufacturing and shipyards, fisheries and fish farming, watersports and yacht building, fuel traders and bunker suppliers, plus marine insurance and P&I players. The IT stack differs slightly for each segment, but the pattern remains: dense standard systems surrounded by work processes that are hard to squeeze into an out-of-the-box module.

At the same time, a lot is changing: digital customs flows are getting stricter, the IMO is pushing decarbonisation through the DCS and the EU through MRV reporting, Ballast Water Management (BWM) and MARPOL requirements are changing maintenance cycles, and Port State Control demands more traceability. Those new data fields are not always available in CargoWise, Navis N4 or IMOS in a form your operation can handle. A lightweight custom layer on top of your existing system is then often more practical than waiting for the vendor to release a module.

Three patterns in which we build in the maritime sector.

Custom maritime software is a broad field. We are usually asked to work on three types of projects — and most assignments combine two of them.

Fleet and voyage project · fixed sprint budget

Voyage management, vessel management and bunkering

An integrated layer for shipping companies that don't run fully on CargoWise or Veson IMOS, but still want control over chartering, voyage planning, route and weather routing, port rotation and bunker orders. Vessel particulars, surveys, certifications and dry-dock planning in a single record, with an automatic signal flow to the classification society (DNV, Lloyd's, BV) when a certificate expires or a survey window opens.

The bunkering component is a separate sub-module that we often build on its own or in combination: orders from operations, delivery by bunker suppliers to the vessel, BDN (Bunker Delivery Note) registration, fuel cost allocation to finance and the voyage, and an integration with IMO DCS and EU MRV for the mandatory reporting. For mid-sized shipping companies and bunker traders working outside the top-tier enterprise suites, that eliminates a paper-based process.

Voyage managementVessel particularsBunkering & BDNDry-dock planningDNV/Lloyd's integrationWeather routing
Terminal and cargo project · fixed sprint budget

Terminal operations, cargo management and port calls

For mid-size container, bulk, breakbulk and tanker terminals that are too small for a Navis N4 implementation but too big for Excel. We build a lighter, custom Terminal Operating System: vessel planning, yard management, gate flow, container stacking, bulk flow from ship to silo or train, breakbulk handling for heavy equipment and RoRo flow. This includes integrations with the terminal's existing planning, finance and weighing systems.

The cargo module covers booking, B/L generation, manifests and EDI with the supply chain: shipper, forwarder, customs and carrier. The port-call module links ETA and ETD, services on board (pilot, tugs, bunkering, waste reception), cargo release, terminal allocation and gate slots. For forwarders who want more control over customer-facing flows alongside their CargoWise instance, we often build a customer portal with live status. For the wider logistics process, see our page on automating logistics processes.

Terminal Operating SystemCargo & B/LPort-call managementYard & gateRoRo & breakbulkEDI
Customs, AIS and compliance project · fixed sprint budget

Portbase, AIS data and customs & compliance flows

An integration layer for Dutch port IT: Portbase for the generic message flow between shipper, terminal, customs and road transport, ICUE for inbound clearance, plus the customs integrations for ENS, EXS, T1 and T2 documents and the NCTS flow. If your operation relies mainly on Antwerp, Hamburg or Bremerhaven, we carry the same pattern over to the NxtPort, DAKOSY and BHT equivalents there.

The AIS module is a separate sub-module: ingesting vessel positions via AIS providers (Spire, MarineTraffic, Vesseltracker) or your own receiver, storing time series, ETA models based on destination, speed and historical behaviour, plus customer-facing track and trace via a dedicated portal. For the wider context of a customer-facing tracking layer, see our page on track and trace systems. Compliance reporting under IMO, SOLAS, MARPOL, BWM and Port State Control runs on the same data set.

A port facility subject to ISPS has its own security plan with three levels and a designated officer. See ISPS software.

PortbaseICUEAIS ingestionENS/EXS/T1-T2IMO & SOLASBWM & MARPOL

What you have at the end.

Working maritime software in production, plus everything around it to manage, audit and develop it yourself within the applicable IMO, EU and Dutch standards.

  • Production and staging environmentTwo separate environments in your own cloud (GCP, AWS, Azure) or in a dedicated EU tenant with us, with the right network segmentation between office, terminal operations and ship-onboard where relevant.
  • Web, mobile and ship-onboardA browser application for the office, terminal and operations centre, a mobile crew and inspection app for use on board, plus a ship-onboard layer with low-bandwidth synchronisation via satellite (VSAT, Starlink, Iridium) as soon as a connection is available.
  • Full codebase and documentationSource code, build instructions, architecture overview, an integration map covering CargoWise, Navis N4, Veson IMOS, Portbase, ICUE, AIS providers and classification societies, plus mappings for every integration. No vendor lock-in.
  • Compliance packageAudit trails, electronic signatures where IMO and SOLAS require them, an IMO DCS and EU MRV report generator, a customs trail for ENS, EXS, T1 and T2, plus a validation file you can hand to the flag state authority, classification society or customs.
  • Training and knowledge transferSessions for key users (fleet managers, terminal planners, port captains, customs coordinators, HSE officers, IT administrators), plus short video tutorials for crew on board and operators at the terminal. An incident-response runbook for your IT team.
  • Maintenance contract (optional)Monitoring, backups, security patches and ongoing development for a fixed monthly fee. Suited to 24/7 operations, with agreed response-time levels for mission-critical components such as port-call and customs flows.

When custom pays off in maritime.

Four patterns where an off-the-shelf package gets stuck and targeted software adds value, based on projects we see in shipping company, terminal, freight forwarder and offshore contexts.

Segment-specific

Container, bulk, breakbulk or tanker each need their own flow

Navis N4 or CargoWise is optimised for container flows. If you handle breakbulk with heavy project cargo, load bulk with conveyors and silos, or run tankers with cargo heating, vapour return and pumping checks, you are at the edge of what the standard package can do. A targeted custom flow for your cargo type stops operators from resorting to workarounds that fall outside any audit trail.

Mid-size terminal

Too small for Navis, too big for Excel

Stevedores and cargo handlers with anywhere from 50,000 to a few hundred thousand movements a year are in an awkward position: the licence costs and implementation of Navis N4 or Cassidian are out of proportion, but Excel and standalone modules don't scale. A custom Terminal Operating System (yard, gate, planning, weighbridge) covers exactly the scale and flow of your site.

Customer-facing

Cargo tracking and self-service portal

Shippers, freight forwarders and end customers expect live status, document access and self-service flows like those they know from retail and parcel tracking. Standard packages rarely deliver that portal layer in your own branding and with exactly the data fields that matter. Your own customer portal built on your cargo, port-call and AIS data takes customer queries off your team and sets you apart in a sector where that is hard to do.

Compliance density

IMO, EU MRV, BWM and Port State Control

The combination of IMO DCS, EU MRV, MARPOL, BWM, SOLAS requirements for cargo securing and LSA, plus Port State Control reporting, rarely fits into a single standard module. A targeted reporting and audit flow that draws all data from one source and exports it in the right formats to the flag state, classification society, customs and EU MRV verifier saves duplicated work and reduces risk.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Modules that recur in almost every maritime project.

The building blocks we draw on. The combination and depth differ per organisation and per maritime segment, but these elements come up again and again.

Fleet

Vessel management and certification

Vessel particulars per ship, with IMO number, MMSI, flag, classification society, P&I club and relevant surveys. Certifications (SOLAS, MARPOL, BWM, ISM, ISPS) with expiry dates, automatic alerts to the fleet manager and direct export to Q88 format for charterers who ask for it.

Voyage

Voyage management and chartering

Chartering with fixture data, voyage instructions, port rotation, route planning with weather routing, laytime calculation and demurrage. Bunker orders linked to the voyage and cost allocation to finance. Accessible to operations ashore and to the master on board via a low-bandwidth web interface.

Bunkering

Bunker orders and BDN flow

A bunkering platform covering fuel orders from operations, allocation to bunker suppliers, delivery on board with a Bunker Delivery Note, BDN archiving in line with IMO requirements and cost allocation to voyage and finance. For independent bunker traders as a standalone tool, for shipping companies as an integration with their own voyage layer.

Crew

Crew management and STCW

A crewing app for rotations, contract management, STCW (Standards of Training, Certification and Watchkeeping) certifications, medical checks, vaccinations and travel arrangements. Includes an integration with payroll and covers the Maritime Labour Convention requirements for working and rest hours on board.

Cargo & B/L

Cargo management and manifests

Booking, B/L generation (master and house), manifests, cargo securing plans and stowage instructions. EDI with shippers, freight forwarders, customs and carriers via the standard maritime EDI formats (BAPLIE, COPRAR, COREOR) and the Portbase and ICUE message flows.

Port call

Port call management and services

ETA and ETD coordination between agent, terminal, pilot, tugs and authorities; booking services on board (bunkering, waste reception, ship supplies, fresh water); cargo release and terminal allocation. Mobile app for port captains and agents, with direct sync to the Port Authority system.

Customs

ENS, EXS and T1/T2 via Portbase & ICUE

Pre-arrival ENS, pre-departure EXS, T1 and T2 transit documents, customs declarations via Portbase for Rotterdam and Amsterdam, ICUE for inbound clearance, and NCTS for transit. Plus equivalent patterns for NxtPort (Antwerp), DAKOSY (Hamburg) and BHT (Bremerhaven) if your flows go that way.

Track & trace

AIS data and customer-facing tracking

Live vessel positions via AIS, combined with booking and port call data in a customer-facing tracking portal. ETA models based on AIS speed, destination, historical port call behaviour and weather. For shippers, freight forwarders and end customers, in your own branding.

Maintenance

Maintenance and dry-dock planning

A Planned Maintenance System (PMS) for maintenance on board, work orders for the chief engineer, inventory management for spare parts and oil, plus dry-dock planning with scope of work, classification input and yard quotes. Sync between ship and office via a low-bandwidth protocol.

Compliance

IMO DCS, EU MRV and Port State Control

One consolidated reporting layer for the IMO Data Collection System (DCS), EU Monitoring, Reporting and Verification (MRV), Annual Efficiency Ratio (AER), Ballast Water Management reporting and Port State Control checks. Includes electronic signatures where the standard requires them, and export formats for flag states, classification societies and EU verifiers.

Offshore

Offshore services and specialist fleets

For offshore operators in dredging, heavy lift, subsea, decommissioning and offshore wind, such as Boskalis, Van Oord, Heerema, Allseas or IHC, we build project modules that bring together spread planning, vessel utilisation, marine spread overviews and project DPRs (Daily Progress Reports). Often with an integration to our oil and gas software for the upstream context.

Integration

An API layer for the maritime IT chain

A clean API layer that exposes your cargo, voyage, port call and customs data in a structured way to CargoWise, Navis N4, Veson IMOS, Portbase, ICUE, AIS providers and classification societies. Part of our API integration practice: build it right once, and every following system is easier to connect.

How a maritime project works.

1

Introduction

A conversation in which we learn which bottleneck you face in operations, terminal flow or the chain with customers and authorities, which enterprise systems you run (CargoWise, Navis N4, IMOS, Portbase, ICUE) and which maritime standards are relevant to your segment.

2

Process, system and compliance analysis

We model your operational flow per maritime segment: fleet, terminal, freight forwarder or offshore operator. Interviews with operations, planners, port captains, customs coordinators and IT, plus a systematic review of the integration landscape and the applicable standards under the IMO, EU and Dutch law. End result: a scope document, a plan and an initial screen flow.

3

Building in sprints

Fortnightly working builds, ready to be tested on a pilot flow: one terminal, one voyage cluster or one customer portal. For ship-onboard apps we test the low-bandwidth sync early, and for Portbase and customs flows we work directly with the actual message exchange. Feedback from your operations is built in straight away.

4

Rollout, validation and management

A phased rollout per location, vessel or segment, a validation package for classification, flag state or customs, training ashore and on board, plus ongoing support for security patches, further development and expansion into new compliance modules such as EU FuelEU Maritime or CII.

Frequently asked questions.

What clients in shipping, terminal, freight-forwarding and offshore contexts usually want to know before we start.

Will you replace our CargoWise, Navis N4 or Veson IMOS?
No, and we are explicit about that. It makes no sense to rebuild a working implementation of CargoWise for freight forwarding, Navis N4 as an enterprise TOS, Veson IMOS for chartering or DAKOSY in a North European hub. We build the custom layer around them (customer portal, mid-size TOS, voyage or bunkering tool, customs flow, compliance reporting) and integrate via the standard APIs and EDI flows of your existing platforms.
Does your software work with Portbase, ICUE and Dutch port IT?
Yes. We integrate with Portbase for the generic message flow between shipper, terminal, customs and road transport in Rotterdam and Amsterdam, with ICUE for inbound clearance, and with customs systems for ENS, EXS, T1 and T2 documents and NCTS. For flows that also touch Antwerp, Hamburg or Bremerhaven, we carry the same pattern over to NxtPort, DAKOSY and BHT.
How do you ingest AIS data and what do you do with it?
We read AIS data via providers such as Spire, MarineTraffic or Vesseltracker, or via your own receiver if you are close enough to the North Sea. Positions are stored as time series, combined with booking and port-call data, and used for ETA models, customer-facing track and trace, fleet monitoring and compliance checks (such as BWM zone checks). For the broader track and trace context, see our page on track and trace systems.
What about IMO, SOLAS, MARPOL and BWM compliance?
Our software layer typically doesn't sit inside a SOLAS-certified safety system on board, but it does sit around it: IMO DCS and EU MRV reporting, BWM logs, MARPOL incidents, Port State Control trail and certification overview. We document explicitly which functions run ashore and which on board, and where needed we coordinate with your classification society (DNV, Lloyd's, BV) on the scope of validation.
Does the ship-onboard app work on poor satellite connections?
Yes. The ship-onboard layer works with low bandwidth and, if needed, fully offline. Crew, the chief engineer or an inspector can record checks, work orders, BDNs and certification updates on board; at the first connection via VSAT, Starlink or Iridium, or on arrival in port, a compact sync goes to the shore-side environment. Conflict resolution and version management are a standard part of the architecture.
What determines the cost of a project like this?
The breadth of scope (a single module or a connected set), the number and complexity of integrations (CargoWise, Navis, IMOS, Portbase, ICUE, AIS, classification), the compliance domain you need to cover, whether ship-onboard is a requirement, and the scale of the rollout in vessels, terminals or customers. We work in fixed sprints with a transparent budget per sprint, so scope and costs grow under your control.

Talk to us about your maritime software.

A no-obligation half-hour introduction. We listen to your operations flow, ask follow-up questions on compliance, integrations and port IT, and give you direction you can actually use, even if custom software turns out not to be the answer. For the broader context of where this type of project fits, see our page on transport software, our work on oil and gas software or our API integration practice.

Edit content