Why a foundational routing model matters
The shipping industry routes around 50,000 commercial voyages a day. Most of them still leave port with a single rhumb-line plan, a 24-hour-old weather download, and a charterer's spreadsheet that hasn't been updated since the cargo was loaded.
The result is a quiet, systemic waste: an estimated 4–11% excess fuel burn per voyage, billions of dollars in unrecoverable demurrage, and an audit trail that — when challenged — collapses into screenshots and email threads.
VesselFront's engine is built on the premise that routing should be foundational infrastructure, not a SaaS add-on. Every prediction is paired with the source data that produced it. Every voyage closes with a signed claims report. The output of POST /voyage/optimise is something an insurer, a charterer, and a master can all read without translation.
This isn't about predicting the weather better. It's about producing routes that survive contact with reality — and proving it, voyage after voyage.