Your journey to the perfect Mangala day
Every rupee, every vendor, every guest and every hour of the day itself — in one place your whole family can actually use. MangalaHub replaces the spreadsheet that only one person understands.
Free while in beta · No card · Export everything to Excel any time

163
days to go
5,120,400
107% of a 4,800,000 budget
74%
+18 today107 still to answer
The problem
It always starts as a spreadsheet.
And the spreadsheet is usually good. The problem is what happens to it: one person owns the file, the numbers stop agreeing with each other, and on the morning of the wedding the only copy of the running order is in someone's head.
The money quietly drifts
A quote becomes a negotiated price becomes an actual, and nothing recalculates. Nobody finds the overspend until the deposit is gone.
Decisions get lost
Three photographers, three WhatsApp threads, three different definitions of "full day". You end up choosing on price because price is the only thing you can line up.
The day lives in one head
The coordinator needs arrival times, phone numbers and a running order — on paper, under stress, with no signal in the hotel basement.
The product
Four screens do most of the work
Scroll, or pick a tab. These are the real screens.
Opens with the only thing that asks something of you — and every row is a link that carries its own filter.
Nethmi & Sahan
Saturday, 14 February 2027
163
days to go
Needs your attention
Critical
- 3payments are overdue
- 7budget lines forecast over what was budgeted for them
412
268 confirmed so far
74%
107 still to answer
61%
57 of 93
9 of 14
4,800,000
5,120,400
107% of budget
320,400
Where the money is going
107% of budgetBudget- Venue & Reception1,640,000
- Photography & Video720,000
- Attire & Jewellery610,000
Readiness
61%Tasks- Day-of operations3 late12%
- Attire & jewellery40%
- Ceremony & legal92%
Everything else
Eighteen more modules, one shape
Attire, jewellery custody, beauty appointments, decor, menu, cake, transport, accommodation, shot lists, procurement and packing. Each one is a list you can own, cost, assign and tick off.
Payments with receipts
Deposit, advance, instalment, final, refundable. Attach the receipt, and the line's status follows on its own.
Contributions and gifts
Who promised what, who has actually paid, and what the wedding really costs once the gifts are counted.
Guests and RSVP, no login
One link per household. Guests reply without an account; the counts, the seating and the headcount for catering all move together.
Move the date, move the plan
Every task and appointment is stored as an offset from the wedding day. Change the date and the whole plan re-dates itself.
Jewellery custody register
Borrowed, rented or family-owned — who is holding each piece right now, and when it goes back.
Export everything, any time
One button, one workbook, every sheet. It sits in the navigation rather than buried in settings, on purpose.

Who it's for
Everyone sees what they should, and nothing more
Access is enforced by the database, not by hiding a menu item. A coordinator with the link still cannot read a single figure.
The coupleowner · partner
Everything. Money, vendors, guests, the day, and the button that exports it all.
Familybride's side · groom's side
The budget and the payments they are funding, scoped to their side. No arguments about who paid for what.
Coordinatorno money, ever
Timeline, vendor arrivals, contact sheet, seating and the emergency plan. Financial rows are not hidden from them — they are not returned at all.
Guestsno login
A single RSVP link per household, rate-limited and captcha-protected. They see their own invitation and nothing else.
The template library
You do not start with an empty page
Create a wedding and it arrives already planned, from a versioned template for your tradition. Every line is yours to rename, re-cost or mark not applicable — and marking something not applicable keeps its budget on the books, so the totals still reconcile.
194
budget lines, coded and categorised
227
vendor questions across 16 categories
93
tasks, each dated from the wedding day
56
timeline events for the day itself
24
Poruwa ceremony steps, in order
82
procurement items — buy, pack, load
62
shot-list items for photo and video
17
legal requirements, each verifiable
Day-of console
The one screen that has to work with no signal
The coordinator is standing in a hotel corridor at seven in the morning. Whatever else is true, the running order, the arrival times and the phone numbers have to be in their hand. So the app prints a pack — the same markup as the screen, not a second copy that drifts.
- A printable pack — timeline, vendor arrivals, contact sheet and the emergency plan, with tick-boxes for a pen.
- Cached for offline — a service worker keeps the day-of screens available when the venue's wifi does not cooperate.
- Clashes flagged — two things booked into the same twenty minutes get caught before the morning, not during it.
- Every number in one place — pulled from the vendor records, so it is never a version behind.
Nethmi & Sahan — Day pack
14 Feb 2027
Vendor arrivals
| 05:15 | Nayana Bridal — hair & make-up | 077 412 8890 | |
| 06:30 | Studio Amaya — photography | 071 902 3341 | |
| 06:45 | Sithumina Decor — poruwa load-in | 070 556 1204 | |
| 16:00 | Beat Lounge — sound check | 076 330 7788 |
If it goes wrong
| Rain before the poruwa | Move to the banquet foyer · Anushka |
| Registrar delayed | Run the cake cut first · Coordinator |
| Power cut at the venue | Venue generator, confirm by 10 Feb |
Your data
Separation you can check, not just trust
One wedding cannot see another's rows. That boundary is a database policy on every single table, written against 266 assertions that test it from the outside — as a member of the wrong wedding, as a coordinator reaching for money, as an anonymous request with a guessed identifier.
Enforced at the row, not the menu
Hiding a navigation link is a convenience. The database refuses the query regardless of what the browser asks for.
Money in cents, never floats
Rounding errors are not a cosmetic bug in a wedding budget — one wrong total costs you every other number on the screen.
Leaving is one click
Export the whole wedding to a workbook whenever you like. The export is in the navigation because a couple who can see it believe they can leave.
Questions
Is it only for Sri Lankan weddings?
No. The Buddhist Poruwa template is the most complete one because that is where the content came from, but Christian, Hindu, Muslim and generic templates use the same engine. The tradition is data, not code.
Can I bring my existing spreadsheet in?
Guests import from CSV today. For the budget, most couples find the template already covers what their sheet had, and renaming lines is quicker than mapping columns.
What if we change the wedding date?
Every task, appointment and countdown item is stored as an offset from the wedding day rather than as a fixed date. Change the date in Setup and the whole plan moves with it. Anything you dated by hand stays where you put it.
Can our coordinator really not see the money?
Correct. Financial tables return no rows at all for the coordinator role — not blurred, not hidden in the interface, simply not sent. Screens that mix money with operations use a separate operations-facing view.
How many guests can it handle?
Guests are grouped by household, and each household gets one RSVP link. A thousand-guest list is a few hundred links, which is well within what the RSVP endpoint is rate-limited for.
Start the plan tonight
Create a wedding, pick your tradition, and the template fills it in. Free while MangalaHub is in beta — and your data comes back out as a workbook whenever you want it.
No card. Cancel by deleting the wedding — it takes its data with it.