01 Venue
The dashboard
The venue signs in at /admin to create weddings, paste guest lists, watch RSVPs land, and upload the delivery. The platform owner grants access. It’s never self-serve.
Quick summary
A wedding lives in five places at once: a LINE group for the guest list, a Google Form for the RSVP, a printed card for the invitation, a Drive folder for the photos that expires when someone clears their storage, and a phone call to the venue every time a number changes. Nobody owns the count. The real headcount lands the week of the wedding.
This replaces all five with one platform. The venue creates a wedding, pastes the guest list in as one column, and the invitation links generate themselves. Guests reply through their own link. The photographer’s delivery arrives on the same site weeks later, with the venue’s name on it, in front of two hundred people who are all about to plan something.
Who this platform is for
This is built for the business that books the wedding, not for a single couple.
- Wedding venues who want every booking to arrive with its own site under the venue’s name
- Planners coordinating several weddings at once who need one dashboard rather than five spreadsheets
- Photographers and studios who want delivery to be a branded experience instead of a link that expires
What problem this platform solves
A wedding currently lives in five places at once, and none of them owns the number that matters.
- The guest list is in a chat group, the RSVP is in a form, the invitation is on paper, and the photos are in a folder that expires
- Nobody owns the headcount, so the true number lands the week of the wedding. That’s the week it’s most expensive to be wrong
- The delivery, which is the moment two hundred future customers see the venue’s work, arrives as a generic file-share link
What you get with this platform
The template is the working platform, plus the path to owning your own copy of it.
- The live demo wedding exactly as it ships. Open it, explore it, and switch it to Thai without signing up
- The exact production prompt behind the build, which you buy once in the prompt shop
- A rebuild service: the same platform rebuilt around your venue’s brand, your copy, and your domain
- Sold outright when commissioned: the venue owns it, charges the couple for it, and pays no per-wedding licence fee
Three doors, one product
Everyone signs in the same way: email plus a one-time code, with no passwords anywhere. What differs is which door they use, and how permission was granted before they got there.
02 Couple
The portal
The couple signs in at /portal to edit their own story and see their own guest list, and nothing else. The venue adds their email to give them access.
03 Guest
The invitation link
A guest opens /i/<token> and is greeted by household name. The link is the guest list. There’s no account to create and nothing to install.
One wedding, three phases
Each wedding carries a phase switch. One click from the dashboard changes what every guest sees, with no rebuild and no second site.
Phase 01
Before
Engagement gallery, the couple’s story, a live countdown, and the RSVP form.
Phase 02
Day of
The order of the day, directions, and a map link. Replies are closed, and the page is a schedule.
Phase 03
After
The full gallery and the highlight film, with full-resolution downloads.
Always
English and Thai
Every phase ships in both, including the invitation itself, and the guest can switch between them.
Stage overview
| Stage | What happens |
|---|---|
| Create the wedding | One record that carries everything downstream |
| Paste the guest list | One household per line, and the links generate themselves |
| Guests reply through their own link | The link is the guest list |
| The count closes itself | The number the kitchen gets is the number that’s true |
| Flip the phase on the day | One switch changes what every guest sees |
| Deliver the photos and the film | The moment that sells the venue |
Design and branding system
Every wedding is visually its own, while the platform underneath stays one codebase.
- Per-wedding palette and monogram, so two weddings on the same platform don’t look like the same template twice
- Fully bilingual. English and Thai run throughout, including the invitation itself, and the guest can switch between them
- Thai-aware typography: a Thai household name inside an English greeting still gets Thai line metrics rather than clipped ascenders
- The venue’s name is on all of it, and that’s the entire commercial point. The delivery markets the venue instead of a third party
Security, isolation, and delivery
Each wedding’s data is fenced off at the database level, so it doesn’t depend on application code remembering to filter.
- Row-level security per wedding. A guest holding one couple’s link can’t reach another couple’s photos or replies, even with a valid session, because the database itself refuses the row
- Passwordless sign-in throughout: email plus a one-time code, with nothing stored that a leak would embarrass anyone with
- Invitation pages are never indexed. They exist for the person holding the link and no one else
- Media URLs are signed and expire, so a link scraped in the morning is dead the same afternoon
How this platform helps you convert
The delivery is the sales channel. Everything else on the platform exists to make sure the venue owns that moment.
- The photos land on the venue’s own site, in front of two hundred people who are all about to plan something
- A self-closing headcount removes the single most expensive uncertainty in running a wedding
- It’s multi-tenant, so the same build serves every wedding the venue books. The cost is paid once and earns on every booking after
Other information about this platform
Worth knowing before you commission one.
- It’s multi-tenant by design: unlimited weddings under one venue account, each fully isolated from the others
- Guests never create a password. Access is a one-time code by email, and the invitation link is the guest list
- Sign-in codes go out over a verified sending domain, so they land in inboxes rather than spam folders
- It’s sold outright when commissioned. The venue owns the build and pays no per-wedding licence fee
What it’s built with
| Frontend | Next.js 16 (App Router) and TypeScript, deployed on Vercel |
|---|---|
| Backend | Supabase: Postgres, passwordless auth, and row-level security per wedding |
| Media | ImageKit: upload, transform, thumbnails, video posters, adaptive streaming, and signed URLs |
| Resend SMTP on a verified domain for the one-time sign-in codes | |
| Languages | English and Thai throughout, switchable by the guest, with Thai-aware typography |
| Tenancy | Multi-tenant: unlimited weddings under one venue account |
Screenshots
Captured from the live demo wedding. This is the platform as it renders.
