MarineIT / Products / Platform
The architecture
One record, from first message to settlement.
Where the data lives
Nothing moves between anything.
A circular arriving this morning and the voyage it becomes are not two copies kept in step. They are the same cargo, vessel, counterparty and rate rows, read at different points across the eight stages.
The practical consequence is that a fixture cannot drift out of agreement with the thread that produced it, because there is only one of it.
Integration is what you need when two systems disagree. We removed the disagreement instead.
The circular you read at 08:14 is the fixture you settle in November.
Not copied into it. Not synced with it. The same record, from the first message to the final claim — which is why there is no connector, no nightly sync and no integration project.
The enquiry
Most of a chartering day happens before there is a voyage.
A cargo enquiry, open tonnage, a live negotiation — none of these are voyages, and many never become one. A system whose central object is the voyage has nothing to say about any of them.
The enquiry is a record from the first circular
It is created when the circular is parsed, accumulates estimates, counters and correspondence through the negotiation, and becomes a voyage when it fixes. Nothing is re-created at the point of fixture, because it was there all along.
Which means an unfixed cargo leaves a record too — the estimate that lost, and the terms that beat it.
What follows from that
Nothing is lost when a cargo does not fix. That is how a desk learns what it consistently prices wrong.
The fixture is not a data-entry event. When a cargo fixes, the voyage already contains everything the negotiation produced.
Your pipeline is real. Value and probability by stage, from live enquiries rather than recollection at a Monday meeting.
The difference this makes
Integrated versus native.
Every vendor can show you an email layer and a voyage system. The question worth asking in a demo is what happens between them.
An email layer and a separate VMS
- Extraction pushes data across a connector, on a schedule or a trigger
- Field mapping has to be configured, maintained and re-tested on upgrade
- Failed pushes are silent — nobody knows the voyage is stale until it matters
- Two vendors, two roadmaps, two support queues, two contracts
- The thread and the fixture can disagree, and often do
- Pre-fixture work lives outside both systems
MarineIT — one record
- Parsed values are written once, as the record itself
- No mapping layer exists to configure or break
- Nothing can fail in transit, because nothing is in transit
- One vendor, one roadmap, one contract
- A voyage and its correspondence cannot disagree — they are the same record
- The enquiry is a record from the first circular onwards
Questions worth asking your current vendor. Leaving a legacy VMS →
How it is built
Five layers. The record runs through all of them.
This is the current structure, not a target. What changes as the platform widens is how much sits inside the fourth layer — today, the dry bulk commercial chain.
What each layer is for
Command Bridge. The surface you work at — what needs attention, what changed, what to do next. Plain-language query is in development.
Communication Hub. Where everything arrives and is read before anyone opens it. Email and Teams today.
Agents and workflow. The machinery between arrival and action. It prepares work and routes it; a person decides.
Commercial ERP. The eight stages from Dialogue to Reports. Dry bulk today; tankers are the next build rather than a configuration option on this one.
Data platform. The one record underneath all of it, with every figure keeping its source and every override keeping the original.
One navigation across four desks, with forty widgets arranged by the people using them. See dashboards →
Design principle
Every screen answers four questions before you scroll.
The rule the whole product is held to, and the reason nobody on your desk should end up calling it complex.
What am I looking at?
What requires my attention?
What changed recently?
What should I do next?
The other question
One record is not the same as no integrations.
Nothing inside the platform needs a connector, which is the argument this page makes. Everything outside that boundary is a different matter, and worth being straightforward about.
Market data, registers and mailboxes are external by nature, and data from an existing platform can be brought across through API endpoints rather than re-entered.
Additional sources available on request, configured during onboarding.
Book a demo
See both halves in one session.
Bring a circular from this morning. We will parse it and build the estimate from what comes out of it — which is the only convincing way to show you there is no gap.
We reply within one business day.