Intro

I'm Mansur, a developer and network/systems engineer working at the intersection of software and the infrastructure it runs on. My core focus is BillSeazy, a multi-tenant ISP and hotspot management platform — which means my day-to-day spans everything from ASP.NET Core backends and MySQL schema design to MikroTik routers, FreeRADIUS authentication, and M-Pesa payment flows.

I like problems that sit between layers: a billing bug that's actually a RADIUS misconfiguration, a slow captive portal that's actually a walled-garden rule, a "simple" dashboard that needs real-time router telemetry behind it. Outside of client and product work, I maintain a handful of side projects spanning e-commerce, fintech, and social apps, and I keep the servers they run on alive with my own CI/CD and monitoring setup. Take a look at some of what I've built below.

My Work

A mix of production systems, ISP/telco infrastructure, and side projects — spanning .NET, Node, and React:

  • BillSeazy: A multi-tenant ISP & hotspot billing platform tying together MikroTik routers, FreeRADIUS, and M-Pesa (Daraja STK push). Covers router management with AES-256 credential encryption, live session monitoring, revenue analytics, bulk SMS, and full WiFi hotspot lifecycle automation (purchase → RADIUS provisioning → session management → expiry). Built with C#/.NET, ASP.NET Core, EF Core, MySQL, KnockoutJS, and AdminLTE.
  • GearHut: A responsive e-commerce platform for phone and laptop accessories, currently being extended with a structured, category-scoped product-specification system (attributes, highlights, package contents) for an Amazon-style product detail experience.
  • USSD Rendering System: A multi-carrier USSD platform (Onfon, Africa's Talking) handling session state, phone number normalization for Kenyan MSISDNs, saved inputs/favourites, and an in-progress analytics dashboard tracking completion rates, drop-off funnels, and navigation paths.
  • Real Estate & Smart Meter Backend: ASP.NET Core Razor Pages backend for tenant billing and water/smart-meter reporting — reconciliation logic for metered readings, running-balance reporting, and a companion .NET worker service (ManualReadings) that syncs and validates external meter data.
  • Tujikaze: A React/TypeScript app for a family chama (self-help group) — member dashboards, M-Pesa billing, PDF minutes export, and Google Drive-backed shared memories — being extended into a multi-tenant platform for multiple families.
  • Habibty: A couples date-planning app with a React/TypeScript/Supabase stack, full product design, and row-level-security-backed multi-user data model.

Each of these has pushed me somewhere new — deeper into networking protocols on one end, product and UI design on the other. I'm always happy to talk through the trade-offs behind any of them.

Stack & Competencies

Technologies and areas I work in regularly:

  • Backend: C#, ASP.NET Core, Entity Framework Core, Node.js/Express, MySQL, SQL Server, Dapper
  • Frontend: React, TypeScript, KnockoutJS, Bootstrap 5, AdminLTE, DataTables, ApexCharts/Chart.js
  • Networking & Telco Infrastructure: MikroTik RouterOS, FreeRADIUS, PPPoE & hotspot billing, captive portals, WireGuard, RFC 3576 CoA/Disconnect
  • Payments & Kenyan Integrations: M-Pesa Daraja (STK Push), Africa's Talking (USSD/SMS), Onfon USSD gateway
  • DevOps: GitHub Actions CI/CD, DigitalOcean droplet management, nginx, Prometheus/Alertmanager/Blackbox Exporter, Linux administration
  • Other: Supabase/PostgreSQL, product & schema design, RESTful API design

About

I hold a Bachelor of Information Technology from JKUAT, and currently work at Leizam Ventures. My path into engineering started with straightforward web development, but building an ISP billing platform pulled me steadily into networking and telecom protocols — and I've stayed there since. I like that BillSeazy forces me to think across the whole stack: a support ticket can start in a Razor Page and end in a MikroTik CLI session.

Outside of code, I play chess and enjoy cognitive games and puzzles that exercise logical reasoning — not too different from debugging a RADIUS auth flow at 11pm.

My approach to development is guided by these principles:

  • Understand before you build: I like to understand trade-offs and match existing patterns before writing new code.
  • Iterative and pragmatic: I favor targeted, well-scoped changes over large rewrites.
  • Own the whole path: from database schema to the CI/CD pipeline and the server it deploys to.

Let's connect and create something amazing together!