NIVON Housing
Housing society management SaaS — gate security, residents, helpdesk, maintenance billing and community for many independent societies.
- Type
- Multi-tenant SaaS
- My role
- Product & engineering
- Platforms
- Web · Mobile · PWA
- Status
- Live
Private repository · walkthrough available on request
Overview
NIVON Housing — “Your Society, Connected.” — runs many independent housing societies on one platform. Guards manage the gate, residents approve visitors and pay maintenance, staff handle complaints and billing, and the platform owner provisions societies and their plans. One Expo app serves every role, alongside a back office for society staff.
The problem
Large societies run security, maintenance and dues on paper visitor registers, WhatsApp groups and spreadsheets. Guards can't verify who is expected, residents chase approvals by phone, and committees have no reliable view of complaints or collections.
Architecture
React · staff
Expo · PWA
Offline sync
NestJS · CQRS · CASL · N replicas behind nginx
TypeORM
OTP · rate limits
Inngest
- REST API
- NestJS with CQRS — stateless replicas behind nginx, sessions in Postgres
- Back office
- React console for society staff and the platform owner
- Mobile app
- One Expo app for residents, guards and staff, also exported as the PWA
- Background jobs
- Inngest jobs for overstay alerts, visit expiry, subscription notices, push retries and retention
Modules
- Buildings, wings, floors and flats
- Residents, occupancy and move-out
- Visitors, approvals and QR/OTP guest passes
- Gate console with offline sync
- Vehicles, parking and violations
- Helpdesk with SLAs and ratings
- Maintenance billing and online payments
- Expenses, dues and collection reports
- Notices, polls and documents
- Amenities and capacity-safe bookings
- Daily help, parcels and SOS alerts
- Roles, staff and SaaS administration
Engineering decisions
The guarantees I designed in, not bolted on.
- 01
Gate writes that never record twice
Every gate write carries a request ID generated on the device, backed by a unique index. A retried or duplicated request returns the original result instead of logging a second entry.
- 02
Honest offline mode
Offline, the guard's device queues entries and marks them “logged offline, not verified”. On sync each item is applied, marked duplicate or flagged as a conflict for supervisors — nothing offline is ever recorded as resident-approved.
- 03
Access scoped to flats and gates
Permissions are database-driven roles with all/own scopes: residents see only their flats, guards only their gates. A subset rule blocks privilege escalation — nobody can grant what they don't hold.
- 04
Billing never blocks safety
A lapsed subscription only triggers notices, and only the platform owner can lock a society, with an audited reason. Even when locked, gate security, sign-in and notifications keep working.
- 05
Built to scale horizontally
The API holds no request state in memory: sessions live in Postgres, OTP codes and rate-limit counters in Redis, so nginx can balance any number of replicas without sticky sessions.
- 06
One identity across societies
People sign in with their mobile number and an OTP. One person can belong to several societies with different roles and switch workspaces without a second account.
Technology
- NestJS
- CQRS
- CASL
- TypeORM
- PostgreSQL
- Redis
- Inngest
- React 19
- React Router
- TanStack Query
- Expo
- Razorpay
- nginx
- Turborepo
- Docker
Engineering quality
- Monorepo with shared DTOs, permissions and enums across the API and every client
- Load-tested against a seeded 800-flat demo society
- Unit tests and API end-to-end tests
- Architecture decisions recorded as ADRs