Plan limits
| Anonymous | Free | Credits | Pro | |
|---|---|---|---|---|
| Automatic fidelity | Standard data | Standard data | All available data | All available data |
| Course length | 60 nm | 150 nm | Any passage | Any passage |
| Route duration | 24 h | 48 h | 16 days | 16 days |
| Departure scans | 1 | 3 | 24 | 24 |
| Models | GFS | GFS | All | All |
| Route retention | 7 days | 30 days | 90 days | 1 year |
| Projects | — | by invitation | by invitation | Yes |
Credits and Pro are capped at 12,000 nm and 384 hours, which is effectively unlimited: the course cap is a ceiling above any real passage (more than half the earth's circumference), there to keep a sane error message for nonsense input, and the duration cap is GFS's own 384-hour forecast horizon, not a number chosen to constrain you. A passage longer than that is accepted and returns honestly, with the route continuing only as far as the forecast does.
Inside a project, the limits are the project's
Starting a project is a Pro feature. Working as an editor on one is not: an invited editor can draw courses, add boats and run routes there, whatever they pay us. A viewer is read-only and does not borrow the project owner's routing limits.
The limits that apply are the project owner's. A navigator on the free tier, invited to help plan an offshore race, gets that project's models and horizon while working inside it — the alternative is inviting somebody to help and then handing them a 150-mile ceiling on a 300-mile race.
Outside that project, their own plan applies exactly as this table says. See projects.
Solving is never limited
No plan caps how many times you compute a route, how long a search may run, or how often you change your mind. Change the departure, the course, or a constraint and compute again — none of that is metered. There is no fidelity picker: each request uses the strongest forecast data its plan allows.
What a plan sets is the size of the problem: how much ocean, how many hours, how many starts, and which models. Those determine how much forecast data has to be fetched on your behalf, which is the part that costs anything to provide, and so it is the part that is priced.
Going over one
A request over a limit is refused, and the message says which limit and by how much. It is never quietly trimmed to fit, because a silently altered request answers a different question than the one you asked.
Retention
When retention runs out, the share link starts returning "expired" rather than "not found", so someone opening an old link is told what happened. Export the route beforehand if you need to keep it.