The part nobody else does
Guests send their flight number once. From then on OurNoce watches every one of them: delays, gate changes, missed connections, who is actually landing when.
Today
147
confirmed, and 33 still thinking
One record per guest. Every module reads from it.
RSVP just in
The Mensah party · 5 coming, 1 under 12
Flight change
Grandma Rose · AS 641 delayed 55m
Checklist
Final headcount due to the resort in 9 days
Why we exist
The big sites hand you a page and a registry, then leave the actual wedding to a spreadsheet, a group chat and a shoebox of contracts. The work is the logistics. That is what we built.
A template site, a registry, a vendor marketplace that is really selling to you. Guest list in one tab, seating in another, payments in your inbox.
Re-typing the same 180 names into four tools. Redoing the seating chart every time an RSVP changes. Answering "what time does Auntie land?" forty times.
One record per guest, and every module reads from it. An RSVP changes the seating, the headcount, the budget and the arrivals board at once.
The platform
Import your invite list, watch replies land by name: adults, children, dietary notes, song requests. No re-typing, ever.
LiveSet the tables, reserve a few, let it generate the plan. Move a party by hand and it stays moved. Every reply re-checks the chart.
SoonA plan that knows your date. Deposits, fittings, final counts, all counted back from the day, with an owner on every line.
SoonBridesmaids and groomsmen get their own accounts: attire, fittings, flights, passports, what they owe. They tick their own boxes.
SoonEstimate, actual, paid, outstanding, against every vendor and every room block, with the maths shown.
SoonEvery quote, contract and deadline in one book, with the payment dates pushed into your checklist automatically.
SoonText everyone, or only the 24 who have not booked a room. Draft once, send to the right list.
SoonOne flight number per guest, then live arrivals, delays and transfers for the whole weekend.
SoonArrivals
It reads the consequences too. A late arrival that will miss the welcome dinner. Four guests who could share one transfer. The shuttle that now needs to leave an hour later.
Amara & Joel Okafor AA 1284 · DFW → SJD | Landed 14:06 |
The Mensah party (5) UA 1129 · IAH → SJD | In the air, 16:40 |
Grandma Rose AS 641 · SEA → SJD | Delayed 55m |
Tomas Ribeiro WS 2201 · YYZ → SJD | Boarding |
| Grandma Rose now lands after the welcome dinner starts. Move her transfer, or hold table 3? | |
One flight number per guest. The transfers sort themselves.
Wedding party
You decide who sees what. Your maid of honour can run the guest list. Your groomsmen see only their own eight tasks. The budget stays yours until you say otherwise.
Guest list, seating, the checklist lines you hand over.
Their own attire, fittings, flights and what they owe.
The arrivals board and the room blocks. Nothing financial.
Join the waitlist
We are onboarding couples in small groups so we can set the first one up with you personally. The nearer your date, the sooner we call.
Already running a real wedding: Marie-Louise & Cedric, four days in Los Cabos, April 2027, around 180 guests. See their site →