Case Study

Rilaebu

Engineering verified housing infrastructure for safer direct tenancies.

Rilaebu is a verified housing infrastructure platform being engineered for the Nigerian rental market. It combines trusted property discovery with identity, verification, controlled transaction workflows, landlord operations, auditability and trust-and-safety foundations. The product is currently in active development, with the architecture intentionally designed for secure growth without premature infrastructure complexity.

Role

Lead Full-Stack Engineer

Industry

PropTech / Housing Infrastructure

Duration

2026 – Present

Status

Active Development

Platform Preview

Product Interface

Visit Live Platform →

https://rilaebu.vercel.app

Overview

Project Overview

A security-first housing platform designed to make direct landlord-tenant transactions safer, more transparent and operationally complete.

The Vision

Project Information

Client: Personal Product
Industry: PropTech / Housing Infrastructure
Duration: 2026 – Present
Role: Lead Full-Stack Engineer
Status: Active Development

Project Links

Visit Live Site All Projects

Blueprint

Product Blueprint

Rilaebu product development roadmap showing the progression from product and trust foundations through identity, the verified marketplace, transaction infrastructure and trust-and-operations expansion.

Product Walkthrough

Inside the Platform

A guided walkthrough of the key experiences that define the product, highlighting both the user interface and the engineering decisions behind each major feature.

Rilaebu Homepage

Housing you can trust

The public entry point introduces Rilaebu's verified-housing proposition and guides users into the platform's core rental journey.

Business Impact

Establishes the product's trust-first positioning while giving landlords and tenants a clear starting point.

Property Search

A focused housing discovery experience

The search experience provides the interface for discovering available housing within Rilaebu's marketplace journey.

Business Impact

Moves the product from its public proposition into practical property discovery.

Rilaebu landlord and tenant registration interface

Account Registration

Role-aware onboarding

Registration introduces users to the platform through landlord and tenant account paths as the foundation for role-aware housing workflows.

Business Impact

Creates a structured entry point for the two primary sides of the rental marketplace.

Secure Sign In

Account access

The sign-in experience provides a focused authentication entry point for returning Rilaebu users.

Business Impact

Supports the identity and session foundation that underpins protected platform experiences.

Password Recovery

Account recovery workflow

The recovery interface supports users who need to regain access to their Rilaebu account.

Business Impact

Extends the authentication experience beyond sign-in with a practical account-recovery path.

Account Verification

Trust begins with verified identity

The verification experience forms part of Rilaebu's trust-first account lifecycle and guides users through account verification.

Business Impact

Connects identity onboarding with the wider trust architecture of the housing platform.

Tenant Dashboard

A dedicated tenant workspace

The tenant dashboard provides a role-specific workspace for the tenant side of the Rilaebu experience.

Business Impact

Demonstrates the platform's progression from public discovery into authenticated, role-aware product experiences.

Landlord Dashboard

A dedicated landlord workspace

The landlord dashboard provides a role-specific workspace for the supply side of the platform.

Business Impact

Establishes the interface foundation for landlord-focused housing and operational workflows.

Platform Story

The mission behind Rilaebu

The about experience explains the product's housing mission and the trust problem Rilaebu is being designed to address.

Business Impact

Gives the platform narrative context beyond individual screens and workflows.

Architecture

Technical Architecture

Every technology was intentionally selected to support scalability, maintainability, performance and long-term product growth.

Next.js + TypeScript

Provides the initial full-stack application foundation with explicit domain and service boundaries that can evolve as scale and operational needs justify separation.

Modular Monolith

Keeps the first production architecture operationally simple while preserving clear boundaries for identity, properties, verification, listings, transactions, trust and administration.

PostgreSQL + Prisma

Provides a relational, type-safe data foundation for stateful housing, identity and transaction workflows.

Identity & Sessions

The implemented foundation covers registration, email verification and account-verification workflows, with the broader lifecycle designed for recovery, session management, MFA and step-up authentication.

Authorization

Sensitive actions are designed around role permissions, resource ownership and current state or policy checks, with enforcement on the server rather than relying on frontend visibility.

Audit & Observability

Authentication, API, authorization/security and business audit events are separated so sensitive workflows can be traced while protected data and credentials remain excluded from logs.

Engineering

Engineering Decisions

Every major technology choice was made to improve scalability, maintainability and long-term product evolution.

Architecture Strategy

Modular monolith before microservices

Rilaebu preserves explicit domain boundaries without paying the operational cost of distributed services before scale, reliability or ownership boundaries justify them.

Authorization Model

RBAC + ownership + state/policy checks

Role-based access alone is insufficient for sensitive housing and financial workflows. Authorization decisions also consider the actor's relationship to a resource and its current state.

Security Foundation

Security as architecture

Authentication, authorization, auditability, logging, privacy, abuse controls and monitoring are treated as foundation concerns rather than features to bolt on after launch.

Property Data Model

Verified asset separated from market listing

Property, ownership, address and verification remain authoritative domain records while a listing is treated as the market-facing representation of an underlying asset or unit.

Challenges

Engineering Challenges

Every complex product presents engineering challenges. These are the key problems encountered while building Rilaebu and the considerations behind solving them.

Challenge 01

Designing trust into the product

A generic verified badge is not enough. The platform must communicate exactly what has been verified while preserving evidence quality and user privacy.

Challenge 02

Fine-grained access control

Tenant, landlord, professional, verification, support, finance and administrative workflows require stronger boundaries than simple role checks.

Challenge 03

Complex workflows without premature complexity

The long-term platform spans identity, properties, verification, applications, agreements, payments, disputes and operations, but the MVP must remain focused and operable.

Challenge 04

Sensitive operational evidence

Security and business events need enough context for investigation and audit without leaking credentials, identity documents, tokens or other protected information.

Solutions

Engineering Solutions

Each challenge was addressed through deliberate architectural and engineering decisions that support long-term scalability and maintainability.

Solution 01

Explicit domain boundaries

The architecture separates identity, authentication, authorization, properties, verification, listings, applications, agreements, payments, audit, security events and administration into clear modules.

Solution 02

Policy-driven authorization

Sensitive server-side actions combine permissions, resource relationships and current state to produce authorization decisions based on least privilege.

Solution 03

Traceable security architecture

Structured authentication, API, audit and security-event records are designed around request correlation, redaction and append-oriented audit evidence.

Solution 04

Deliberate phased delivery

The platform defines future capability while implementing the secure golden path first, avoiding unnecessary infrastructure and unsupported feature claims.

Lessons

Lessons Learned

Key insights gained while building Rilaebu.

Trust requires explainability

Verification is more useful when users understand what was checked, rather than seeing an unexplained status badge.

Authorization is a domain problem

Secure access control depends on resource relationships and workflow state as much as it depends on a user's role.

Architecture should preserve options

Clear boundaries can support future service extraction without forcing a young product to operate distributed infrastructure too early.

Security decisions shape product design

Identity, auditing, privacy and abuse prevention affect workflows and data models from the beginning, so they belong in product architecture.

Transformation

Product Development Roadmap

Rilaebu is being delivered deliberately from product and security foundations toward a focused verified-tenancy MVP before broader platform expansion.

Stage 01

Product & Trust Foundation

Define the housing problem, trust model, product principles, design system, legal/compliance dependencies and production architecture.

Stage 02

Identity & Session Foundation

Build the account lifecycle and secure identity/session foundations. Registration and email verification are already part of the active implementation.

Stage 03

Verified Marketplace MVP

Develop the focused landlord and tenant journey around profiles, properties, authority evidence, verification, listings, enquiries, viewings and applications.

Stage 04