Portfolio

Software is more than code. It is the careful translation of real-world problems into systems that people can rely on.

This portfolio is a curated collection of products and platforms I have designed and built. Some are commercial systems, some are open-source, and some are research projects. Together, they reflect my interests in enterprise software, financial technology, backend engineering, security engineering, and systems architecture.

Every project below links to a detailed article where I discuss the problem, architecture, engineering decisions, and lessons learned throughout its development.

Monesize Core

Enterprise Financial & Operational Platform

Monesize Core is a modular backend platform built for businesses that need far more than traditional accounting software. Designed as a single-tenant financial operating system, it combines finance, operations, inventory, payroll, projects, procurement, analytics, compliance, and workflow automation within a single architecture.

Built as a modular Node.js monolith with event-driven coordination, the platform allows independent business domains to remain loosely coupled while preserving the simplicity of a unified deployment model. Each deployment is isolated with its own backend, database, and environment, allowing the platform to be tailored to the operational needs of individual organizations.

Role

Founder • Product Architect • Backend Engineer

Technologies

Node.js • Express.js • PostgreSQL • Prisma ORM • Event-driven Architecture

Status

Active Development

→ Read the engineering story

Kongres

Attendance & Engagement Platform

Kongres is an attendance and engagement platform designed for churches, ministries, and organizations. Beyond simple attendance recording, it provides event management, QR-code attendance, member tracking, analytics, and a growing engagement ecosystem designed to help organizations better understand and serve their communities.

The platform was designed with future expansion in mind, including support for USSD, messaging, AI-powered insights, and scalable organizational management.

Role

Founder • Backend Engineer

Technologies

Node.js • Express.js • PostgreSQL • Prisma ORM • JWT

Status

Prototype

→ Read the engineering story

Open Fintech

Open Source Fintech Backend

Open Fintech is an open-source backend project exploring the architecture behind modern financial products. It provides a reusable foundation for developers building fintech applications, including authentication, transaction management, analytics, payment splitting, dynamic credit scoring, and savings workflows.

The project reflects my interest in creating reusable infrastructure that allows fintech teams to build products without repeatedly solving the same backend problems.

Role

Creator

Technologies

Node.js • Express.js • PostgreSQL

Status

Open Source

→ Read the engineering story

Meetvo

Professional Network for Tech Talent

Meetvo is a text-first professional networking platform built specifically for the technology community. It allows engineers to showcase their careers through public profiles, share technical thoughts, discover opportunities, and connect directly with recruiters without the distractions common to traditional social platforms.

The project explores the idea that meaningful professional networking can be built around knowledge and conversation rather than endless media consumption.

Role

Founder • Product Designer • Backend Engineer

Technologies

React • Node.js • Express.js • PostgreSQL

Status

Prototype

→ Read the engineering story

More Projects

My work extends beyond these products. I regularly build internal tooling, security research projects, proof-of-concepts, and experimental systems that help me explore new technologies and engineering ideas.

Many of these are documented throughout this website as technical articles rather than standalone portfolio entries.

Popular Posts

Building Event Reliability at Monesize Core

As Monesize Core evolved into a modular business platform, more parts of the system started depending on events. Accounting needed to react to sales. Inventory needed to react to purchases. Activity logs needed to capture important actions. Notifications needed to respond to business events. The architecture naturally moved toward an event-driven approach. A service performs a business operation, emits an event, and other modules react. At first glance, this looks simple. A transaction happens. An event is emitted. Listeners process the event. The problem is that distributed systems are not defined by what happens when everything works. They are defined by what happens when something fails. The question I eventually had to answer was: how do I guarantee that a business event is never silently lost? The Gap Between Database Writes and Events The first version of event handling looked simple: await prisma.sale.create({ data: saleData }); eventBus.emit('sale:created', {...
Read more

RecruitX: From Reconnaissance to Remote Code Execution

I recently completed a TryHackMe room called RecruitX, a web application penetration test that walks through a realistic engagement from start to finish. This post documents the exact chain of vulnerabilities I exploited and what I would fix if I were the developer. The Setup RecruitX is an internal recruitment portal. Hiring managers post jobs, candidates apply, and administrators manage the workflow. I was given a target IP, a web-based attack box, and a simple brief: find the security issues. Reconnaissance and Enumeration I started with Nmap to discover open ports and services: Port 22: SSH Port 80: Apache 2.4.58 running the main application Port 3306: MySQL Port 8080: Apache default page The stack was classic LAMP: Linux, Apache, PHP, MySQL. I confirmed PHP session management from the HTTP headers, which showed a PHPSESSID cookie. Next I ran Gobuster for directory enumeration and found several interesting paths: /admin — admin panel, redirected to login when unauthenticated /api ...
Read more

God Never Wrote a Book: A Nigerian Agnostic's Case

Religion is a human system. It claims divine authorship for human documents. It asserts universal jurisdiction while displaying local origins. It promises moral order while producing observable dysfunction. This essay examines those claims directly. Let me be clear about what this is and what it is not. This is not an attack on believers. I grew up around believers. I know good people who believe. I know generous, thoughtful, hardworking people who also read Hebrews every morning and face Mecca every afternoon. This is not about them. It is about the systems they participate in. The claims those systems make. And the evidence those claims are supposed to rest on. Because the claims are extraordinary. And the evidence is not. The Fraud of Divine Authorship Let us start with the most basic question. How does a perfect, infinite, all-knowing being communicate with humanity, and the best delivery mechanism available is a human being with a pen? Every holy book was written by peop...
Read more