Our Work

Products, Platforms, and Open Source We Operate Ourselves

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

At a glance

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.

Platform

RoyalHub

WiFi billing and access management

A WiFi billing platform for captive portals, subscriber billing, access control, and device management workflows.

  • Built for WiFi billing and recurring access management flows
  • Supports captive portals and operational control for connected users
Open Source Package

PesaKit

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…

  • Focused SDK and docs for Safaricom M-Pesa Daraja APIs
  • Built for callback-heavy payment and reconciliation flows
Digital Product

JetVero

Travel experience platform

A travel experience platform serving global users with production-grade booking, payments, and operational workflows.

  • Serving global users on cloud-native infrastructure
  • Built from product strategy through day-to-day operations

Step 2 · Deep dives

Long-form breakdowns

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.

Product breakdowns

Numbered chapters—same products as above, with the full narrative and evidence we use when talking to technical buyers.

Chapter 1

RoyalHub

Platform
Live product

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.

Core capabilities

  • Subscriber billing, service plans, and payment-linked access workflows
  • Captive portal journeys that manage onboarding and connection access
  • Device and access control workflows for active network operations
  • Operator-facing tooling for day-to-day support and service management

Operational realities

  • Access state and billing state must stay aligned to avoid support and revenue issues
  • Captive portal flows sit directly on the first-use customer experience
  • Device management creates ongoing operational demands, not just one-time setup work

What it demonstrates

  • We can design systems where payments, access control, and operational tooling are tightly connected
  • We are comfortable building software for infrastructure-adjacent businesses, not just content or marketing sites
  • We understand admin workflows, state management, and support-driven product requirements

Chapter 2

PesaKit

Open Source Package
Live product

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.

Core capabilities

  • STK Push, Dynamic QR, C2B, B2C, reversals, and status checks
  • Pull-based reconciliation support for payment operations
  • Node.js-friendly abstractions and implementation guidance
  • Documentation aimed at teams shipping real Daraja integrations

Operational realities

  • Payment systems are asynchronous and callback-heavy, so API initiation is only part of the job
  • Reconciliation, reversals, and status visibility matter as much as the first transaction request
  • Mobile money integrations need operational clarity and maintainable code paths, not just quick demos

What it demonstrates

  • We have deep familiarity with East African payment rails and Daraja integration patterns
  • We turn repeated integration pain into reusable tooling instead of solving the same problem from scratch each time
  • We care about developer experience, maintainable interfaces, and production-ready payment workflows

Chapter 3

JetVero

Digital Product
Live product

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.

Core capabilities

  • Travel booking journeys and customer transaction flows
  • Payments embedded in customer-facing product experiences
  • Operational tooling needed to manage travel service delivery
  • Cloud-native architecture for reliability and ongoing iteration

Operational realities

  • Booking, payment, and fulfillment states have to remain aligned across the product
  • Global audiences raise the bar for uptime, responsiveness, and support readiness
  • Live consumer products require observability and day-two operations, not only initial build quality

What it demonstrates

  • We can take products from strategy and build through live operations
  • We are comfortable shipping customer-facing platforms with transactional complexity
  • We have practical experience with reliability, scale, and operational workflows in production

Need a Product Team That Understands Real Delivery Constraints?

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.