Skip to main content

For ISPs and WISPs in Kenya

Bill customers, collect M-Pesa and control MikroTik from one console

Cloud ISP Engine matches every M-Pesa payment to the right invoice and switches PPPoE and hotspot service on or off on your routers, so your team stops reconciling by hand.

No card required. We set up your workspace with you.

  • M-Pesa matching

    STK push and paybill

  • MikroTik control

    PPPoE and hotspot

  • RADIUS

    Auth, accounting, CoA

  • Self-service portal

    Pay, usage, tickets

  • 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

Where an ISP back office loses its time

Most of it is the same three jobs, repeated every day.

  • Billing by hand

    Invoices built in spreadsheets, due dates kept in a notebook, and a scramble at month end to find out who has not paid.

  • M-Pesa reconciliation

    Customers pay with the wrong account number or from another phone. Someone matches the paybill statement to accounts line by line.

  • Router changes and late disconnects

    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

The daily work of running an ISP, in one place

Collection, service control and day-to-day operations, built around MikroTik and M-Pesa.

  • M-Pesa STK and C2B

    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.

  • PPPoE and hotspot on MikroTik

    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.

  • Built-in RADIUS

    A RADIUS server with authentication, accounting and CoA, and rate limits per package, for networks that authenticate through RADIUS instead of router secrets.

  • Invoicing and dunning

    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.

  • Customer self-service portal

    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.

  • NOC and alerts

    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.

  • Multi-tenant and resellers

    Each ISP's data is isolated from every other. Resellers get a margin, a wallet and their own customers, with commissions tracked.

  • 2FA and audit trail

    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.

Payments

Every payment lands on an invoice, or in a queue you can see

  • Each M-Pesa payment is matched to a customer and applied to their open invoices.
  • Payments that cannot be matched are listed for a person to review, not lost.
  • A daily reconciliation compares what you recorded with what M-Pesa reports, and flags payments stuck pending.
  • When an invoice is settled, suspended service is restored on the router.

How it works

From request to first payment in three steps

  1. Step 1: Request a trial

    Tell us about your network. We set up your workspace, usually within one working day.

  2. Step 2: Connect your routers and paybill

    Add your MikroTik routers and your M-Pesa credentials with us. We help import your existing customers from a CSV file.

  3. Step 3: Let payments drive service

    Customers pay by STK push or to your paybill. Invoices are settled, and service is switched on or off on the router.

Pricing

Pick a plan by the size of your subscriber base

Start with a free trial on Starter or Professional. Prices are in Kenya shillings.

Starter

For small ISPs getting started

KES3,500a month

or KES 35,000 a year, 2 months free

Start free trial
  • Up to 250 customers
  • Billing & invoices
  • Customer portal
  • M-Pesa payments
  • Email support
Recommended

Professional

For growing ISPs & WISPs

KES12,500a month

or KES 125,000 a year, 2 months free

Start free trial
  • Unlimited customers
  • Automation & scheduler
  • MikroTik monitoring
  • Hotspot & vouchers
  • CRM & tickets
  • Reports & analytics

Enterprise

For large multi-branch operators

Custom

Contact sales
  • Everything in Professional
  • Multi-tenant / branches
  • API access & webhooks
  • Advanced analytics
  • Priority support

FAQ

Questions we get from ISP owners

Plain answers about what the platform does today.

Something else? sales@cloudispengine.com

Is there a free trial?

Yes. Request a trial and we set up a workspace for you on the plan you choose. No card is required.

Which routers are supported?

MikroTik, through the RouterOS API (provisioning, live sessions, monitoring) and the built-in RADIUS server with CoA. Other router vendors are not supported yet.

How do M-Pesa payments reach the right invoice?

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.

Which other payment methods work?

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.

What happens when a customer pays late?

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.

Can I move my existing customers over?

Yes. Customers can be imported from a CSV file or through the API, and we help with larger migrations during your trial.

How is my data protected?

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.

Do you support branches and resellers?

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.

Is there an API?

Yes. A REST API under /api/v1 with Swagger documentation, webhooks and API keys.

Where does it run?

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.

Run a trial with your own routers and customers

We set up your workspace, connect a MikroTik router and your M-Pesa paybill with you, and help import your customers. No card required.