Feature · Multi-event timeline
Mehendi, sangeet, reception — one timeline.
An Indian wedding is not 'a wedding'. It's a five-day festival with overlapping guest lists, dress codes, and venues. Multi-event was the first feature we built, because no other tool we tried understood that.
Each event, its own world
Sangeet has its own RSVP list, dress code, venue, and timeline. Reception has its own. The app stops conflating them, which is what every other tool gets wrong.
Multiple venues, one map
Add up to five venues with directions, parking notes, and venue manager contact. Guests see only the venues for the events they're invited to.
Dress code per event
Indo-western for Sangeet, traditional for ceremony, semi-formal for reception. Communicate it once; it lives on every guest's invite card and reminder.
Day-of run-of-show
Minute-by-minute timeline per event. Pheras at 8:20, garlands at 8:55, mom's speech at 9:10. Share with the MC, the DJ, the videographer.
Cross-event analytics
How many guests attend all five events? How many only the reception? Useful for catering planning and for thanking the right people in toasts.
Custom events welcomed
Mangni, Tilak, Roka, Mehendi-after-party — add any event with a custom name and we treat it as a first-class citizen, not a workaround.
What we don’t pretend to do yet
Cross-wedding workspaces are Planner-tier
If you're a professional planner running three weddings in a single month, you'll want the Planner tier. The default is one wedding per workspace by design — keeps families separate.
Recurring sub-events not supported
We don't model 'three sangeet nights in a row'. Each event is its own row. Adding a Sangeet-1 and Sangeet-2 is the recommended pattern.
Map your celebration in 15 minutes.
Add your events, drop the venues on the map, the rest of the planning flows from there.