This is the software we build beyond client delivery: a WiFi billing platform, an M-Pesa integration toolkit, and a travel experience product. Each one reflects the way we approach architecture, payments, operations, and production support.
Step 1 · Overview
Quick snapshots of each product—what it is, who it is for, and where to go next. The deep dives below unpack architecture, operations, and proof points in full.
WiFi billing and access management
A WiFi billing platform for captive portals, subscriber billing, access control, and device management workflows.
M-Pesa toolkit for Node.js
The practical toolkit for STK Push, Dynamic QR, C2B, B2C, pull-based reconciliation, status checks, reversals, and callback-heavy Daraja…
Travel experience platform
A travel experience platform serving global users with production-grade booking, payments, and operational workflows.
Step 2 · Deep dives
The sections below are intentionally detailed: capabilities, operational realities, and what each product demonstrates about how we build. Use the navigation to jump straight to a product.
Numbered chapters—same products as above, with the full narrative and evidence we use when talking to technical buyers.
Chapter 1
WiFi billing and access management
A WiFi billing platform for captive portals, subscriber billing, access control, and device management workflows.
RoyalHub is built around the realities of running managed WiFi services. Billing, captive access, and device operations cannot live in separate silos because subscriber state, network access, and support workflows affect each other in real time. The platform brings those concerns together so operators can manage service delivery from one place.
Chapter 2
M-Pesa toolkit for Node.js
The practical toolkit for STK Push, Dynamic QR, C2B, B2C, pull-based reconciliation, status checks, reversals, and callback-heavy Daraja integrations.
PesaKit exists because M-Pesa integrations are rarely solved by a thin wrapper around a few endpoints. Real teams need help with asynchronous callbacks, reconciliation, reversals, transaction state checks, and the practical edge cases that appear when payment flows move from sandbox demos into production. The package is built to make those workflows clearer for Node.js teams.
Chapter 3
Travel experience platform
A travel experience platform serving global users with production-grade booking, payments, and operational workflows.
JetVero is a live travel product, not just a brochure site or a simple booking form. It has to combine customer discovery, transactions, and the internal workflows required to run travel operations reliably. That mix of customer-facing product design and back-office execution is where a lot of software complexity appears, and it is exactly the kind of complexity this platform handles.
If you are building a platform with payments, operational workflows, or customer-facing transactions, we can help you design and ship it with production realities in mind.