How to build a wedding website and RSVP platform

Short answer

We estimate a wedding website and RSVP platform costs $30,000–$50,000 (AUD, ex GST) for an RSVP-first version and $50,000–$90,000 for a full self-serve platform with payments and custom domains. Start with household guest lists, personal RSVP links and reliable invitation email. The hard parts are the guest model, email and SMS delivery, and guest privacy, not the web pages.

$30k – $90kOur estimate for a first version (AUD, ex GST)
18 daysyourwedding.app, first commit to live
8,039Automated unit and tool checks at launch

What do Australian couples use today?

Australian couples can choose from free builders and one-off paid ones. The free ones earn money from registries, upgrades or vendor listings. The paid Australian ones charge once, in AUD.

Prices below were checked in October 2026. Builders change them often, so treat this as a snapshot.

Wedding website builders Australian couples use, October 2026. Prices from each vendor’s own page.
BuilderPriceNotes
JoyFreeDomain, texts and premium stationery designs are paid upgrades
Easy WeddingsFreeAustralian. RSVP management included
WedBuildFree to 50 guests, then A$99 or A$199 onceAustralian. Paid plans run for 2 years
WedSitesA$59, A$159 or A$319 once6, 12 or 24 months of hosting. Online RSVPs start on the A$159 plan
yourwedding.appFree to try, then A$229 or A$299 onceOur product. A personal link per guest, texts to Australian mobiles

Build, buy or white-label?

  • Planning one wedding? Use a builder. Building your own is far more than any builder costs.
  • A planner or venue with many weddings a year? A white-label site under your brand can make sense.
  • A new product? Only build if you have an angle the free builders don’t cover.

We decided yourwedding.app couldn’t compete on “free website”. Our angle was named-guest RSVP, texts to Australian mobiles and guest data stored in Sydney. Other angles: a niche like destination or cultural weddings, or a different event type.

How much does it cost to build?

It depends on how self-serve it is. A platform where couples sign up, pay and publish with no help from you is much bigger than a site you set up for each client.

Our indicative estimates for a client build. They assume new design, no data migration and up to two outside integrations.
ScopeWhat’s in itCost (AUD, ex GST)Time
RSVP-first MVPOne guest-site theme, personal RSVP links, CSV import, email invitations, a couple dashboard, data deletion$30k – $50k1–2 months
Self-serve platformAdds sign-up, a site editor and styles, Stripe packages, own domains, reply alerts, scheduled deletion$50k – $90k2–3 months
Full platformAdds SMS with a reply inbox, guest photo uploads, scheduled wedding-day texts, an AI connector$90k – $100k+3–5 months

For how these numbers compare with other app types, see how much an app costs in Australia.

What is a wedding platform made of?

yourwedding.app is two web apps on one backend, plus a marketing site.

  • The guest site. The public wedding website, with the day, travel, the RSVP form and photos.
  • The couple studio. Where the couple edits pages, imports guests, sends invitations and tracks replies.
  • The backend. Accounts, guests, replies, payments, email, SMS, own domains and deletion.

The stack we chose, and why

  • Guest site and studio: Next.js, built as static files and served from CloudFront. One site shell serves every wedding.
  • API: AWS AppSync (GraphQL) with Lambda functions. Couples sign in with Amazon Cognito.
  • Data: DynamoDB and S3 in Sydney (ap-southeast-2). Infrastructure is written in AWS CDK.
  • At launch it was 10 application stacks and 22 Lambda functions in Sydney.

The guest site has no server. When a couple presses Publish, the page content is written as a static file with no guest details in it. If the API has a bad hour on the wedding day, guests can still read the address, the schedule and the dress code. Only replying and photos need the API.

Near-zero cost when nobody is using it

We planned for traffic in bursts: a spike after invitations go out, then quiet. So we pay per request, not per hour.

A test in the build fails if anyone adds a resource with a standing charge, such as a NAT gateway, a WAF firewall, a Secrets Manager secret or provisioned database capacity. Stored data and backups still cost a little. We cover running costs in more detail in app maintenance costs.

How should the RSVP work?

This is where the hard product decisions are. Couples think in households. Caterers think in people. Guests just want to tap a link and reply.

  1. The couple imports a CSV or Excel list. yourwedding.app takes up to 500 rows per import and suggests households by surname.
  2. Each invited person gets a personal link with an 8-character code. The code sits after the # in the link, so it isn’t sent when the page loads and stays out of CDN logs. Treat the link like a password all the same.
  3. The guest opens the link. There’s no account, password or app.
  4. The link opens that person’s household. One person can reply for everyone in it, yes or no for each name.
  5. Guests who accept answer the couple’s questions. Couples can add up to 10, per person or per household.
  6. The guest can change the reply later from the same link. The couple gets a reply alert by email.

Rules to decide before you build

  • Plus-ones. We chose no unnamed ones. Every guest is added by name, which keeps numbers firm for the caterer.
  • Children. Our rule: a child under 16 belongs to a household, has no email or mobile, and never gets a text. That’s a product choice, not an age set by the Privacy Act.
  • Limited spots. Some questions run out, like parking or on-site beds. A question can cap how many say yes.
  • Forwarded links. Only people on the guest list can reply, but a forwarded link still works. Couples can issue a new link, which stops the old one.
  • Guessing codes. Codes use a 32-character alphabet, so there are about 1.1 trillion. The guest authoriser also counts failed tries per IP.
  • Late changes. Decide when replies close and what the couple sees when someone changes their mind.

Which features are worth building?

Effort is relative to the rest of the platform.
FeatureWhy couples want itEffort
Personal RSVP linksOnly people on the guest list reply. No plus-one surprisesHigh
Guest list importCouples arrive with a messy spreadsheetMedium
Site editor and stylesLooks like their wedding without a designerMedium–High
Own domainyournames.com instead of a platform addressMedium
Email invitations and remindersThe default channel on yourwedding.appMedium
SMS to guestsGuests without email, or who prefer textsHigh
Guest photo uploadsEveryone’s photos in one place, with no appMedium–High
AI connectorAsk “who hasn’t replied?” from Claude or ChatGPTMedium
Seating chartsMany builders offer one. We left it out of version 1High

Own domains

Couples buy the domain themselves. They type it into the studio and copy the DNS records it shows. yourwedding.app then requests a free AWS certificate in us-east-1, where CloudFront reads them. It creates a CloudFront distribution for that name and maps it to the wedding.

Each distribution uses a slot in your AWS account. CloudFront allows 500 distributions per account and 100 per CloudFront Function by default. That’s one reason own domains are on paid packages only. Past a few hundred domains, plan for CloudFront’s multi-tenant distributions.

The AI connector

On Pro, couples connect their own Claude or ChatGPT to their wedding. It can read guests and replies, and with permission add guests or draft page edits.

It can never send invitations, take payments or delete anything. Page edits wait until the couple presses Publish. Each change is logged for 90 days.

The AI company does receive guest names, households, replies and dietary notes, and may store them in the US. The connector leaves out guests’ stored emails and mobiles. Guests agree to dietary notes being shared with a connected AI when they reply. The couple chooses to connect, under their own agreement with that company. See AI app costs for how we price AI features.

Will the invitation emails land in the inbox?

Meeting the big mailbox rules doesn’t guarantee the inbox. But failing them can mean rejections, delays or the spam folder. A platform sends every couple’s invitations from one domain, and Google counts mail from the same primary domain together. So a busy Saturday can cross its bulk-sender line.

Google treats anyone who sends close to 5,000 messages a day to personal Gmail accounts as a bulk sender. That status is permanent. Since November 2025, Gmail has been ramping up rejections of mail that fails the rules.

The main bulk-sender rules, checked October 2026. Gmail also requires TLS and valid reverse DNS from every sender.
RuleGmailYahoo
AuthenticationSPF and DKIM, plus DMARCSPF and DKIM, plus DMARC
DMARC policyp=none is allowedAt least p=none, and it must pass
One-click unsubscribeRequired on marketing and subscribed mailRequired on marketing and subscribed mail
Honour unsubscribesWithin 48 hours (recommended)Within 2 days
Spam complaint rateBelow 0.3%. Aim for under 0.1%Below 0.3%

Sources: Gmail’s sender guidelines and Yahoo’s sender best practices.

Your own marketing email is a separate question. Messages that promote your platform fall under the Spam Act. The ACMA says you need consent, must identify yourself and must make unsubscribing easy. A guest list a couple uploads is not marketing consent.

What does SMS cost in Australia?

yourwedding.app uses Mobile Message, an Australian provider. Its standard prices, ex GST, are below. The rate depends on how many credits you buy at once. Replies are free and credits don’t expire.

Mobile Message standard pricing, checked October 2026.
Credits bought at oncePrice per SMS part (ex GST)
500+4¢
1,000+3.5¢
10,000+3¢
100,000+2.5¢
1,000,000+2¢

From Mobile Message’s pricing page. A first purchase made within 30 days of sign-up is 1.6¢ a part. The first dedicated number is free after that first purchase.

yourwedding.app sells 200 credits for A$19, GST included. The margin pays for failed-send handling, the reply inbox and support.

A worked example

These counts are illustrative. Work out the parts from your real message, including the link and opt-out wording.

  • A 120-guest wedding texts 20 households without email. Say each invitation is 2 parts. That’s 40 credits.
  • A reminder to 15 households, 2 parts each, is 30 credits.
  • A wedding-day update to 90 guests who opted in, 1 part each, is 90 credits.
  • Total: 160 credits × 3.5¢ = $5.60 ex GST for the whole wedding.
  • At 600 weddings a year, that’s 96,000 credits. Bought in lots of 10,000 or more, it’s 96,000 × 3¢ = $2,880 ex GST.

What makes SMS harder than email

  • Length. A plain GSM-7 text part holds 160 characters, or 153 when parts are joined. One emoji or curly quote can switch the message to Unicode: 70 a part, or 67 when joined.
  • Replies. With one shared number, a reply has to find the right wedding. Guests in more than one wedding are asked to start their reply with that wedding’s code.
  • STOP. A STOP to a shared number ends texts from every wedding on it. Our rule is to honour it before the next send.
  • Sender names. Since 1 July 2026, texts from an unregistered business name show as “Unverified”. The ACMA says senders using a phone number don’t need to register. A number also lets guests reply.
  • Overseas guests. yourwedding.app texts Australian mobiles only. Guests overseas get email.

How do you protect guest data under the Privacy Act?

A wedding platform holds names, emails, mobiles and dietary notes for thousands of people who never signed up. Treat it as personal information from day one.

Most businesses with annual turnover of $3 million or less are exempt from the Privacy Act. Exceptions include health service providers and businesses that trade in personal information. The OAIC lists them all, so check with a lawyer before relying on it. We wrote yourwedding.app’s policy as if the Australian Privacy Principles (APPs) apply.

  • Guests didn’t sign up. The couple uploads their details. Tell guests, in the invitation and on the RSVP page, who holds their information, why, and who it’s shared with. Link your privacy policy.
  • Dietary notes. Allergies or medical diets can be health information, which the OAIC lists as sensitive information. Sensitive information generally needs consent. On yourwedding.app, the reply form asks for consent before sharing dietary needs with the couple, their helpers, the caterer and any connected AI.
  • Overseas providers. APP 8 covers disclosing personal information overseas. yourwedding.app stores wedding data in Sydney. Its privacy policy names the providers that may process data overseas, including SMS, payments, error monitoring, analytics and AI.
  • Security. APP 11 asks for reasonable steps to protect it, and to destroy or de-identify it once it’s no longer needed. Guests see only their own household. Guest sites ask search engines not to index them, but they’re still public pages.
  • Deletion. On yourwedding.app, the default is 24 months after the wedding, and couples can pick 3, 6 or 12. The site is hidden first, with 7 days to undo, then deleted. Backups can hold data for up to 35 days after that.
  • Breaches. If you’re covered by the Act, the Notifiable Data Breaches scheme says you must tell affected people and the OAIC when a breach is likely to cause serious harm. Assess a suspected breach within 30 days.

Payments add their own records. yourwedding.app keeps payment records for at least 7 years, even after a wedding is deleted. Ask your accountant how long you need to keep yours.

How should couples pay?

We chose one payment per wedding, because a wedding has an end date. yourwedding.app charges through Stripe Checkout. Prices for couples include GST.

yourwedding.app packages, October 2026. Text credits are sold separately.
PackagePrice (GST incl.)What it adds
FreeA$0Every page except Photos, up to 5 guests, a preview ribbon
WeddingA$229 onceThe whole guest list, invitation emails, texts with credits, photos, own domain
ProA$299 onceEverything in Wedding, the AI connector and 100 text credits

Stripe’s standard rate for domestic cards in Australia is 1.65% + A$0.30, including GST. On a A$229 package that’s 1.65% × 229 = $3.78, plus 30c, so about $4.08.

You can’t pass that on as a card surcharge. Surcharges on eftpos, Mastercard and Visa cards ended on 1 October 2026.

Build the Stripe webhook so a repeated event can’t grant a package or credits twice. Plan refunds and disputes too, even as a manual runbook. Your refund terms can’t remove consumer guarantees under the Australian Consumer Law.

How do you start?

  1. Pick the angle. Decide what your platform does better than the free builders, and for whom.
  2. Write the guest model on one page: households, people, children, questions and limits.
  3. Choose the channels: email only, or email and SMS. Budget for SMS credits and the sender setup.
  4. Decide on payments: one-off packages, add-ons and refunds.
  5. Prototype the RSVP with a real, messy guest list before building the rest.
  6. Agree the launch tests: one household can’t see another, revoked links stop, duplicate imports and payment events do nothing twice.
  7. Write a brief. Our app brief template covers what to include.
  8. Get an estimate. Our free estimate form takes a few minutes.

We’re an Australian team in North Bondi, and we built yourwedding.app ourselves. See the yourwedding.app case study for screens and detail.

Common questions

How long does it take to build a wedding RSVP app?

We estimate 1–2 months for an RSVP-first client build and 2–3 months for a full self-serve platform. yourwedding.app went live 18 days after its first commit, but it was our own product with no approval loop.

Should I build a wedding website platform or use an existing builder?

For one wedding, use a builder. Free and one-off options cost far less than any build. Build only if you are launching a product with a clear angle, or you run many weddings a year as a planner or venue.

Do I need a native mobile app for a wedding platform?

Usually not to start. Guests open a link from an email or text, so a fast mobile website is what they use. yourwedding.app launched as web only. If a native app later sells digital features, Apple and Google billing rules apply.

How do guests RSVP without creating an account?

Each guest gets a personal link with a short code. The link opens only their household, and the server checks the code before it shows or saves anything. Guests never set a password.

Can I send invitations to guests overseas?

Email works for guests anywhere. SMS depends on the provider and the country. yourwedding.app texts Australian mobiles only, so overseas guests get their invitation by email.

How much does it cost to send SMS to guests in Australia?

Mobile Message, the Australian provider we use, charges 2 to 4 cents per message part, ex GST, depending on how many credits you buy at once. The number of parts depends on the full message, including the link. Replies are free.

Is a wedding website platform covered by the Privacy Act?

Possibly. Businesses with more than $3 million turnover are covered, and some smaller ones are too. Guest dietary notes may count as health information. Check with a lawyer, and build as if the Australian Privacy Principles apply.

Can the same platform run other events?

Yes. Household links, questions, reminders and day-of texts suit engagement parties, milestone birthdays, reunions, memorials and member events. Conferences usually need ticketing and check-in on top.

Sources

  1. Google: Email sender guidelines FAQ
  2. Google: Email sender guidelines
  3. Yahoo: Sender best practices
  4. ACMA: Avoid sending spam
  5. Mobile Message: SMS pricing
  6. ACMA: Unregistered branded SMS labelled “Unverified” from 1 July
  7. ACMA: Sending text messages with your business or organisation name
  8. OAIC: Small business and the Privacy Act
  9. OAIC: What is personal information
  10. OAIC: About the Notifiable Data Breaches scheme
  11. AWS: CloudFront quotas
  12. AWS: Amazon SES pricing
  13. Stripe: Pricing (Australia)
  14. RBA: Merchant card payment costs and surcharging, at a glance
Proof

One we built.

Our own product · Web and mobile

yourwedding.app

Our own product. Couples get a wedding website with a personal RSVP link for each guest, SMS invites, a shared photo album and their own domain.

From first commit to launch
< 3 weeks
Couples manage it from Claude or ChatGPT
MCP
Read the case study →
Free consultation

Building an event or RSVP platform?

You’ll hear back from Dylan, not a sales team. Reply within one business day, AEST.

Reply within one business day.
Free, no obligationGet an estimate →