A pilot boarding a vessel, a mooring gang on a quay, a duty officer in a blackout — all of them still have to record what happened, and the record has to be trustworthy when it arrives.
Censerva is being built for exactly that. Today, when the signal drops mid-movement, the checks, start and finish recorded on the device are held there and sent when it returns, against the same rules the server applies. Other records still need a connection to save. And because a write that has not reached the server is never shown as confirmed, an operator always knows exactly what is recorded and what is not.
Synced
Confirmed by the server.
Pending sync
Queued. Not yet confirmed — and never shown as if it were.
On this device
Saved locally while offline. Visible at a glance.
Conflict
Changed elsewhere meanwhile. You decide, not last-write-wins.
Ask what is delayed, what is arriving, which services are unassigned or what hazardous cargo is in port, and you get an answer drawn from your own operational records — with a link to every record it used. Where the records do not support an answer, it says so rather than guessing.
It never originates a vessel position, a time, a service or an incident. That is a property of how it is built, not a promise in a prompt.
Command centre
What needs you, ranked above what does not.
Live map
Vessel positions with their source and age, always shown.
Vessel register
IMO, MMSI, callsign, tonnage and draft.
Service dispatch
Eleven lifecycle states, four working queues.
Censerva is set up for each organisation rather than opened by self-service sign-up, so every account starts from an invitation.
Get in touch with the port or terminal you run and what you want Censerva to cover.
Your organisation is set up in Censerva and its first owner is invited by email.
The link in that email creates your sign-in. There is no public sign-up form to fill in.
Add the rest of your team from Members, each as an owner, a member or a read-only viewer.