Problem
Service info lived across invoices, photos, and emails; IDs were inconsistent.
2024 – 2025
VesselDB — Maritime Vessel Database
Built a lightweight webapp to track vessels, onboard systems, service history, and parts—optimized for fast field lookup.
- Data
- Postgres/Supabase
- API’s
- RBAC
Results at a glance
Results that mattered
A snapshot of the results and changes across operations, adoption, and team experience.
- Lookup time
- Minutes → seconds
- Technicians found vessel and system context quickly using indexed text search.
- Tables
- ~40
- Normalized schema for vessels, systems, service logs, parts, vendors, and documents.
- Access control
- RLS per org
- Row-level security and role-based access across organizations.
Approach and execution
What I did
What I did
Modeled the domain (Vessel, Owner, Berth, System, WorkLog, Part, Document); implemented Postgres/Supabase with RLS and roles; built CSV importers with dedupe rules (name+MMSI/IMO/HIN similarity); exposed read-optimized endpoints and text search; added migrations, nightly backups, and integrity checks; linked photos/diagrams to systems.
Outcome
Lookups dropped from minutes to seconds; consistent IDs and cleaner history sped up field work and quoting.
Stack
Postgres (Supabase), SQL migrations, Python/FastAPI glue.
My role
Solo builder from requirements → ERD → schema → importers → API → docs.
Interested in similar results?
I’m available for full-time roles or contract engagements—let’s discuss how my hands-on approach can help your team.