Full Stack · Real Estate
A real estate platform that connects house hunters, landlords and agents without the fraud that makes online property hunting miserable. Django REST backend with four distinct roles, admin verification gates and a moderation queue; React 19 and TypeScript on the front.
Demo status: the React front end is deployed on Vercel so you can walk the interface, but the Django API isn't hosted yet — listings stay empty until the backend runs. Local setup steps are at the bottom of this page.
Live embed of the deployed app. If it doesn't load in your browser, open it in a new tab.
The interesting work here is authorisation: four roles that see genuinely different systems.
Online property hunting in Kenya has a trust problem. Listings are posted for houses that were let months ago, deposits are collected for properties the poster doesn't control, and the same photos appear under three different agents. House hunters end up paying viewing fees to find out.
Fixing that isn't a UI problem, it's an authorisation problem: who is allowed to post, who has been verified to do it, and what happens when a listing is reported.
Sole developer across both halves. I designed the role and permission model, built the DRF API with its verification gates and moderation flow, and built the React front end that consumes it.
A Django REST backend of focused apps, and a Vite-built React client that talks to it over JWT.
Custom user model, the four roles, and the verification state each one carries.
Property records, ownership rules, active/verified flags and report handling.
Users flag listings as fake or unavailable; admins resolve them from a queue.
Matches hunters to listings with its own permission boundaries.
Conversational assistant for search and questions about a listing.
React 19, TypeScript, Tailwind 4 and Framer Motion, bundled by Vite.
Each app ships its own DRF permission classes. Hiding a button in React is a courtesy; the server refusing the request is the actual rule.
House hunters are auto-verified because the risk they pose is low. Agents and landlords — the roles that can publish and take money — wait for an admin. Friction is applied where the fraud actually happens.
A flagged listing creates a report record with a reason and a resolution state, so moderation has a queue and a history rather than an inbox.
Listings carry is_active and is_verified rather than being removed. A moderator can reverse a mistake, and the audit trail survives.
dj-rest-auth, django-allauth and SimpleJWT instead of a hand-rolled login. Authentication is the last place to be inventive.
The React client is deployed independently of the API, so the interface can ship without redeploying the backend — and a second client could reuse the same API unchanged.
Two terminals: the Django API and the Vite dev server.
git clone https://github.com/Eunice-ctrlz/Find-a-home.git
cd Find-a-home
python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
python manage.py migrate
python manage.py createsuperuser
python manage.py runserverAPI on localhost:8000. The superuser is what verifies agents and landlords.
cd frontend
npm install
npm run devVite serves the client on localhost:5173.
I'm happy to talk through the architecture or the decisions above — and I build systems like this for other people too.