The invitation is the free part, on purpose
Every guest at a wedding opens the invitation. Nobody opens the guest-list spreadsheet. So the invitation is the part we give away — it is beautiful, unlimited, watermark-free and costs nothing, because it is how a couple and three hundred of their guests meet us. What we charge for is everything that happens after: knowing who is coming to which function, reaching them on WhatsApp without typing three hundred messages, and getting them to the right venue on the right day.
Built for multi-day weddings, not adapted to them
Most wedding platforms are built around one ceremony and one guest list. An Indian wedding is haldi, mehendi, sangeet, the ceremony and the reception — frequently across two cities and four days, with a different set of people invited to each. That shape is the foundation here rather than a feature bolted on: RSVPs are recorded per guest, per function, and a guest can be invited to the sangeet and not the haldi without anyone maintaining a second list. Read more about per-event RSVP and guest list management.
The phone we optimise for is not the one we own
A wedding invitation is almost never opened in Chrome on a laptop. It is opened inside WhatsApp's built-in browser, on a mid-range Android phone, on patchy data, frequently by someone in their sixties. That is the device every template is tested on. It is why animations are built to stay smooth rather than to look impressive in a demo, why heavy images are loaded late, and why we care about the WhatsApp link preview as much as the page behind it.
One shared component library, many templates
A Wedence template is a theme and a configuration over one shared set of blocks, not a separate hand-built site. That is an engineering decision with a direct consequence for couples: a fix or an improvement made once reaches every template, and a couple picking a less popular design is not choosing a worse-maintained one.
Privacy is structural, not a promise
Guest lists are the most sensitive thing a couple gives us — real names and real phone numbers, several hundred of them. Each wedding's data is isolated per tenant at the database level, so one couple cannot read another's guests even in the event of a bug in the application above it. We do not sell or rent guest data, and no vendor gets a guest's number from us.
What we have not built yet
We would rather say this plainly than let a feature list imply otherwise. Wedence is not a vendor marketplace and takes no commission on bookings. It is not a registry or a gifting platform. It does not print cards. And the guest-facing invitation is curation rather than access control by default — the schedule shows a guest the functions they are invited to, but the link itself is shareable unless a couple switches on guest-list verification.