From scattered records to one product.
I designed Kaza as a web platform that connects day-to-day property management with rental listings. It brings owners and tenants into separate spaces built on a shared data model.
The product is still an MVP in development. The full stack foundation is in place; payments, notifications and other external integrations are part of the next steps.
NEXT.JS → NESTJS → POSTGRESQLOne domain, two interfaces.
The Next.js frontend and NestJS API share the same business model, persisted with Prisma and PostgreSQL. Owner and tenant roles are separated through the API.
Owner space
A place to manage properties, units, contracts, rent and listings.
Tenant space
Personal access to lease details, rent deadlines, receipts and housing conversations.
Optional marketplace
Listings can be attached to available units without making every property public.
Kaza also generates lease documents and rent receipts as PDFs. On the API side, JWT sessions, owner and tenant roles, resource ownership checks and input validation protect access to these records.
The MVP covers authentication, property and contract management, rent and receipt flows, listings and messaging. Mobile Money, automated notifications and public marketplace search remain future integrations.