NIVON PG
Multi-tenant PG, hostel and co-living management SaaS — owner console, resident app and public discovery on one platform.
- Type
- Multi-tenant SaaS
- My role
- Product & engineering
- Platforms
- Web · PWA · Mobile
- Status
- Launching soon
Private repository · walkthrough available on request
Overview
NIVON PG is one platform for many PG owners and property management companies. It covers the whole operation: properties down to individual beds, residents and their stays, rent and deposits, staff, complaints, visitors, food and checkout — with SaaS plans and subscriptions for the operators themselves.
The problem
PG and hostel operators juggle beds, rent, deposits, staff and complaints across notebooks, spreadsheets and chat groups. Balances drift, beds get double-booked, and residents have no single place to pay rent or raise an issue.
Architecture
React · PWA
Expo · PWA
Discovery
NestJS · CQRS · CASL · tenant-scoped
TypeORM
OTP · rate limits
Inngest
- REST API
- NestJS with CQRS — the single source of truth, documented with an API reference
- Owner & staff console
- React installable PWA for owners, staff and platform admins
- Resident app
- Expo app, also exported as a PWA
- Public discovery
- Website for finding PGs and sending booking requests
- Background jobs
- Inngest jobs for rent generation, late fees, reminders, holds and subscription expiry
Modules
- Properties → buildings → floors → rooms → beds
- Residents, stays, bookings and admissions
- Rent, invoices, ledger and deposits
- Online rent payments
- Staff, attendance and salary
- Complaints and maintenance
- Visitors and deliveries
- Food and mess
- Assets and stock
- Notices
- Checkout and deposit settlement
- Reports, dashboards and SaaS subscriptions
Engineering decisions
The guarantees I designed in, not bolted on.
- 01
Tenant isolation, fail-closed
Every organisation-owned table carries an organisation ID, and the ORM query layer adds it to every read and write from the request context. A query without a tenant scope fails instead of leaking data.
- 02
Double booking stopped by the database
Bed allocation locks the bed row, and a partial unique index refuses a second live stay on the same bed — a guarantee that survives a bug in application code.
- 03
One ledger, one balance
Each resident has a receivable and a deposit account. Every balance comes from one function, invoices are immutable (a correction is a void plus a new invoice), and rent invoices are idempotent by period.
- 04
Payments settle exactly once
The client never marks a payment paid. Only a verified checkout signature or webhook settles it, under a row lock with a unique gateway payment ID. Gateway keys are per organisation and encrypted at rest.
- 05
Subscriptions with a humane lock
After the grace period an operator's workspace turns read-only automatically — but residents can still sign in, pay rent and raise complaints.
- 06
Privacy-first PWAs
Service workers cache only the app shell, never API responses, so no invoice or personal data stays on a device after sign-out. Identity documents are encrypted and served through short-lived signed links.
Technology
- NestJS
- CQRS
- CASL
- TypeORM
- PostgreSQL
- Redis
- Inngest
- React 19
- React Router
- Tailwind CSS
- TanStack Query
- Expo
- Razorpay
- Turborepo
- Docker
Engineering quality
- Monorepo with shared DTOs, permissions and enums across the API and every client
- Typed API client generated from the backend contract
- Unit tests and API end-to-end tests
- Architecture decisions recorded as ADRs