Platform · Autonomous vessels

A crewless ship cannot inspect itself.

Maritime Autonomous Surface Ships (MASS), remotely operated vessels, and defense USVs all share one structural gap: no crew to walk the hull, read the tanks, and file a condition report. Hullproof CoatingPassport is the structured, machine-readable condition-intelligence layer that replaces the missing human loop — IMO MASS Code and DNV AROS aligned.

Why Hullproof is the condition layer MASS needs

Crewless means no human condition check

On a conventional ship the crew walks the hull, the tanks, the cargo holds — and files a report. A crewless vessel has none of that. The entire human condition-monitoring loop disappears. It must be replaced by structured, machine-readable condition intelligence. CoatingPassport is that replacement, by construction.

The Remote Operations Center needs structured data, not PDFs

Massterly's Remote Operations Center in Horten monitors Yara Birkeland + the ASKO autonomous feeders. A ROC operator overseeing a fleet cannot read PDF survey reports per vessel. They need a structured condition object per asset, queryable, diff-able, drift-aware. CoatingPassport + the diff + VQA endpoints are built for exactly that console.

Biofouling hits autonomous electric ships harder

Yara Birkeland is electric. Biofouling increases hull drag; drag drains battery range. On a crewed diesel vessel fouling is a fuel cost — on an autonomous electric vessel it is an operational-range constraint. Structured biofouling assessment is mission-critical, not just compliance.

Condition-based class survey is where DNV is heading

DNV's AROS class notations and its stated direction — use condition monitoring to focus surveys on risk areas instead of fixed scheduled surveys — require a structured condition input. CoatingPassport is that input. The autonomous-vessel survey regime and Hullproof's data product are converging.

VLA closes the autonomous loop

An autonomous vessel that detects its own condition defect and triggers the next action — route to the ROC for closer inspection, schedule a hull clean, flag for the next port call — is the Vision-Language-Action loop. Hullproof's VLAProvider interface is the seam where finding becomes action, co-developed with the operator.

Defense USVs have the same gap

US Navy medium USVs (Seahawk, Sea Hunter), HII ROMULUS, Textron Multi-Mission USV — uncrewed by definition. Hull machinery + electrical condition has no human to watch it. The dual-use condition layer serves naval USVs and civilian MASS on one schema.

The IMO MASS Code runway

The same pattern as the IMO biofouling regime: a non-mandatory code now, a mandatory one by the early 2030s. The operators and tooling that build the structured-condition muscle during the Experience-Building Phase are the ones positioned when it turns mandatory.

  1. May 2026 — MSC 111

    IMO adopts the non-mandatory MASS Code. The 10-year runway to mandatory autonomous-ship standards begins.

  2. Dec 2026 — MSC 112

    Experience-Building Phase (EBP) framework developed.

  3. 2026–2028 — EBP

    Operators run autonomous vessels under the non-mandatory code; insights feed the mandatory code. Condition-monitoring evidence is part of what regulators will want to see.

  4. 2028

    Development of the mandatory MASS Code begins.

  5. 1 Jul 2030

    Mandatory MASS Code adopted.

  6. 1 Jan 2032

    Mandatory MASS Code enters into force.

Edge resilience has two layers

A crewless vessel has to keep deciding correctly when shore connectivity drops and when its own signals can no longer be trusted. The 2024–2025 GNSS-spoofing incidents — 117 vessels falsely placed at Beirut airport, the MSC Antonia grounding off Jeddah, the Front Eagle collision near Hormuz — proved the point. Edge resilience is two distinct layers:

Signal-integrity layer

Is my position real? Is my GNSS / AIS / network feed being spoofed? This is a cyber-physical, RF-domain problem — a specialist field, and not what Hullproof does. Dedicated maritime-cyber players own it.

Condition-integrity layer

Is my hull sound? My coating, my structure, my biofouling — degrading toward a failure no one is aboard to see? This is Hullproof. CoatingPassport is the condition-integrity layer, edge-deployable per CLAUDE.md §10E.

An autonomous vessel needs both, and they are complementary, not competing. Hullproof stays disciplined: we are the condition-integrity layer and a structured input to whatever vessel-decision-support system sits above. We do not build navigation, cyber, or signal processing — that focus is itself the future-proofing.

Norway is the proving ground

Hullproof is a Norwegian company in the country that leads world autonomous shipping. The ecosystem is on our doorstep:

  • Yara Birkeland + ASKO feeders — the world's first autonomous electric container vessels, operating now.
  • Massterly Remote Operations Center, Horten — fleet-monitoring console that needs structured condition data per vessel.
  • Kongsberg Maritime — autonomous-shipping systems; already a Hullproof target (see /for/kongsberg).
  • NTNU Maritime AI institute, Trondheim — launched Jan 2026, Research-Council-funded, focused on the software-defined vessel. CoatingPassport is the condition data layer of a software-defined vessel.
  • DNV — AROS class notations + condition-based survey direction. See /for/dnv.

For autonomous-vessel programs

Operators, ROC builders, autonomous-shipping system integrators, and naval USV programs — the condition-intelligence layer is platform-tier, co-developed with your autonomy + assurance team. The vessels are being built now. The condition layer should be specified into them, not retrofitted.