WeddingOS — Free RSVP Platform for Weddings

"Eliminate the 'Canva + Excel + WhatsApp' chaos every couple inherits."

Overview

WeddingOS is a free RSVP and guest-management platform for weddings. Planning a wedding breaks most project-management tools because it has too many moving parts: 50–300 guests each with plus-ones, dietary restrictions, travel logistics, seating constraints, and a deadline you absolutely cannot miss. Most couples end up stitching together Google Sheets, WhatsApp groups, Canva invitations, and sticky notes.

WeddingOS is the opinionated alternative: one platform that handles invitations, RSVPs, guest communications, and logistics with templates and automations built specifically for weddings.

🎯 Core Features

Guest management

• Bulk guest import from CSV / Google Contacts
• Households, plus-ones, and RSVP state tracked at person-level
• Dietary restrictions, song requests, accessibility needs
• Guest segmentation (ceremony-only, reception-only, after-party)

Digital invitations & RSVP

• Template library with customizable designs
• Per-guest RSVP links (no shared codes)
• RSVP deadline reminders with escalating cadence
• Plus-one confirmation flow

Logistics

• "Where to stay" accommodation recommendations per guest
• Transport coordination
• Seating chart planner
• Timeline-of-events builder

Communications

• Email blasts segmented by RSVP status
• Reminder automations

🛠️ Tech Stack

Application

• Next.js 16 App Router with React 19 and TypeScript
• Tailwind CSS, shadcn/ui
• Supabase Auth (magic links + OAuth)

Data

• Supabase Postgres with Row-Level Security so each couple only sees their own guests
• Realtime subscriptions for live RSVP dashboard
• Supabase Storage for invitation assets

Production-grade ops

• Sentry on client, server, and edge runtimes (three config files: sentry.client.config.ts, sentry.server.config.ts, sentry.edge.config.ts)
• Playwright end-to-end tests with dedicated playwright-report
• Instrumentation hooks for request tracing
• Stripe for premium tier
• Upstash Redis rate limiting on public endpoints (RSVP pages can't be signup-spammed)

Developer ergonomics

• Full local Supabase stack via Docker (auth, database, storage, email testing via Inbucket at :54324)
• Cloud Supabase option for staging
• Test coverage reports + manual testing doc
• Process-mining data for understanding guest flows

🏗️ Engineering Highlights

Per-guest RSVP with no login

Each guest receives a unique tokenized link. They RSVP without creating an account — the whole point of wedding software is that 70-year-old grandparents use it. Tokens are single-purpose, time-bound, and revocable.

Household-aware data model

A household is the unit of invitation (the Jones family gets one invite), but each person RSVPs individually. The schema handles this cleanly without forcing the couple to think in spreadsheet rows.

Production observability from day 1

Most side projects skip Sentry until something breaks. Wedding software cannot fail silently on the day the RSVPs go out. Full error tracking across client, server, and edge runtimes is wired in before the first user.

E2E tests on the critical path

Playwright covers the signup → guest import → send invitations → receive RSVP flow. These are money paths (the premium tier) and trust paths (the whole product is useless if invitations don't send).

💡 Why I Built This

Every couple I know has rebuilt the same broken system. The problem isn't that wedding platforms don't exist — it's that the existing ones (The Knot, Zola) are ad-riddled marketplaces first, software products second. WeddingOS is free and ad-free because the real value is making the day go well, not upselling vendor referrals.