Alex Ndungu

Co-Founder + CTO

Let's talk
HomeAboutExperienceProjectsSkillsContact
Let's talk
HomeAboutExperienceProjectsSkillsContact

Alex Ndungu

Backend systems, machine learning retrieval, and clean product-minded engineering for teams that care about reliability.

GitHubLinkedInLeetCodealexmeta517@gmail.com
Multi-Tenant Real Estate Operating System

Harlem Manage

The company I lead as CTO. Harlem Manage is a Kenya-first operating system for property firms — multi-tenant core, role-aware AI execution, real-time M-PESA payment flows, and a production observability stack — scaling as the system landlords and agencies run their business on.

harlem.co.ke

Multi-tenant

Organisation and property isolation

M-PESA

Native payment rail

Role-aware AI

Akoko execution layer

Problem statement

Property management in the target market is not just CRUD over properties and tenants. It requires organization-level isolation, financial correctness, payment reconciliation, operational coordination across multiple roles, and localized workflows that reflect how real rental systems run in Kenya.

Architecture breakdown

I framed the system as a distributed, multi-tenant SaaS platform with strict relational modeling, RBAC enforcement across the application and AI layer, M-PESA-first payment design, and Akoko as a first-class intelligence engine with role-specific execution modules, channel-aware outputs, and human escalation paths.

  • - Role-based AI agent system with dynamic tool selection per role — full audit trail per message for compliance
  • - M-PESA C2B STK Push with OAuth2, field-level encrypted credentials per organisation and property, and live payment status streamed via JWT-authenticated WebSocket consumers over Redis
  • - Distributed async task architecture over Celery and RabbitMQ driving scheduled ledger generation, maintenance automation, and payment reminders
  • - Production observability: structured JSON logging, per-request UUID tracing, recursive PII scrubber redacting sensitive field patterns before Sentry/GlitchTip transmission
  • - Organisation-to-property multi-tenancy with fully isolated payment flows, RBAC enforcement, and field-level encryption transparent at ORM level

Tech stack explanation

Next.jsDjangoDjango REST FrameworkPostgreSQLM-PESAWhatsApp/SMSAkoko AI

System diagram

[ Organizations ]
      |
      v
[ Multi-Tenant Core ] ---> [ Properties / Units / Tenants ]
      |                             |
      |                             +--> [ Lease & Rent Engine ]
      |                             +--> [ Ledgers / Reconciliation ]
      |
      +--> [ RBAC Layer ]
      |        +--> Owner
      |        +--> Manager
      |        +--> Caretaker
      |        +--> Tenant
      |        +--> Guard
      |
      +--> [ Akoko Intelligence Layer ]
               +--> Owner Execution
               +--> Caretaker Execution
               +--> Tenant Execution
               +--> Guard Execution

Key challenges

Harlem Manage is a Kenya-first, multi-tenant real estate operating system built for landlords, agencies, and property firms. It combines property workflows, tenant and lease management, financial reconciliation, communication channels, and Akoko, a deployed operational intelligence layer that adapts by role. We are building it as core infrastructure for African rental operations, not a management panel with a local coat of paint.

  • - Building the product as real estate operating infrastructure for the African rental market, not a simple management panel.
  • - Integrated operational intelligence directly into the product through Akoko rather than treating AI as a future add-on.
  • - Established a technical foundation — multi-tenant isolation, financial correctness, access-controlled AI — that the business can scale on without a rewrite.

What I learned

AI becomes much more valuable when it is embedded inside operational workflows rather than exposed as a generic assistant.
Multi-tenant architecture needs to be treated as a system-wide discipline across schema design, service logic, and permissions.
Local market context like M-PESA, language behavior, and escalation norms can meaningfully shape architecture decisions.