Built on the PIMS baselineMarine operations, rebuilt for how ports actually work

The operating layer for your port.

Vessels, port calls, movements, services, resources, incidents and billing evidence — one connected record, from the pilot boarding ground to the invoice. It keeps working when the connection does not.

A port does not stop when the signal does.

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 offline-first by architecture, not as a fallback mode. Critical workflows read and write locally and reconcile when connectivity returns. 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.

Marine operations platform

One record, end to end. Vessel, call, movement, service, resource, incident and the evidence behind the invoice — connected, not stitched together from separate systems.

Operations command centre
Exceptions first. Delayed moves, active incidents and unassigned services get their own lane, because in a port the exceptions are the job.
Port calls and visit plans
The PIMS visit model, kept intact: standard, dead and transit calls, thirteen voyage statuses, checks and requirements gating every move.
Berth planning
A occupancy timeline that detects overlaps, draft breaches and length breaches before the vessel arrives — and states them in words, not just colour.
Marine services and resources
Pilotage, towage, mooring, bunkering and the rest, from request through to billable — with the tugs, boats and crews assigned against them.
HSE and incidents
Incident recording with severity, risk scoring, investigation and corrective actions. Records are evidence, so nothing is destroyed irreversibly.
Reporting and analytics
Every PIMS report by name — arrivals, berth usage, manoeuvring time, hazardous cargo — plus turnaround, delay analysis and service utilisation.

The copilot cites its sources. Always.

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, draft and history.

Service dispatch

Eleven lifecycle states, four working queues.

Multi-portOne tenant, every port you run.

Pricing that scales with the port, not the seat count

Start with a single port and add more as you grow.

Value
Starter
The perfect plan to get started
$9.99/month
Billed monthly
  • Feature 1
  • Feature 2
  • Feature 3
Popular
Pro
The perfect plan for professionals
$19.99/month
Billed monthly
  • Feature 1
  • Feature 2
  • Feature 3
  • Feature 4
  • Feature 5
Enterprise
The perfect plan for enterprises
$29.99/month
Billed monthly
  • Feature 1
  • Feature 2
  • Feature 3
  • Feature 4
  • Feature 5
  • Feature 6
  • Feature 7