The same information shouldn’t need to be handled several times
Voyage, cargo, operational and documentation data is often handled in several different places. Information that already exists may need to be entered again in logs, documents, spreadsheets or shore-side reporting.
OceanLogix is built around a simple principle: Record information as part of the work onboard and reuse it throughout the rest of the workflow.
We’re getting OceanLogix ready for its first pilots
The first version of OceanLogix Vessel is nearing completion. The next step is to test it against how more tanker vessels and operators actually work.
That’s why we’d like to talk to people working onboard or with tanker operations ashore.
Vessel MVP
Industry validation
Onboard pilot
We start onboard
OceanLogix Vessel is the first part of the system. The goal is for information already recorded during onboard operations to also be used for documentation, history and by the office ashore – without entering the same information again.
Vessel Operations
This includes voyages, trips, cargo, loading, discharging, operational logging and documents in the same onboard workflow.
Office
Information already recorded onboard should be available to the office ashore without separate reporting and duplicate data entry. OceanLogix Office is the next step towards that.
Port Knowledge
Over time, OceanLogix should also be able to collect structured knowledge about ports, terminals and berths and reuse experience from previous calls.
Our Key Features
OceanLogix Vessel follows the actual work onboard, from voyage and cargo to logging, documents and history.
Voyage & Cargo
Keep voyages, trips and cargo together in the same workflow. Information stays connected from the start instead of being spread across several different places.
Loading & Discharging
Log loading and discharging against the current cargo and voyage. Events and operations stay in the same flow while the work is happening onboard.
Operational Logging
Record relevant events as part of the operation while it is happening. Logging becomes part of the work itself instead of a separate step afterwards.
Documents from the same data
Reuse information from the operation when preparing NOR, Statement of Facts and other documents. The same details should not need to be entered several times.
History & Traceability
Keep structured history of voyages, cargo, operations and changes. What happened should still be easy to follow after a voyage has been completed.
Offline-first
OceanLogix keeps working onboard when the internet is missing or unstable. Work continues locally and sync happens when connectivity is available.
About Us
We are two lifelong friends with a shared passion for innovation and improvement. One of us is a Chief Officer on oil tankers, the other an IT consultant. Together, we’ve combined our experiences to create a tool that simplifies bridge operations—starting with oil tankers.
The shipping industry is still in its early stages of digital transformation, and we want to be part of that change. Our focus isn’t on flashy technologies or lightning-fast servers, but on practical, meaningful improvements that reduce paperwork and make everyday tasks more efficient.
What sets us apart is our philosophy: small, steady steps can lead to big changes. Through collaboration and a constant drive to learn, we’ve gained a deep respect and fascination for each other’s industries. OceanLogix is the result of that shared curiosity and dedication.
Do you work with tanker operations?
We’d like to talk to more people working onboard or ashore and hear how you handle voyage, cargo, logging and documentation today. If you want to see what we’ve built, we’d be happy to show you.