Every failed check stays in sight until the work is done.

Vessels, safety inspections, work orders and shift handovers for a fleet, in one audited workspace.

Try the live demo as

Password for every role: ShipShape2026

The accounts are shared, so you may see other visitors' changes.

A portfolio project by Johnmark Enriquez, with synthetic data. Not a certified maritime safety system.

Aegir dashboard for Northwind Shipping: five fleet figures, with 2 inspections and 2 work orders overdue and 1 blocked, above the work queue and inspections due. — The dashboard in the live demo (synthetic data).

One failed check, followed to the fix

What happens to a safety finding in Aegir, shown in the demo's own screens. Each role sees the part that is theirs.

The inspector records it on deck
On a phone, check by check: pass or not applicable in one tap. A failure needs a finding and a severity, and it stays flagged until work is raised for it.
FailCritical severityNeeds follow-up
Full size (opens in a new tab)
The fix becomes a work order
Raised from the failed check and linked back to it. Assign it, set a priority and a due date, then start it, block it with a reason, or complete it. Every move goes into its history.
Critical priorityBlockedOverdue
Full size (opens in a new tab)
Unfinished work is handed over
At shift change, the outstanding tasks go to a named colleague, who acknowledges them. Here the night shift hands the isolated fuel pump to the day's technician. A handover can't be edited once it's sent.
For youPendingAcknowledged
Full size (opens in a new tab)
The manager sees the whole fleet
The dashboard and the vessel watch list put critical, blocked and overdue work first. Every figure is current when the page opens; nothing waits for a weekly report.
1 critical1 overdue1 blocked
Full size (opens in a new tab)

On deck and at the desk

One shared record for everyone who touches a finding, each on the screen that suits where they work.

Safety inspectorOn deck, on a phone: Records each check where it is. Every control is at least 44px tall, and a failure can't be saved without a finding and a severity.
TechnicianBetween jobs: Sees the jobs assigned to them, starts one, blocks it with a reason when a part is missing, and hands what's left to the next shift.
Fleet managerAt the desk, or anywhere: Sees critical, blocked and overdue work first across the fleet, then assigns it and sets priorities and due dates.
Auditor or stakeholderRead-only: Follows everything, including who changed what and when, and can't change anything.

The same dashboard on a phone: the figures stack into one column above the work queue. — The manager's dashboard on a phone.

Records you can stand behind

Safety records are only useful if nobody can quietly change them. Aegir enforces that in the system itself, not in good intentions.

Your company's records stay yours: Another company on the same system can never see or change your vessels, inspections or work. The demo has a second company, Meridian Tankers, only to prove it.
Every change is signed and dated: Who changed what, and when, is recorded automatically. Nobody can edit or delete an entry.
The rules can't be skipped: A work order can't jump from open to completed, and safety records can't be deleted, whichever screen or script tries.
Handovers can't be rewritten: Once sent, a handover is fixed. Acknowledging it records who read it and when.

How each of these is enforced, for engineers

The audit log, grouped by day: each change names the record, what changed and who made it. — The audit log in the demo: the night shift's handover acknowledged, and the fuel pump job blocked with its reason. Entries from the demo's sample data are signed “System (seed data)”.

What it replaces, and what it doesn't do yet

Instead of findings scattered across spreadsheets, email threads and paper checklists: one record per finding, from the failed check to the finished work.

In this version

Vessels and a watch list that puts the ones needing attention first
Inspections with checklists, findings and severities
Work orders raised from failed checks, with a reason whenever work is blocked
Shift handovers that the recipient acknowledges
A dashboard of what's overdue, blocked and waiting
A complete history of every change
Works on a phone, a tablet and a desktop browser

Not in this version

Photo and file attachments
Email or push notifications
Exports and reports
Offline use at sea, or native mobile apps
Self-service sign-up, single sign-on or two-factor sign-in
Screens to manage users and companies (the demo's are set up for you)

The checklists are examples, not official templates. Aegir is a portfolio project with synthetic data and is not certified for the ISM Code, SOLAS, flag-state or class requirements.

Try it as each role

Four people at Northwind Shipping, a made-up company with synthetic data. Each link opens sign-in with their account filled in and the password shown. Here is a first thing to try as each.

Fleet managerMarcus Reyes
Open Northwind Fjord on the watch list and see why it's flagged, then assign or reprioritise its work.
marcus.reyes@northwind.example
Sign in as Marcus
Safety inspectorIngrid Solberg
Finish the monthly fire safety audit on Northwind Halcyon: fail a check, then raise a work order from it.
ingrid.solberg@northwind.example
Sign in as Ingrid
TechnicianTomas Okafor
Start the oily water separator alarm job on Northwind Fjord, then block it with a reason.
tomas.okafor@northwind.example
Sign in as Tomas
ViewerVera Lindqvist
Open the audit log and follow who changed what. Try to change something: you can't.
vera.lindqvist@northwind.example
Sign in as Vera

Safety records can't be deleted, by design, so you may find other visitors' work in the demo. The administrator account isn't published.

Want this for your fleet?

Aegir is a working demonstration built by Johnmark Enriquez with synthetic data. If your crews need something like it, shaped around how they actually work, let's talk.

Talk to Johnmark on LinkedIn