Roadmap

What is next — and who decides it.

Published so you can hold us to it. Each item says what has to be true for it to happen, and whose decision that is. No company counts, no turnaround percentages — those are outcomes, not plans.

Now

Prove the whole port call in a test environment

Every write path exercised against a national maritime single window's test environment — notification, declaration, amendment, cancellation, departure — with the evidence recorded. Done for what the test environment allows; the remaining questions are with the authority.

Next · the authority's decision

Production access on the single window

The one gate between a proven engine and a product with a meter. When granted, the first Singapore agencies file through it on founding terms.

Next · ours

The engine as a service others can call

A remote transport and keys on the MCP server, so an agency's own system or an authority's platform can call it directly; the voyage and the clock as subscribable events, so an agent is told rather than polling.

Next · ours

Publish the shapes

The port-call record, the port-profile schema, the rule tables and the fatigue engine, under Apache-2.0 — the standard that lets a pilotage system, an agency system and an authority's platform read the same call.

Then · a second pilotage provider

The suite at a second port

Onboarded from its own data as a profile, as Singapore and Melbourne were. The price is set to earn the first reference, not to maximise it.

Then · Australia

The same engine, an Australian adapter

Australia has no single window yet. The port call a ship makes between Singapore and Melbourne, one record end to end — the ship carries it; each port reads it.

Founding customers

Be first through the engine — on founding terms.

Singapore agencies and operators; pilotage providers anywhere. A stated discount for a reference, nothing else asked.