Explore here
- Web app
- Consumer apps
Build a wedding website with an RSVP that knows who is coming
Wedding websites are easy until the RSVPs come in. Then you need to know, per guest rather than per household, who is coming, who is bringing a plus-one, who chose the fish and who has an allergy — and a template site hands you a list of free-text replies. Vibely builds the whole site from a description, with the RSVP as real data: an invitation code per household, a choice per guest, and a page where the two of you see the totals.
- Platform
- Web app
- Category
- Consumer apps
- Stack
- React, TypeScript, Supabase
- Plans
- Free and up
Per-guest RSVPs with meal choices and dietary notes
Included in the first build
Household codes so only invited guests can reply
Yours to keep
- Deploys to a live URL — nothing for your team to install
- React and TypeScript you own, synced to GitHub on every plan
- A private totals page and CSV export for the caterer
- Free plan, no credit card; custom domain on Pro and Business
1. Who this is for
For couples, and for the friend who has been volunteered to make the site. It is also a good first build if you have never made an app, because the shape is familiar. If all you need is a date and an address, a free page builder is enough; the case here is the RSVP and the guest list behind it.
2. Start with this prompt
Paste it in and edit the details to match your own. Being specific about the screens and the data is what separates a working app from a mockup.
Build a wedding website for Priya and Sam, getting married on 14 June at a vineyard. Pages: a home page with our names, the date, a live countdown and a photo; Our story as a timeline of five moments; The weekend with the schedule for Friday drinks, the Saturday ceremony and Sunday brunch; Travel with hotels and directions; Registry with three links; and a FAQ. RSVP: guests enter a household code, then for each guest in the household choose attending or not, a meal (beef, fish or vegetarian) and dietary notes. Some households are allowed a plus-one. Data: households, guests and responses in Supabase. A private page for the two of us after signing in shows totals by meal, who has not replied and a CSV export. Seed it with twenty households.
3. What the build actually consists of
The pages guests read
A home page with a countdown, your story as a timeline, the weekend schedule, travel and hotel notes, a registry page with your links and a FAQ — in the style you describe, on a phone first.
An RSVP that is data
Guests enter their household code, then answer for each person: attending or not, meal choice and dietary notes, with an optional plus-one where you allowed it. Every answer is a row in Postgres, not an email.
Your view of the numbers
A sign-in-protected page for the two of you with totals by meal, the list of who has not replied yet and a CSV export for the caterer and the seating plan.
Built on:The Supabase backendOne-click publishingCode you own
4. What you get
- Pages for your story, the schedule, travel and the registry
- A live countdown to the day
- An RSVP form that answers per guest, with meal choices
- A private page with totals and the guests still to reply
- A CSV export of the final guest list
5. What to build next
Once the first build lands, these are the prompts people send next.
- Add a song request field to the RSVP and a list of requests on our private page.
- Add a photo upload page for guests after the wedding.
- Send each household a personal link that fills in their code automatically.
Works with the tools you already use
Nine built-in connectors — Vibely AI, Supabase, Stripe, RevenueCat, GitHub, Notion, Linear, Figma and Miro. Anything else is an API call in code you own.
Questions, answered.
Describe it. Watch it build.
Paste the prompt above and react to something running instead of writing a spec. The free plan needs no card, and the code is yours from the first build.