The Maritime Operating System: Why Shore-Side Operations Still Run on Radios and Spreadsheets

Maritime is investing in AI at a genuinely fast clip. The maritime AI market was valued at roughly $4.13 billion in 2024 and is on track for a 23% compound annual growth rate over the following five years, and the number of organizations actively building maritime AI has grown from 276 to 420 in a single year. Cost is the stated reason: more than 70% of shipowners and managers point to cost reduction as the main driver behind digitalisation, with close to half forecasting savings above $1 million a year and 15% expecting savings north of $10 million. The wider maritime digitization market — everything from smart navigation to onboard sensors — is valued at roughly $241 billion in 2026 alone.

Almost all of that investment sits on or around the vessel itself: voyage optimisation, predictive maintenance, fuel-efficiency modeling, digital twins of the ship and its machinery. That's a reasonable place to focus, and it's producing real results. What it hasn't touched, in most operators, is the shore-side business running underneath the vessel — the booking, the dispatch, the tariff calculation, the fuel-quality verification, the claim raised when something goes wrong. That side of the operation is, for a large share of the industry, still coordinated by radio, phone call, whiteboard and spreadsheet, updated by whoever remembers to update it.

That gap matters more in maritime than it would almost anywhere else, because so much of what happens on the shore side carries a legal or contractual consequence attached to it. A towage job's tariff is a legally billable amount, not an estimate. A bunker delivery's quality verdict determines whether a supplier or a buyer is on the hook for a disputed claim. None of that is forgiving of an informal process the way a generic back office might be.

Why the usual tools fail here in a specific way

Marine operators choosing software today are typically stuck between three options, and each one fails at this problem differently. Heavyweight ERP suites — SAP and its peers — were never built to price a night movement against a regional holiday calendar or verify a fuel delivery against an international quality standard; approximating that takes years of customization. Port and terminal systems dispatch cargo, not tugs, and have no concept of a tariff rule or a claims workflow. And spreadsheets, radios and phone logs — still the default across a large share of the industry — put the tariff book in someone's memory and turn every billing dispute into an argument nobody can settle with evidence, because there's no record of which rule applied to which job at which moment.

The fix isn't a better spreadsheet or a more patient ERP customization. It's software built specifically for how a marine operation actually runs, with the pricing and compliance rules enforced in the system itself rather than carried in someone's head.

Three systems, two underlying disciplines

Marine services split cleanly into two operational problems that look similar from a distance but are run by different people, on different timelines, with different failure modes — and one of those two problems shows up in two different markets with two different regulatory regimes behind it.

Towage and pilotage dispatch is a live, real-time coordination problem: which tug and which crew are free right now, what does this specific movement cost under the tariff that applies to it, and can that invoice be defended line by line if a shipping agent disputes it later. Total port costs for a single large vessel call — port dues, pilotage, towage, linesmen, cargo handling — commonly run $50,000 to $200,000, and pilotage and towage are repeatedly flagged as the single biggest source of overrun between the disbursement account agreed upfront and what actually gets invoiced, precisely because those charges are usually reconstructed by hand after the job rather than calculated at the point of service. Crew certification carries its own quiet exposure alongside it — a single vessel can carry well over a hundred separate certificates needing tracking against expiry and endorsement dates, and a missed one doesn't surface until an audit or a port state control detention makes it visible, at which point a two-day detention has been estimated to cost in the region of $68,000 once missed schedules, fees, fuel and crew overtime are added up.

Bunker fuel supply is a different problem: a delivery has to be verified against a quality standard, and if a buyer disputes it, the supplier's entire position depends on producing a clean evidentiary record fast enough. Bunker-related claims rose roughly 50% in the first five months of 2026 compared with the same period the year before, and the overwhelming majority concern fuel quality rather than delivery logistics. A typical quantity dispute costs in the region of $27,790 to resolve; on the quality side, industry P&I data attributes 16% of main-engine machinery claims to off-spec bunkers, at an average repair cost of roughly $545,000. Bunker claims also carry unusually short contractual time bars — a supplier can have a fully defensible, in-spec delivery and still lose a dispute purely because the right sample wasn't tested against the right standard, or because the claim wasn't formally raised inside the window, which has nothing to do with the fuel itself and everything to do with how the evidence was kept.

Different operational rhythm, same underlying requirement: the rule — tariff, quality standard, claim deadline — has to be enforced by the system at the moment it matters, not reconstructed from memory after the fact.

What that actually looks like built out

BlastAsia's Port & Maritime Operators systems — part of the Xamun OS Series, built by Xamun and delivered by BlastAsia — cover both disciplines across two markets.

MarshaOS runs Gulf towage and pilotage dispatch: booking, live tracking, crew and captain field apps, and a billing engine where every invoice line traces back to a specific, versioned, effective-dated tariff rule rather than a number someone typed in. When an agent disputes a charge, the response is a rule citation and a sealed evaluation record, not a spreadsheet formula somebody may have edited since the job ran.

TugOS runs the same discipline for Philippine harbours — the same operational category as MarshaOS, built and proven against a different regulatory backbone. An advisory dispatch matrix recommends tug count and minimum bollard pull against Philippine Ports Authority compulsory-tug floors, a fleet scheduler catches conflicts before two crews are committed to the same job, and billing rates a signed Statement of Facts against the exact tariff version stamped at booking before posting to ERP. MARINA certificate compliance is checked at the point of dispatch — an under-tugged movement or an expired license gets stopped before it sails, not flagged in a report afterward.

BunkerOS runs the supply side: AI-assisted intake that turns a raw email or WhatsApp nomination into a structured booking a human confirms, live barge-fleet scheduling, and a quality auditor that checks lab certificate values against the governing edition of the ISO 8217 standard using the correct reproducibility margins for that edition — an easy detail to get wrong by hand, and a common source of disputes on its own. The moment a claim is raised, the platform starts the time-bar clock automatically and seals the relevant evidence with a ledger-linked hash, so the defensible record exists before the dispute even properly starts, not scrambled together afterward.

Localized to fit regulations — and built to extend past one region

MarshaOS and BunkerOS were built and proven first for Gulf operations specifically, and that shows in the detail: native AED billing with 5% UAE VAT, Hijri and Friday-Saturday weekend calendars, full Arabic right-to-left interfaces, and direct posting into SAP S/4HANA rather than a bolt-on integration project. BunkerOS is additionally proven against Fujairah's specific bunkering-hub conditions — a market that has swung sharply on volume this year amid regional disruption, exactly the kind of volatile supply environment that pushes buyers toward less familiar counterparties and raises the odds of a quality dispute.

TugOS was built and proven for a different regulatory backbone entirely — Philippine harbours, against PPA compulsory-tug floors, MARINA certificate rosters, and the Data Privacy Act (RA 10173), rather than Gulf regulation. It's the clearest illustration in the whole maritime family of the same product category built and proven twice, deliberately, for two markets with genuinely different rules underneath.

None of that regional detail is architecturally fixed. MarshaOS and TugOS's billing engines both work from a versioned "rules pack" per jurisdiction — a specific port's tariffs, surcharges, calendar and tax treatment, bundled and checksummed as data the engine reads rather than logic written into the codebase. A new port or a new country is a new rules pack, not a rebuild — the same underlying dispatch and billing engine, pointed at a different jurisdiction's numbers. The regional tag on any of the three products today reflects where it has the deepest operational track record, not a hard limit on where it can run.

Why the timing matters right now

The forcing functions here are converging from a few directions at once. Maritime AI investment is accelerating industry-wide, and the operators capturing real savings from it are the ones treating it as an operational discipline, not a pilot project. Regulatory pressure is tightening in parallel — international quality and emissions standards keep being revised, and an operator running on manual processes has no reliable way to confirm which edition of a standard actually governed a specific delivery. And in both of BlastAsia's proven markets — a volatile Gulf bunkering market producing more disputes, and Philippine harbours where PPA and MARINA enforcement leaves little room for an under-documented dispatch — the cost of an indefensible paper trail is rising, not falling.

The operators building a real evidentiary and billing discipline now are the ones who'll be trusted with the harder, less familiar counterparties everyone else in the market is currently avoiding.

How this actually gets built

Each system is built by Xamun through the Xamun Software Factory and delivered to clients by BlastAsia. Each starts from a proven production base rather than a blank page — the majority of the codebase is generated by AI agents from an approved specification, then passed through automated quality gates before a human ships it. A configuration workshop tailors that base to a specific operator's ports, fleet and rulebook, delivered through BlastAsia's Turnkey or xDD engagement models, with a live, working system typically following in weeks rather than the multi-year timeline a traditional maritime ERP integration would require. All three systems are also demo-ready before any commercial conversation — an operator can click through the actual product, not a slide deck, before deciding anything.

Where to start

The maritime family in BlastAsia's OS Series is smaller than some of the other verticals — three systems, not four or more — but it's built on the same principle and the same compliance discipline across both disciplines and both markets. The honest starting question is the same one that applies anywhere in this series: which side of your operation is actually costing you right now — the dispatch and billing side (Gulf or Philippine), or the fuel-quality and claims side?

If you're evaluating where the real exposure sits in your own marine operation, let's talk through your fleet and ports.