What Pruva is
Twenty modules for a ship operator, from the fleet map and the noon report to finance, vetting and the insurer.
Pruva is the operating record for a fleet. Twenty modules share one vessel, one port call, one part and one crew list. Six core modules are open core; a workspace buys a hosted package by how many Pro modules each vessel runs, and adds Safety Vision for the cameras. Each person has a level on each module: none, view, edit or publish.
The fleet map shows where every ship is and whether her health needs someone today. Predictive maintenance raises an alert when a component drifts toward failure, with a probability and the days left, for example 72 % within 9 days. Cameras add an explained still from the bridge, the deck, the engine room or a MARPOL watch. Noon reports carry the day’s position, speed and fuel. Emissions turns that fuel into CII, EU ETS, UK ETS and FuelEU. Insurance shows the risk score to the underwriter on the vessels the operator shares.
Around the port call sit the cargo files and the containers, the agent and the disbursement account, the purchase orders due, and the work orders. Planned maintenance holds the job card. Dry dock collects the class jobs into a specification. Inventory holds the spare. Procurement buys it. Finance posts the invoice. Certificates, HSEQ and vetting hold the compliance record. Crew holds who is on board, the STCW dates and the rest hours. Reports and dashboards only read the others.
Voyage performance and chartering are named and priced. Their screens are placeholders. Crew payroll is not built. The user guides say what each module does today. The module reference lists the pages, the connectors and the actions that need publish.
Who uses it
| Person | Role in Pruva | What they do |
|---|---|---|
| Fleet manager | Owner | Reads the fleet, decides what to do first, holds publish on every module |
| Technical superintendent | Admin | Runs alerts, jobs, port accounts, procurement and HSEQ |
| Chief engineer on board | Member | Completes jobs, reports incidents, raises spare requests |
| Master on board | Member | Files the noon report, reviews camera events, reads the port call |
| Emissions officer | Member | Tracks CII and submits the reports |
| Chartering and finance manager | Member | Funds a disbursement account and posts the ledger, when those modules are open |
| Marine underwriter | Member | Sees shared vessels, their risk score and the cameras |
| AI agent | Agent | Reads and drafts. Never holds publish |
The demo people and the exact level each one has are on The demo fleet.
What is in this build
- App on port 4400 with the module pages, running in demo mode with generated data.
- Marketing site on port 4410 with pricing and a demo checkout.
- These docs on port 4430.
- Local database mode with Supabase on ports 4420 to 4429, row-level security and seeded users.
Not in this build: live AIS or sensor connectors, real payments, real AI calls by default, voyage and chartering screens, crew payroll, and a public launch. Every connector is a mock.