NexaQuid is built in Kenya by Innoquid Tech Services, for the operators we build it alongside.
Every ISP in this region runs on the same stack of workarounds. A spreadsheet for subscribers. A WhatsApp group for faults. A paybill statement somebody reconciles by eye on a Sunday. A MikroTik whose PPPoE secrets are the real customer database, edited by hand, by whoever is awake.
It works, right up until it does not. A payment lands and nobody notices for two days, so a subscriber who has paid stays cut off and rings the desk angry. Somebody is disconnected who should not have been. A technician drives across town to a job that was closed that morning. None of it is anybody's fault; it is what happens when the record of the customer, the record of the money and the record of the network are three different things in three different places.
NexaQuid exists to make them one thing. Not by adding another dashboard on top, but by being the place the subscriber, the invoice, the payment, the session and the ticket all live — so that a payment arriving is the same event as a line reconnecting, and nobody has to remember to make it so.
We build it the way we would want it built if it were our own network, because for the people we build alongside, it is.
These are not values on a wall. Each one is a decision that is already enforced in the code, and each one costs us something — which is how you can tell we mean it.
One ISP cannot read another's data because Postgres refuses, not because every query remembered a filter. Our cross-tenant tests are written as attacks, because a policy that is merely present proves nothing.
A payment that could belong to two accounts, or to none, waits for a person. Crediting the wrong account reconnects somebody who has not paid and leaves somebody who has cut off, and neither of them hears about it from us.
Invoices, payments, receipts, stock movements and messages are append-and-correct. Nothing is deleted to tidy a screen. What you told a subscriber, and when, stays answerable.
Modules that have not shipped are labelled on this site and in the product. An ISP that discovers a gap in its first week has been sold something, and we would rather sell less and keep the customer.
Your subscribers see your name, your colours, your domain. We keep one attribution line on documents and otherwise stay out of the way.
M-Pesa is not an integration we added late. Paybill matching, STK Push, part payments and the reconciliation queue were designed first, because that is how an ISP in Kenya gets paid.
We learn more from an hour with an operator than from a month of planning. If you run an ISP, we would like to hear how you do it.
supportnexaquid@gmail.com
