Engine Room Holding Tanks

Set this up once for each vessel. The entry assistant offers these tanks when you log an operation.

Cargo & Slop Tanks

Only oil tankers need this. Leave it empty for any other type of ship.

Fuel Types Management

The fuels and lubricating oils this vessel is certified to carry and bunker.

Overboard valve seals

Record the seal already fitted to the overboard valve when this vessel starts using the electronic book. Without it, the first Code I "Unsealing of overboard valve" entry has no seal to break.

Vessel snapshot

Tank status

🔒 Ledger integrity (tamper-evidence)

Each signed entry is locked to the one before it with a SHA-256 fingerprint. Re-checking the chain here will show you whether any entry was changed after it was signed.

Data archive

Export writes everything you can see — fleets, vessels, tanks and every Oil Record Book entry — to a single JSON file, generated by the server. Keep it as an offline archive of the record.

Restore reads only the fleets and vessels from such a file, to re-create them on a new installation. Entries are never written back: a signed entry belongs to the hash-chained ledger and can only be created through the Oil Record Book itself.

Audit trail — scoped to what your role can see

Companies (platform level)

💳 Billing & Subscription

This deployment cannot and does not process real card payments unless Stripe/Razorpay secret keys are configured in the server's environment (see the deployment guide) — no secret key ever belongs in browser code. With keys configured, "Subscribe" redirects to a real Checkout session; a subscription only activates once the gateway's webhook confirms payment, never from the redirect alone. Without keys configured, the server returns a clear error and a platform administrator can activate a plan manually instead (e.g. for an invoiced payment).

Fleets

Vessels

Users, roles & access scope

Create a user