SyncModule 06 · Connection layer
Synchronisation engineered for VSAT, not for office Wi-Fi.
Every vessel runs on its own local database. Changes queue as pending, transfer incrementally when a link is available, retry automatically on failure and are only marked synced after a positive acknowledgement from shore. Attachments upload straight to object storage with separate file and metadata acknowledgement.
Offline-first by design
- 01Zero lost work orders due to connectivity
- 02Lower bandwidth cost per vessel
- 03Shore sees vessel status as soon as the link allows
Capabilities
What Sync does
Local-first operation
The onboard application and database keep working through outages. Nothing on board waits for shore.
Incremental transfer
Only what changed travels — cursors and timestamps keep payloads small on expensive links.
Acknowledged commits
Pending records become synced only after a positive server acknowledgement, so a dropped connection never loses work.
Automatic retry
Scheduled cycles — work orders every 15 minutes, critical spares every 45, pending records and files every 60 — plus on-demand manual sync.
Separate file pipeline
Photos and documents upload directly to S3-compatible storage before their metadata, with independent acknowledgement states.
Conflict rules
Clear master vs. transaction ownership: shore owns master data, vessels own their operational changes, terminal states are protected.
Sync health on shore
Sync history, app installation reporting and release tracking show which vessel is on which build and when it last checked in.
Backward compatible
Older vessel builds keep syncing while new releases roll out — no fleet-wide big-bang upgrade.
How it flows
A closed, auditable loop.
- 1
Connected
Normal incremental synchronisation runs on schedule.
- 2
Interrupted
Local applications and database continue on board.
- 3
Recovered
Queued changes retry, validate and synchronise.
- 4
Consolidated
Central shore database becomes the fleet view.
Watch it work
Link lost. Work saved. Delivery confirmed.
An automatic demonstration of how onboard changes survive a connection loss and become synced only after shore acknowledges them.
Satellite link up
0 pending · 0 synced
Vessel connected
Automatic demo · 1 / 9
Vessel · local database
Shore · fleet database
› Vessel and shore are connected.
Outcomes
What changes for your fleet
- Zero lost work orders due to connectivity
- Lower bandwidth cost per vessel
- Shore sees vessel status as soon as the link allows
- Safe, gradual software rollout across the fleet
Frequently asked
What happens if the connection drops mid-sync?
Records stay pending on board until the server positively acknowledges them. The next scheduled or manual sync retries automatically — no data is lost and nothing is double-counted.
How much bandwidth does sync use?
Sync is incremental: only changed records travel, and attachments upload separately. It is designed for VSAT and other metered links.
How are vessel app updates delivered?
The desktop application ships signed updates per release channel, and shore can see which build each vessel is running.
See Sync on your own fleet data.
Book a 30-minute walkthrough with our team. We'll map your workflows, connectivity and data sources — and show you the platform live, including what happens when the link drops.