About

It shares a codebase and a database with two other sites: Regatta Pages, which runs and scores regattas, and Saildex, which publishes results and ratings. They exist together because a race organiser, a competitor and a navigator all end up needing the same underlying data, and keeping one copy of it correct is easier than keeping three.

The routing is a standard isochrone search. What is less standard is where it runs. The server prepares the forecast, and the search itself happens in the browser using SharedArrayBuffer across as many workers as the machine has cores. That is why the site sets COOP and COEP headers on the workspace, and why the workspace loads as its own document rather than as another page here.

Boat performance comes from an ORC certificate, a polar table you paste in, or a polar you have saved to your account. A pasted polar is sent to the browser in a single no-store response and held in memory for the session — never logged, and never written down unless you save it. A saved polar is stored under your account alone, and is never shared or read for anything beyond preparing your own routes. Either way, routes carry only the polar's digest.

What is being built

Accounts, saved routes, and paid plans ship today. Server-side solving is built and not yet switched on: it is for people who want consistent performance on any device, a validated result, or routing that continues with the tab closed. The browser solver will stay the default.

Bug reports and complaints go to the same inbox the code was written in.