How the software is built, released and hosted
The six product lines ship as one application stack. What follows applies across recruitment, onboarding, accounting, reporting, scheduling and containers, and it is the part most maritime vendors leave to a sales call.
Application and delivery
Code-signed releases
Every released artefact is code-signed before it leaves the build pipeline. Shore installs, vessel packages and update bundles carry a verifiable signature, so operators can confirm the binary they run is the binary Seafarerops published and not a copy that changed in transit. This matters more at sea than ashore, because a vessel package often travels over a link and a medium nobody fully controls.
Security in the codebase
Security practice is treated as part of the product rather than a wrap-around. The codebase follows current secure development practice: controlled dependencies, review of privileged paths, least-privilege service access, and handling of crew and owner data as regulated maritime records rather than generic application data.
AI inside the products
AI integration is available across the product line. It is used where it shortens a desk or a bridge task: reading a document pack, surfacing a missing certificate, drafting a routine exception. It does not replace the Master's or the manning desk's decision, and the core record never requires a live satellite link.
Cloud team and infrastructure
A trained team operates the shore side on cloud platforms. Production infrastructure is hosted primarily on Amazon Web Services, with DigitalOcean used where that footprint fits the customer. The same team designs the offline vessel runtime, so the ship keeps working when the cloud is unreachable.
The offline architecture, in plain terms
Store-and-forward is not a feature bolted onto a cloud application. It is the shape of the data model.
Work completes locally
Forms, packs and wage inputs are written to the vessel's own store. The officer finishes the task; the link is irrelevant to whether it is done.
The queue carries state
Each item holds a visible pending or synced state with a timestamp. Nobody has to guess whether yesterday's noon left the ship.
Replay is ordered
When a window opens the queue drains oldest first. Conflict rules apply where shore has edited the same period, instead of a silent overwrite.
Snapshots are frozen
A released joining pack or rotation is a timestamped snapshot the vessel can open with no live connection. It is either complete or it names what is missing.
Shore separates confirmed from last known
The fleet view reports the last confirmed timestamp per vessel. A stale figure is labelled stale rather than rendered in green.
Sync is medium agnostic
VSAT, harbour wifi, a 4G burst alongside, or a USB drop. The queue does not care which window it gets, only that the order holds.
Data, security and the questions procurement asks
Crew records are personal data, and in this domain they include medical and financial detail. We would rather answer these in writing than in a fourth call.
Where data sits
Shore infrastructure on Amazon Web Services, with DigitalOcean where that fits the customer. Region is agreed during assessment, and data residency preferences are part of that conversation rather than an afterthought.
Vessel side
A local runtime holds the queue and the released snapshots. It is designed for the constrained, locked-down machines vessels actually run.
Access and audit
Role-based access across shore, vessel and principal. Adjustments in the wage ledger carry a reason, an actor and a timestamp.
Regulatory context
The record set is built around what MLC 2006, STCW, flag state and PSC obligations actually require of a manning office and a vessel, rather than a generic document library with maritime labels.
Start with a complimentary assessment
A working session against your fleet, flag mix and manning model. We map where you are today, where the record breaks, and what an honest roadmap looks like. No charge, and no obligation to go further.
What you leave with
- A map of where crew, wage and report data currently breaks
- Which module earns its place first, and why
- A staged roadmap with a proof of concept scoped to one area
- An indicative cost envelope before you commit anything