The launch essay is live. Read it →
Pre-launch · Spring 2026

Ships run on data. APIs make it flow.

Maritime is not short of data. It's short of connections, shared vocabulary, and places where the people doing the work can compare notes. We're building one — a community, a knowledge bank, and a directory of solution providers, software, and consultants worth knowing.

The problem

Silos, not missing data.

The fuel figure, the port ETA, the berth schedule — they already exist. They sit inside systems that were bought separately and never taught to talk. Most maritime companies run five to twenty disconnected tools every day.

Reports capture what someone types into a form at the end of a shift. Events capture what actually happened, the moment it happened, with context and a timestamp. Most of the industry still runs on reports.

A number in a cell is useless without a schema behind it. Without DCSA's container definitions or IMO's just-in-time framework, "ETA" means something slightly different in every contract.

What can be done

APIs for flow. Events for reality. Open standards for meaning.

APIs let systems read and write each other's data without humans in the middle. The integration work is one-time, not per-voyage.

Event-based data replaces end-of-shift summaries with ground truth — emitted by sensors, engines, port systems — so decisions are made on what is, not what was remembered.

Open standards (DCSA, IMO JIT, port-call schemas) define what every field must mean. Once buyers and vendors agree on the shape, the silos come apart on their own.

What's at stake

Real numbers, not slogans.

  • ~20% fuel saving from just-in-time port arrival (IMO)
  • 14.16% average CO₂ reduction per container voyage with JIT (LCGIA)
  • 15% of shipping emissions happen in port areas (SINTEF)
  • 8–14% fuel reduction from voyage optimisation on integrated systems
  • 40% fewer manual data-entry errors with integrated systems

Every figure cited. References published at launch.

What we're building

Community. Knowledge bank. Directory.

A community where shipowners, operators, developers, and consultants talk shop without the trade-show veneer. A knowledge bank that writes down, once, the things every operator re-learns alone — decoded standards, shared playbooks, working examples. A directory of software, APIs, and consultants indexed by what they actually do, so a fit takes an afternoon, not a procurement cycle.

Not a vendor. Not a marketplace. An education platform that makes API literacy a standard skill in this industry — because when buyers know what to ask for, the products get better.

Join the waitlist

Tell us who you are and what you're looking for.

No spam. We'll reach out when there's something worth your time — early access, beta invites, and the occasional well-written dispatch.

What you're looking for (pick any)
We store only what you enter. One-click unsubscribe at launch.