Starter
For small ISPs getting started
KES3,500a month
or KES 35,000 a year, 2 months free
- Up to 250 customers
- Billing & invoices
- Customer portal
- M-Pesa payments
- Email support
Staff 2FA
Authenticator app, can be required
Audit trail
Console changes are logged
Multi-tenant
Data isolated per ISP
Resellers
Margin, wallet, commissions
REST API
Swagger docs and webhooks
The problem
Most of it is the same three jobs, repeated every day.
Invoices built in spreadsheets, due dates kept in a notebook, and a scramble at month end to find out who has not paid.
Customers pay with the wrong account number or from another phone. Someone matches the paybill statement to accounts line by line.
Every new customer or plan change means editing PPPoE secrets yourself. Overdue customers stay online for weeks, and paying customers wait for service to return.
What it does
Collection, service control and day-to-day operations, built around MikroTik and M-Pesa.
Send an STK push, or let customers pay your paybill. Payments are matched to the customer and applied to open invoices. Anything unmatched is queued for review, and a daily reconciliation compares your records with M-Pesa's.
Create and update PPPoE secrets and hotspot users through the RouterOS API. Service is suspended and restored from payment status, and hotspot vouchers can be generated and redeemed.
A RADIUS server with authentication, accounting and CoA, and rate limits per package, for networks that authenticate through RADIUS instead of router secrets.
Recurring invoices with VAT, credit notes and a wallet for overpayments. Dunning stages follow the due date: remind first, suspend later, and each stage fires once per invoice.
Subscribers sign in to pay by M-Pesa, see invoices, receipts and usage, buy a package and open a support ticket, so fewer routine calls reach your team.
A live board of router status and active sessions, with a ranked list of router, provisioning and system problems. Acknowledge an alert, or silence it for a set time.
Each ISP's data is isolated from every other. Resellers get a margin, a wallet and their own customers, with commissions tracked.
Authenticator-app 2FA for staff, which can be required for everyone. Role-based permissions, lockout after repeated failed sign-ins, and a log of changes made in the console.
How it works
Tell us about your network. We set up your workspace, usually within one working day.
Add your MikroTik routers and your M-Pesa credentials with us. We help import your existing customers from a CSV file.
Customers pay by STK push or to your paybill. Invoices are settled, and service is switched on or off on the router.
Pricing
Start with a free trial on Starter or Professional. Prices are in Kenya shillings.
For small ISPs getting started
KES3,500a month
or KES 35,000 a year, 2 months free
For growing ISPs & WISPs
KES12,500a month
or KES 125,000 a year, 2 months free
For large multi-branch operators
Custom
FAQ
Plain answers about what the platform does today.
Something else? sales@cloudispengine.com
Yes. Request a trial and we set up a workspace for you on the plan you choose. No card is required.
MikroTik, through the RouterOS API (provisioning, live sessions, monitoring) and the built-in RADIUS server with CoA. Other router vendors are not supported yet.
Customers can pay by STK push or to your paybill. Each payment is matched to a customer and applied to their open invoices. Payments that cannot be matched are listed for a person to review, and a daily reconciliation compares what you recorded with what M-Pesa reports.
Card and bank collection run through Paystack, Pesapal, Flutterwave or a direct bank transfer. Cash can be recorded by staff. Notifications go out by email, WhatsApp or any HTTP SMS gateway.
You set dunning stages relative to the invoice due date. Each stage sends a reminder, and a later stage can suspend the subscription. When the customer pays, service is reconnected automatically.
Yes. Customers can be imported from a CSV file or through the API, and we help with larger migrations during your trial.
Each ISP's data is isolated from every other ISP at the data layer. Access is controlled by roles, staff can use authenticator-app 2FA (which can be required for all staff), repeated failed sign-ins lock the account for a while, and router and payment credentials are encrypted at rest.
Resellers are built in: each has a margin, a wallet and their own customers, with commissions tracked. Multi-branch operation is part of the Enterprise plan.
Yes. A REST API under /api/v1 with Swagger documentation, webhooks and API keys.
On a Linux server with Node.js 20 and PostgreSQL. A server with a public IP address is recommended so the built-in RADIUS server and the WireGuard management VPN can receive UDP traffic.