Nodus is two things that share a plan. For the couple, a planner: checklist, vendors, budget, guest list with tables and dietary restrictions, day-of schedule, notes, and a sheet for the wedding coordinator that prints as a PDF with or without the figures. For everyone else, the invitation that comes out of it — the date, a countdown, the venue on a map, and the gift list.
Guests claim a gift by name, with a message if they want to, and it leaves the list so nobody buys it twice. The claim is written to a separate document the couple’s account can read but not be flooded by, which keeps a page open to anyone with the link from being a way to spend somebody else’s storage quota.
The plan lives on the device first and syncs through Firestore, merged item by item with a timestamp on each one and a tombstone for each deletion. Two phones editing different things offline both keep their work; two phones editing the same thing keep the newer. It was built that way after a whole-document merge quietly threw away an evening of typing.
There is no sign-up, and no demo. Access is by invitation: the planner sits behind a door, and the invitation it publishes travels by link rather than by search — it carries a noindex and is in no sitemap. Which is why this page is all there is to see of it.