Products

Three products. One port-call record.

The pilot's tools, the clearance engine and the screening service are three views of the same record. Each is listed with what it does today and what it is proven on — not what it might do.

Live beta · Melbourne & Geelong

Pilots — the Nāvika suite

Pilotage software built by a working marine pilot, for the pilot on the bridge and the people who run the service. Offline-first: the core — plan, under-keel clearance from embedded data, checklist, signatures, PDF — works with no signal at all.

  • MPX — the Master/Pilot Exchange: passage plan, UKC and tide window, tugs, checklist, signatures, PDF; sent to the ship for review before boarding.
  • OPS — the coordinator's allocation board, synced to the port's movements; push to MPX.
  • e-CHIT — the signed pilotage service record, audited and exportable.
  • CREW — licensing, currency, inductions, duty and rest.
  • Fatigue — an operational FRMP score (duty + night, against the port's limits) beside a simplified biomathematical prediction.
  • Evidence — every app writes a hash-chained audit trail, anchored off-site; an audit console verifies and exports it.

Who it is for · what it costs

Pilotage providers, and ports with in-house pilotage.

A port is onboarded as a profile assembled from its own published data — berths, routes, channels, tide stations, UKC rules. Two profiles exist today: the Ports of Melbourne and Geelong, and Singapore. Per pilot per month, with a one-off port onboarding. Founding customers get a stated discount in exchange for a reference.

Proven on: live pilotages since June 2026, with the feedback log driving the changes.

In testing · a national maritime single window

Port calls — the clearance engine

A digital ship agent on the authority's single window. The master sends the figures and documents from their own interface — offline if need be; the engine assembles the port call from the authority's feeds and the ship's record, drafts the declarations to the authority's own field specification, screens them, and stops for a person to confirm. Then it keeps the evidence.

  • Three role pages on one record — the Master's pack, the Owner/Operator/Agent's queue and call page, the Filing narration.
  • The whole call — pre-arrival notification, arrival declaration, amendment, departure declaration; each leg filed automatically once confirmed by a human in the loop.
  • A ledger — an identical filing is never sent twice; a retry becomes a lookup of our own record.
  • The clock — every obligation as a countdown from the declared times, met only by an accepted filing according to the port's requirements.
  • The voyage on the record — required speed against speed over ground, projected against declared arrival, fuel and CO₂ for the leg with the assumption printed; a drift proposes the amendment.
  • The record the ship carries — an open, portable port-call record: the ship's figures, documents and filings, re-opened at the next port.

Who it is for · what it costs

Ship agents and operators, per port call. Port authorities, as the agent-facing layer of their single window.

Priced per declarable port call — the unit everyone in the chain already pays by — with a founding price for the first agencies. For an authority or port-community operator: a platform licence per port, hosted or on their own infrastructure.

Proven on: a national maritime single window's test environment — pre-arrival notifications accepted on real hulls, the full four-leg port call filed as one human-confirmed run; every refusal recorded and explained. Not yet: production access — that is the authority's decision, and the engine is ready for it.

Live · the Singapore & Melbourne fleets

Screening — before she arrives

Every vessel due at the port, screened before it matters: against the OFAC, DFAT, UK and UN sanctions lists; against port-state-control detention and deficiency history from the PSC MoUs; and against her own AIS behaviour — a flag change, a name change, going dark, an impossible jump.

  • A dossier per vessel — sanctions, detentions, deficiencies, flag and recognised-organisation performance, behaviour flags, feed freshness — with the source of each line.
  • Inside every filing — the screen is recorded in the declaration's evidence as it stood at the moment of filing.
  • A fleet map — sanctioned hulls red, PSC-flagged amber, click for the dossier; the same view inside the 3D port twin.

Who it is for · what it costs

Port authorities and harbour masters first; the agent's clearance desk through the engine.

The duty to refuse a sanctioned hull — and the embarrassment of learning from the press — belongs to the port. Per port per month, with the digital twin as the view. Agents get the same screen on every filing as part of the clearance engine, not as a separate purchase.

Proven on: the live Singapore and Melbourne fleet, 24/7, with 3,700+ PSC records and 2,600+ sanctioned hulls indexed and watched for staleness.

Open

The shapes are free. That is the point.

A port call that any system can read is worth more than one that only ours can.

Record

The port-call record

What a ship carries between ports: her figures, documents and filings, with provenance. Re-opened at the next port.

Profile

The port profile

A port as a file — berths, routes, channels, tide stations, UKC rules — assembled from its own sources. Onboard a port, not an integration.

Rules

The rule tables

The declaration field maps measured against the authority's validator; the deadline windows with their sources, and whether each has been verified.

Fatigue

The fatigue engine

The operational FRMP score and the simplified biomathematical model, with every caveat, as a library. Publication pending the paperwork.

Which one is yours?

Tell us who you are — we'll show you your view.

A pilotage provider, a port authority, a ship agency, a line. One conversation, the right product, a live walkthrough.