Client Error
Request failed, please try again
Something went wrong!
XenFi alternative
If you are weighing XenFi against ISPman, this is what separates them — and the honest version of what XenFi is, from their own site.
XenFi markets itself as an all-in-one hotspot billing, PPPoE billing and ISP automation platform with ISPs across Kenya, Uganda, Tanzania, South Sudan, Nigeria and Zimbabwe. It describes a single cloud RADIUS billing core that handles authentication for every session, and supports MikroTik, Ruijie, Omada and UniFi hardware.
Also written Xenifi, Xenfi Systems. From their own site — check it for anything current. Not affiliated with XenFi.
Every claim below is about ISPman and is checkable — in the product, in our guides, or in the architecture we publish.
Usage updates arrive for every live session, far outnumbering logins. They are handled clear of the authentication path, so a busy evening of traffic reporting cannot keep a customer standing at a captive portal.
Every PPPoE re-dial and hotspot login is somebody waiting. Authentication scales on its own, so thousands of reconnections a minute during an outage recovery do not become a second outage.
Managed automation for MikroTik, Ruijie and Teltonika, customer ONTs from Huawei, FiberHome and others over TR-069, GPON OLTs over SNMP — and any NAS that speaks RADIUS authenticates and accounts against us, Cisco and Juniper included.
Your team runs the ISP from their phone, and the reports in it are built for decisions — where revenue came from, which sites are growing, which subscribers are about to lapse — not just a smaller copy of the dashboard.
Routers connect over WireGuard, which asks far less of a NAS's CPU and memory than the older VPNs most billing systems still require — leaving your router's resources for customer traffic.
Branch-scoped data, per-area roles down to reader and admin, an audit trail of who changed what, and white-label branding — a growing ISP does not outgrow it.
One system, one login, one database of record — not a billing panel with add-ons bolted to the side.
Switching billing systems is mostly a data problem, so that is the part we built first. ISPman imports customers from a spreadsheet, straight off a MikroTik's PPPoE secrets and hotspot users, or both together — matching the two so a subscriber who exists in each is not created twice. You map their packages onto yours, review exactly what will be written, and only then apply it.
Read the migration and onboarding guides →Onboard one router and a handful of subscribers. Take a real payment. That settles it faster than any comparison page, including this one.