I build the product—and the systems that keep it running.
Distributed systems · Product engineering · Developer tooling
Ghana · Elyfe Innovations

I'm a software engineer working across application code and production infrastructure. My work spans messaging platforms, distributed .NET services, web and desktop applications, and the tooling that makes them easier to build and operate.

I'm just as interested in what happens after deployment: how a service recovers, how state survives, how a release rolls back, and how quickly a trace gets you to the real problem.

• Messaging and multi-tenant platforms — SMS, USSD, billing, identity, and the operational workflows around them.
• Distributed .NET systems — Orleans virtual actors, PostgreSQL-backed persistence, durable messaging, and recovery paths.
• Web and desktop products — TypeScript applications, Tauri tooling, and offline-first workflows.
• Production engineering — Kubernetes, infrastructure as code, CI/CD, and observability that helps explain failures.

Much of my platform work lives in private repositories. The projects below are the public side of that work: libraries and tools built around problems I encounter firsthand.

A desktop Git client built with Tauri, React, TypeScript, and Rust. Bringing repository workflows into a native desktop experience, with background operations and GitHub integration. Under active development.

Orleans meets PostgreSQL. A provider suite covering grain persistence, clustering, and reminders, with Marten-backed storage and analyzers for schema configuration. Built for the details that matter in distributed applications: concurrency, isolation, and durable state.

Making Flatpak and AppImage apps feel at home on Omarchy: install-menu integration, launcher registration, and automatic updates from GitHub releases.

A maintained and modernized fork of JamaaSMPP for .NET messaging integrations, with async APIs, structured logging, and concurrency improvements.

I contribute fixes, integration work, and reproducible bug reports to tools I use. A few examples:

• Orleans / Marten: fixed client gateway address selection, merged upstream.
• Infisical .NET SDK: proposed folder provisioning support, including safe creation of nested secret paths.
• Omarchy: proposed GitHub-release tracking and automatic AppImage updates.
• AI developer tooling: proposed Pi extension SDK compatibility fixes and reported reproducible Oh My Pi startup failures.

Talk to me about distributed .NET, messaging systems, offline-first software, Linux tooling, or making production easier to understand.

Good software should be useful to the people running it—not just the people writing it.