Odedara Labs
Sabha
Maintenance funds for housing societies. Bills, collections, receipts and a ledger every resident can see — instead of a register in the treasurer’s cupboard.
Three people, three views of the same money
Resident
Your flat, your dues, your payment history. What’s owed, what’s paid, and the receipt for each one — without asking anybody.
Committee
The whole society at a glance: who has paid, who hasn’t, what the fund holds, and where it went.
Treasurer
Raise the month’s bills for every flat at once, record payments as they come in, and issue receipts that residents can see immediately.
A Flutter app for Android and the browser, talking to a Spring Boot API over HTTPS. Accounts are approved by the committee before they can sign in, and the backend enforces every permission independently of the app — the screens you don’t see are also screens you can’t reach.
- App
- Flutter (Android, Web)
- API
- Spring Boot, JWT auth with refresh
- Data
- PostgreSQL
- Hosting
- Single VM, HTTPS throughout
One account, not one per product
Sabha used to keep its own passwords. It doesn’t any more: accounts live in a single Odedara Labs identity service shared by everything here, so a resident who also rides with ODD Flow signs in once rather than twice.
A society’s residents mostly have a phone number and no email, so an account can be either — and the number is what links somebody to the flat the committee already knows them by.
Sabha never sees the password. It holds only the public half of the key that signs a session, which means it can tell who you are and cannot issue a session for you. Being a member of a society is separate again: an account gets you in the door, and the committee decides whether you belong to that particular building.
Want it for your building?
Sabha is running in a real society today. If your committee is still tracking maintenance in a register or a spreadsheet, write to me and I’ll walk you through what setting it up involves.