We build the systems
Kenyan businesses run on.
Then we run them.
ISP operations, mobile money, commerce and identity infrastructure. Software that talks to the router, reconciles the payment and opens the ticket — not another place to type up what already happened somewhere else.
- ISP tenant · instance 01
- Optical polling · 30 min interval
- ISP tenant · instance 02
- Isolated credentials · circuit breaker
- ONUs per poll cycle
- Alerting + auto ticket creation
- Ticket escalation
- Time-based · reassigns support group
- M-Pesa channels
- Live in production
The outage gets logged correctly.
Nobody acts on it until morning.
This isn't a monitoring failure. SmartOLT sees the ONU go dark at the exact minute it happens — the record is right there. What's missing is the step after: something that reads that signal at 2am and acts on it, instead of waiting for a human to notice in the morning.
Below is the same real incident, once without that layer and once with it. The equipment and the failure are identical — only the four hours in between change.
- 02:14
ONU on Node 14 loses signal. SmartOLT logs it correctly.
- 02:14
Nobody is watching the dashboard. No ticket, no alert sent anywhere.
- 06:40
A customer messages asking why they've been offline all night.
- 06:52
An agent checks SmartOLT by hand and finds the outage.
- 07:10
A ticket is opened manually in Splynx, referencing nothing.
- 02:14
ONU on Node 14 loses signal. SmartOLT logs it correctly.
- 02:14
The next poll cycle catches it and opens a Splynx ticket automatically.
- 02:14
Deduplicated against Node 14's history. Assigned tier 1.
- 02:44
No update in 30 minutes — escalates to tier 2, wider group notified.
- 03:08
Resolved.
Illustrative timeline based on the ISP operations platform's actual poll interval and escalation rules — exact timings vary by network. See the full case study.
Five things, each one running somewhere right now.
We do not have a services page full of capabilities we have never shipped. This is the list, and every item below links to the system that proves it.
ISP & network operations
Poll the OLT on a schedule, raise an optical alert, open the ticket in the billing platform, deduplicate it, and escalate through four tiers if it stays open.
Payments & mobile money
Take payment by paybill, till or STK Push, consume the bank webhook, and reconcile it against the right account without anyone matching references by hand.
Ecommerce & growth
A storefront that takes mobile money and reports which channel produced the sale, because the measurement is wired in before launch rather than after.
Identity & attendance
Card plus fingerprint, matched on the card itself. The credential is bound to one person, so it cannot be handed to someone else at the gate.
Platform engineering
Containerised deployment, CI with type and vulnerability gates, backed-up and transaction-wrapped database changes, and isolated credentials per tenant.
Not a partner list. These are the APIs, protocols and hardware our production systems talk to every day.
Systems in production, not concepts.
Each of these is running for a real operator or business. The screenshots are the actual interfaces, not mockups.
ISP operations platform
Optical monitoring, billing and bank payments in one operations system. Two operators run on it, isolated from each other.
Hotspot billing
Customers pay by mobile money and get network access without anyone touching the router.
Blessed Collections
A storefront that takes mobile money and reports where the sale came from — instrumented at build time, not bolted on.
Asset tracking & kiosk
QR-based asset tracking with a gate-attendant kiosk, attendance and task records.
Biometric attendance & identity
Tap card plus fingerprint. The card is bound to one person, so it cannot be passed to a friend at the gate.
Numbers that belong to a specific system.
Nothing here is a round marketing figure. Each one comes from a system we can point at.
ISP operators running on the same platform, with isolated credentials and independent failure handling
ISP operations platformoptical network units polled per cycle, with alerting and automatic ticket creation
ISP operations platformescalation tiers that reassign the support group and raise priority without a human deciding to
ISP operations platformM-Pesa channels live in production — paybill and till — behind one checkout
Blessed CollectionsShipping it is the easy half.
The systems we build handle money and network infrastructure, so the deployment path matters as much as the code. Nothing reaches production without passing the same gates.
How we work- 01Docker Compose on AWS EC2
- 02Images to AWS ECR
- 03GitLab CI/CD
- 04Lint + tsc --noEmit gates
- 05Trivy vulnerability scanning
- 06Transaction-wrapped migrations
- 07Pre-flight database backups
- 08Per-tenant credential isolation
Different businesses, the same missing layer.
ISPs & connectivity operators
The problemYour monitoring, billing and payments live in three systems that do not speak. A customer is offline for hours before anyone notices, and the ticket gets opened by whoever happens to look.
What we doOne operations layer over the equipment you already run, raising and escalating tickets on its own.
Read moreCommerce & retail
The problemThe store is live, orders come in, and nobody can say which channel produced them. Marketing spend is a guess because nothing was instrumented at launch.
What we doA storefront that takes mobile money and reports the path to every sale, measured from day one.
Read moreSchools, colleges & HR
The problemAttendance is a register or a shared card. Records are reconstructed after the fact, and nobody can prove who was actually present.
What we doCard plus on-card fingerprint, bound to one person, posting to a backend others can integrate with.
Read moreThe ones people actually ask.
Can you integrate M-Pesa into a system we already have?
Yes. We work against the Safaricom Daraja API and have paybill, till and STK Push flows running in production, including bank webhook reconciliation. We can add payments to an existing system without rebuilding it.
Do you work with our existing billing platform?
Usually. We build on top of platforms operators already run — Splynx for ISP billing, SmartOLT for optical monitoring — rather than asking you to migrate off them. The integration is the product.
Do you maintain systems after launch?
Yes, and it is most of what we do. Our systems run on infrastructure we deploy and monitor: containerised on AWS, deployed through CI with vulnerability scanning, with backed-up and transaction-wrapped database changes.
Do you build ecommerce stores?
We build stores that take mobile money and report where each sale came from. Analytics and conversion tracking are wired in at build time rather than added later, so the store is measurable from day one.
Where are you based?
Nairobi, Kenya. We build for Kenyan and East African operating conditions — mobile money, local billing platforms, and hardware that is often several hours away from the nearest engineer.
Tell us what breaks, and we'll tell you
whether we're the right people to fix it.
A short conversation about what you run today, where the manual work sits, and what it would take to close the gap. If it is not a fit, we will say so.