Plan every ceremony,
track every rupee.
Budget. Guests. Gifts. Ledger.
WLB splits your total budget across renameable categories, holds a contingency buffer for the surprises, tracks your guest list with shagun and thank-you status, runs a gift registry with pooled group funds, and keeps a personal give-and-take ledger that stays yours alone — across an engagement, sangeet, wedding, reception, or anything in between.
Native iOS & Android · One account, synced everywhere · Local-first & private · by Aviora Tech
Built for the real complexity of an Indian wedding.
Not a generic Western budgeting app — a planner shaped around multiple ceremonies, both families' guest lists, shagun customs, and the fact that several people are spending from the same pot.
Smart budget split
Enter a total and get a sensible percentage split across renameable categories — Main Event, Food & Catering, Jewellery, Decorations, Photography and more. Auto-allocate, lock a category and redistribute the rest, or add and remove your own.
Contingency buffer
A dedicated buffer pool absorbs surprise costs. Top up an over-running category from the buffer instead of letting one line item blow up the whole plan.
Hard caps
Optionally block any spend that would take a category past its budget — so the limit is a rule, not a suggestion somebody notices a week later.
Planned vs actual
Log expenses against categories and watch planned and actual diverge in real time, with a budget-analysis view that surfaces spend trends over the run-up.
Lakh & crore, done right
Money is stored as whole paise and displayed in whole rupees with lakh/crore grouping — the way the numbers are actually said out loud, not decimal, dollars-style formatting.
Multi-event planning
An engagement, sangeet, wedding, reception or birthday — each its own event with its own budget, guest list, registry and members. Switch between them freely.
Guests & shagun tracking
Manage the guest list with shagun and cash-gift amounts per guest, and mark thank-you status as you work through it.
Import from Contacts
Pull guests, members and ledger contacts straight from your address book — or add someone by name alone and fill in the phone or email later.
Registry & pooled funds
Run a registry of wished-for items alongside named cash funds with a target amount, that several people can contribute to together with visible progress.
Cash and items, counted separately
Gifts received keep cash and estimated item value as two separate totals — adding a guess at the value of a saree to actual shagun would overstate the money in hand.
Planning timeline
A checklist of planning tasks running alongside the budget, so the things that aren't money still have somewhere to live.
Works fully offline
Local-first: every change is written to the device first and the UI reacts to that, so nothing waits on a network round-trip. Sync is background reconciliation on top.
From total budget to settled accounts.
Create the event
Add a wedding, engagement or any celebration with the couple's names and date, pick your categories, and enter a total — WLB proposes the split before you've typed a single line item.
Bring in your circle
Invite family and planners by phone or email at the role you want them to have. They sign in with that contact and the event is simply there, at that role.
Track as you plan
Log spend against categories, record shagun and thank-yous, run the registry, and keep your personal ledger up to date — on iOS or Android, online or off.
See where you landed
Planned against actual, gifts in against spend out, and a buffer that shows exactly how much room is left before the plan is in trouble.
Five roles, so everyone sees exactly what they should.
A wedding is planned by a committee, not a person — and not everyone on it should see the budget. Every action in the app is gated on one shared set of capabilities, so no screen invents its own rules.
Full control, and only ever one. Can grant the budget to an editor, change anyone's role, and delete the event.
Owner-equivalent day to day, and you can have several — for the two families, or a lead planner.
Records spend always. Touches the budget and the contingency buffer only if the owner explicitly grants it.
Read-only. Can follow along without any risk of changing a number by accident.
Registry-scoped. Every other tab collapses away — they can pitch into a group fund without ever seeing the budget.
The owner can view the whole app as an editor or viewer to check what they'd see — without it ever changing real permissions.
A personal ledger, independent of any event.
Weddings come with money changing hands outside the budget too — cash lent to a cousin, a vendor advance you covered, a shagun you're owed. WLB keeps a separate give-and-take ledger per person, so those informal accounts don't get lost in a chat thread.
- Track money lent or borrowed with anyone, by name
- Lives outside any single event — it's yours across every celebration
- Structurally private: it sits outside the shared event tree, so a collaborator cannot reach it at any role
Not a second expense app
The ledger deliberately does no splitting and no settling-up maths. It answers one question — who owes whom, and how much — and it answers it for you alone.
Your ledger is nobody else's business.
Access isn't a UI convention here — it's enforced on the server, and tested as the attack it's meant to prevent.
Clients can't grant themselves access
Membership is never writable by an app. Cloud Functions do it atomically with the Admin SDK, so an invite can't be forged, enumerated, or escalated into a higher role.
Rules tested as attacks
Twenty security-rules tests run against the emulator, each written as the thing it blocks — privilege escalation, invite enumeration, forging a notification, reading someone's personal ledger.
Notifications that don't leak
A shared-event push says that someone updated the event — never what changed or by how much. The detail stays behind the app's own access checks.
An inbox you control
Invites, role changes and removals arrive in an in-app inbox with accept and decline. Declining revokes the invite for real on the server, rather than just hiding the row.
Sign in your way
Google sign-in or phone OTP, on both platforms. Your data is scoped to your account, and shared events are visible only to the people invited to them.
Deletion that keeps the door open
Delete your account and your personal data and solo events are destroyed. Shared memberships re-open as pending invites tied to your verified contact — sign up again and those ledgers come back at the same role.
Both platforms, at parity.
iOS was the reference implementation and Android was built against the same domain model — the same tabs, the same capability gating, the same thirteen persisted types, and two sync services writing an identical document shape.
iOS
In testing- SwiftUI + SwiftData, feature-modular, with a pure Swift domain package
- Full feature set built and unit-tested
- App Store release pending
Android
In testing- Jetpack Compose + Room, mirroring the iOS models field for field
- Feature parity with iOS, audited and closed out
- Google Play release pending
Backend
Live- Event-centric Firestore with per-role security rules, deployed
- Seven Cloud Functions live — invite, claim, decline, role change, remove, phone claim, delete account
- Push notifications for shared-event edits
Policies & contact.
Everything about how WLB handles your data.