Session active · Kampala, Uganda · UTC+3
I build the software that sells internet access in East Africa: the portal a customer sees, the mobile-money payment behind it, the router that lets them through, and the ledger that has to stay right.
The work
A multi-tenant platform for people who sell WiFi. Business owners run hotspots; customers pay by mobile money and get online. I am the only engineer on it, and it has been in production since February 2026.
When the captive portal lost its payment intent ID mid-flow, initiation could run again and take a second payment. I made initiation idempotent against the intent, so a retry settles onto the same charge instead of creating a new one.
Real money, real customers, no way to unsee it in the ledger.
The package request went out 83.9 KB into the document. I moved it to
2.3 KB, a 97.3% cut, and opened DNS, TCP and TLS at parse time with
preconnect, removing about 330 ms of handshake. Returning
devices now paint from cache with no network at all.
Customers are on cheap phones and thin signal. Bytes are the product.
Caching "is this session valid?" in Redis is what makes the hot path fast, and also what lets a stale yes outlive a revocation. I fenced revocation so a cached positive can never resurrect a dead session, and reconciled outstanding fences at startup. PostgreSQL stays the only authority.
Fast is worth nothing if it is fast and wrong.
I brought a second RADIUS site up in Belgium and proved failover end to end, then fixed disconnects to be site-aware, so a router is reached over the tunnel it is actually attached to, not the one that happened to report it.
Verified by taking the primary away, not by reading the config.
Also built
A tourism platform for Uganda, rebuilt from a static HTML site into a typed, server-rendered application. Multi-language with next-intl so visitors read it in their own language, and a GSAP motion layer tuned to stay smooth on low-end phones.
Next.js · TypeScript · Neon Postgres · GSAP · Zod
Lodge and campsite booking. Deployed to Cloudflare Workers through OpenNext, chosen deliberately, so a site serving visitors from anywhere runs at the edge and costs almost nothing at launch traffic.
Next.js · Cloudflare Workers · Drizzle · Neon
The operator's app: 16 feature areas covering sales, vouchers, agents, wallet, routers and live sessions. Built so an owner can run the whole business from a phone, because most of them do.
React Native · Expo SDK 54 · Zustand · EAS Build
Company platform on a Radix-based component system, with Zod-validated forms and motion used sparingly enough that it still feels like a business, not a demo.
Next.js · TypeScript · Drizzle · Framer Motion
Stack
Listed by layer rather than as a wall of logos, because knowing where a thing sits is most of knowing how to use it.
About
I am a full-stack engineer in Kampala. Most engineers with two years behind them have touched a lot of small things; I have gone a long way down one large one. PesaFii put me in the same week across a React dashboard, a React Native app, an Express API, a PostgreSQL ledger, RADIUS accounting and a router's own configuration, and made every one of those a place where being wrong costs somebody money or their connection.
That has shaped how I work. I read the system before I change it, I decide what must not break before I write anything, and I verify by taking the thing away rather than by reading the config and believing it.
Get in touch
Open to remote engineering work. The fastest way to reach me is email.