Core administration.
Document storage, cost tracker, maintenance schedule with engine-hours integration, crew permissions, NMEA-2000 device inventory from auto-discovery.
Platform · Boat Management
Insurance documents, registrations, survey reports, cost tracking, maintenance schedules, crew permissions, sensor inventory. All of it in one place, and all of it connected to the real operating data of the boat — engine hours, miles sailed, battery cycles.
What's covered
Most sailors manage this stuff across a mix of folders on iCloud, spreadsheets, and a few apps that don't know about each other. I built boat management to pull all of it together in one place that also knows how many hours the engine has run.
What makes it different
The maintenance schedule knows the engine has 212 hours on it because it reads from the NMEA-2000 bus — not because you typed it in. Oil change at 250 hours? The reminder fires automatically with a 20-hour warning. No manual logging of hours required.
The same is true for battery cycle counts from a Victron monitor, watermaker run hours, and generator runtime. Anything the bus reports becomes maintenance intelligence.
When I sell the boat, I want to hand the new owner a complete picture: the full log, every service record, every survey, all the receipts, the sensor inventory. That should be one export — not a frantic folder-gathering exercise.
The new owner imports it into their own 32°N instance and starts with the full history. Nothing proprietary, nothing that requires buying a subscription to access records about your own boat.
Access model
Boat management is the one part of 32°N that is owner-gated. Crew see what they need; you decide what that is.
When you add a crew member to the boat profile, you choose their scope: read-only on all apps, full access to nav apps but not management, or a custom set. Scopes are enforced at the platform level — individual apps do not manage their own access rules.
For a delivery crew or a charter, you create a temporary credential with an expiry date. It automatically revokes at the end of the delivery. No need to remember to remove someone from the boat's device registry.
Cost tracking and document storage are visible only to the owner by default. You can grant a specific crew member read access to specific document categories — for example, the first mate may need to see safety certificates. You decide.
Every write to the boat management data — a new maintenance entry, an updated document, a crew permission change — lands in the platform audit log. Structured, queryable, tamper-evident.
Roadmap
Document storage, cost tracker, maintenance schedule with engine-hours integration, crew permissions, NMEA-2000 device inventory from auto-discovery.
Full handover bundle: logs, surveys, maintenance records, photos, receipts. New owner imports into their 32°N instance. Portable format, no proprietary lock-in.
Agent observes usage patterns and flags upcoming maintenance before it becomes urgent — "watermaker pre-filter due based on run hours, not calendar." Proposals come to you as maintenance queue additions.
The demo lets you explore 32°N without any hardware. The platform page has the five-layer architecture — boat management sits in the apps layer, built on the same platform services as every other app.