What kind of ISP
are you running?
ISPStack ships the same product to every operator, with sensible defaults for whichever shape your network takes. Pick the one that looks like you and jump to what matters.
Fixed-wireless ISP
You run MikroTik-style NAS, sectors and APs across rooftops, and customers want hotspot top-ups via M-Pesa.
See the fitFibre / FTTH operator
You run an OLT shelf or two, ONUs sit at customer homes, signal levels matter as much as billing.
See the fitHotspot / venue operator
Cafés, hostels, transport hubs, event venues. You sell wifi by the hour or the gig.
See the fitMulti-site / parent group
You run several ISP brands or country-level subsidiaries and need one platform with tenant isolation by default.
See the fitFixed-wireless ISP
You run MikroTik-style NAS, sectors and APs across rooftops, and customers want hotspot top-ups via M-Pesa.
- Sector capacity creeping up; no quick way to see which AP is over-subscribed
- Hotspot vouchers printed on a spreadsheet, sold at a stall, reconciled by hand
- Customers on PPPoE expect M-Pesa top-up, USSD top-up, AND a captive portal
- NAS provisioning + drift detection (push profile, audit weekly)
- Hotspot vouchers with batch print + redemption tracking
- M-Pesa STK push + walled-garden release in one CoA flow
Fibre / FTTH operator
You run an OLT shelf or two, ONUs sit at customer homes, signal levels matter as much as billing.
- OLT vendor portal is a separate world from your billing book
- Customer says it's slow; tech has to log into the OLT to read signal
- ONU provisioning still goes through 3 tools and an Excel file
- OLT integrations (Huawei / ZTE / V-Sol / BDCom) on the customer record
- Live signal levels + CRC stats attached to the open ticket
- ONU bind / decommission from the customer page; no vendor portal
Hotspot / venue operator
Cafés, hostels, transport hubs, event venues. You sell wifi by the hour or the gig.
- Vouchers printed on a thermal till; redemption count is "approximate"
- Splash page is whatever came with the router. Branding? Not really.
- When the customer pays, you wait a beat — manual is the only way to top up
- Branded captive portal at your venue subdomain, plan tiles + voucher entry
- Voucher batches with redemption tracking; pay-per-use beyond your tier
- M-Pesa STK push from the portal; CoA-release the second the code clears
Multi-site / parent group
You run several ISP brands or country-level subsidiaries and need one platform with tenant isolation by default.
- Each subsidiary keeps its own spreadsheet; consolidated reporting is an end-of-quarter project
- Brand consistency is fine on the parent site, then breaks the moment you log into a child portal
- Finance wants one P&L, ops wants the per-region view
- Hard tenant isolation at the row level; per-tenant currency + branding
- Cross-tenancy reporting for the parent without exposing sibling data
- Centralised platform admin for finance + ops; each tenant stays sovereign
Not sure which fits your network?
Tell us about your operator size, your customer mix, and the kit you're already running. We'll show you the path.