What is built, and what is not yet
We keep the two apart. The right-hand column says plainly whether each part works today or is waiting on an outside service.
Live map
Berths and yachts are drawn from their real dimensions, so a 12-metre berth looks smaller than an 18-metre one and a yacht that is too long visibly overhangs. The map pans, zooms and searches, and works on a phone.
AvailableBuilt and in use in the demonstration marina.
Berth status rules
Each colour comes from a written rule checked against the booking and the yacht’s size: no booking, wrong berth, overstay, over the berth’s length, beam or draft, departure due today. You set the thresholds.
AvailableBuilt. Checked by automated browser scenarios against the running system.
Bookings and allocation
The server checks every booking for a clash, a closed berth and a yacht that does not fit, and refuses or asks for a manager’s reason. The berth is locked while it is checked, so two bookings made at the same moment cannot both be accepted.
AvailableBuilt. Clash, closed-berth and fit checks are tested against a real database.
Real-world position
A marina is given a latitude, longitude and bearing, and every berth gets an outline in standard GeoJSON coordinates that any map or GIS tool can read.
Not completeBuilt: placement and GeoJSON export. Satellite imagery under the plan needs a map provider account and is not connected yet.
Vessel tracking (AIS)
A server-side connection to an AIS data feed is written, so the key never reaches a browser. AIS covers ships and larger yachts; many small leisure boats do not transmit it.
Not completeBuilt and tested against a stand-in feed only. Not connected to the live service. The demonstration shows a clearly labelled simulated feed.
Notifications
Alerts appear in the system as soon as a rule is met.
Not completeEmail and SMS delivery are not connected.
Online payment
Plans and subscriptions are recorded per customer.
Not completeNo payment provider is connected. Nothing is charged through the system.
Data security
Separation by customer
PostgreSQL row-level security on every customer table. Even a missing filter in our own code cannot return another customer’s records.
Our staff’s access
Our administrators see only totals. To look inside an account they must open a session for that one customer, read-only unless they give a written reason. It lasts 60 minutes, shows a banner throughout, and is recorded.
Sign-in
Passwords are stored hashed (bcrypt). Sessions use httpOnly cookies, with rate limiting and a temporary lock after repeated failures.
Audit trail
An append-only log of sign-ins, bookings, overrides, settings changes and support sessions, with who and when.
Roles
Owner, manager and employee permissions are enforced by the server, not by hiding buttons.
Secrets
Keys for outside services are held on the server and never sent to a browser.
We do not hold third-party security certifications, and the system has not yet had an independent penetration test. Both are planned before general availability.