nausika

roadmap

Roadmap.

Last updated

Nausika exists so that your AI assistant — Claude, ChatGPT, Cursor, anything that speaks the open MCP protocol — can reach real maritime data: weather and waves, tides, places, sea routes, your own boat. One connector, one consent screen, one source of truth. The roadmap below is the path from "useful" to "indispensable for anyone planning a passage with an AI assistant."

A roadmap is a living document, not a contract. Concrete dates harden as we approach them; further-out items are directional. When something slips or gets cut we say so on /log.

What your assistant with Nausika can do today

Every conversation with a compatible AI assistant already gets these capabilities, live in production.

  • Plan a sea passage that avoids land. Genoa → Bastia (106 nm), Naples → Palermo (169 nm) computed in well under a second, on the curated Mediterranean sea-route network.
  • Know what the sea is doing before you leave. Wind, waves, currents, water temperature, visibility, pressure, UV — up to 14 days ahead, anywhere in the world. For longer windows, a seasonal outlook up to 7 months.
  • Find real places with real photos. Marinas, anchorages, sheltered bays, lighthouses — each with attributed photos under open licenses. No AI-generated imagery.
  • Tell the assistant about your boat. Draft, beam, mast height, range: your boat profile filters anchorages and routes accordingly.
  • Keep favorites, saved routes, ratings. They persist across conversations and stay yours.
  • Connect your favorite AI assistant in one click. No secret to copy, no manual setup — works with claude.ai, Claude Desktop, Cursor, ChatGPT.

In flight now

Three concrete improvements aimed at sailors.

  • A sea route to any point on the coast. Today calculated routes hit major ports and marinas cleanly; smaller anchorages and isolated coves get snapped to the nearest node. We're extending the network so any place on the coast becomes a valid destination — the AI can plan a route to that off-the-beaten-track shelter too.
  • Lighthouses, towers, fortresses: the coast, told. A dedicated category for landmarks visible from the sea — historic lighthouses, watchtowers, coastal fortresses, cliff-side monasteries — with visibility range, seamark symbol, and Wikipedia linkage. So "what's that tower on the cliff?" gets the right answer instead of being forced into the wrong category.
  • Local tide stations beyond the US. Today, observed-station tide data covers only US coasts (NOAA); elsewhere the data is modeled. We're integrating European networks, starting with the Mediterranean, so "high tide at Venice" comes from a real station, not an estimate.

Geographic growth

Today: the Mediterranean, complete. Italian, French, Spanish, Balearic coasts, the Adriatic, the Aegean. Every place type — marinas, anchorages, shelters, lighthouses, fuel stops — with attributed photos, descriptions, and sea routes computable between any two points.

Already worldwide. Marine forecasts, tides, geocoding, coordinate conversion, distance calculator. Wherever you ask, the assistant answers — on these pillars.

Next area we open: the European Atlantic. Atlantic coasts of Portugal, Spain, France, the UK, Ireland. Same curatorial discipline as the Mediterranean: real places, sea routes that avoid land, photos under open licenses. The natural continuation for anyone crossing the Strait of Gibraltar.

Then, gradually. As the community grows, the other waters sailors frequent — Northern Europe, the Caribbean, the US East Coast, the South Pacific. The architecture is geography-agnostic; what changes is the pace of curation.

Looking ahead

Vision, not commitment.

  • Bunkering and provisioning. Where licensing permits: fuel availability and provisioning notes for marinas and equipped anchorages — so the AI can answer "can I bunker at that marina Tuesday morning?" before you pick up the phone.
  • Your data on top of the common data. For charter fleets, sailing schools, clubs: a private layer visible only inside your conversations — handover notes, school briefings, internal annotations. Public data stays public, your data stays yours.
  • The captain's logbook. Every passage planned with Nausika quietly persisted. "This run last August — how did it go? What's different now?" gets an answer, without you having to archive anything by hand.

What we won't do

A roadmap is also what you say no to. Nausika will not:

  • Become a booking or payment platform. Reservations and money flow are someone else's problem; navigation and discovery are ours.
  • Carry advertising or paid placements. Place ranking is neutral (proximity-based) and will stay that way.
  • Ingest proprietary or paywall-scraped data. Open licenses or original observations only.

Maintenance commitment

Nausika is built and maintained by a single developer. To compensate for the bus factor of one, we commit to:

  • Service continuity. The service will remain operational at minimum through December 31, 2026. If we ever decide to wind it down, we publish a notice on /log and email connected users with at least 90 days lead time.
  • Security. Patch SLAs and the responsible-disclosure process are in the security policy.
  • No surprises in the interface. If we change how the AI sees Nausika in non-backward-compatible ways, we announce it 60 days ahead on /log. Additive changes (new capabilities, new fields) ship freely.
  • Public log. Development is tracked openly on /log with RSS. Bugs and feature requests are public on the GitHub feedback tracker.
  • Honest scope. When something on this roadmap slips or gets cut, we say so on /log. The roadmap is a living document, not a contract.