iBilling vs WHMCS — ISP billing vs hosting billing
WHMCS is the market leader in web hosting billing. But ISP billing is not hosting billing. RADIUS, PPPoE, MikroTik, CoA, OLT, and FUP enforcement are absent from WHMCS — replaced by marketplace modules of varying quality.
Last updated: June 2026 · WHMCS data sourced from their public website
Our verdict
WHMCS is a poor fit for broadband ISPs. Its core product handles invoicing and a client portal — RADIUS, MikroTik API, CoA, PPPoE session management, and FUP enforcement are all absent. Every network capability requires a paid third-party add-on that WHMCS does not maintain. ISPs running on WHMCS spend more engineering time on integrations than on their actual network. iBilling ships everything an ISP needs in one platform — no add-ons required.
Feature comparison
| Feature | iBilling | WHMCS |
|---|---|---|
| Built-in RADIUS (PPPoE / IPoE / MAC auth)WHMCS needs BlissRADIUS add-on ($30–$130/mo) or self-managed RADIUS server | ||
| MikroTik API + CoA (Change of Authorization)Requires custom module; no native MikroTik API support | ||
| PPPoE session management | ||
| FUP bandwidth enforcement | ||
| OLT management (GPON / fiber) | ||
| bKash payment (Gateway + Webhook + PayBill)WHMCS has a community marketplace module — not officially supported | ||
| Nagad / JazzCash paymentThird-party marketplace modules; quality varies | ||
| BDT / PKR / NPR billingWHMCS supports multi-currency billing | ||
| Multi-tenant ISP SaaS (dealer hierarchy)WHMCS is a single-operator billing tool, not a multi-tenant SaaS | ||
| IP pool management (IPAM) | ||
| WhatsApp / SMS invoice automationWHMCS has email automation; WhatsApp requires third-party module | ||
| Customer portal (PPPoE self-service)WHMCS has a client portal but no RADIUS/PPPoE self-service | ||
| Starting priceWHMCS raised prices 84–135% over 6 years; increases ongoing | from $10/mo | from $34.95/mo |
| Designed for ISP billingWHMCS is built for web hosting billing, not broadband ISPs |
= Yes = Partial = No
Why choose iBilling
- RADIUS built-in — PPPoE, IPoE, hotspot, MAC auth with no add-ons needed
- MikroTik API and CoA integrated natively — disconnect/reconnect on billing events
- FUP bandwidth enforcement with hourly quota tracking
- OLT management for Huawei, ZTE, BDCOM, VSOL fiber networks
- bKash, Nagad, JazzCash, Khalti payments — no marketplace module needed
- Dealer/sub-dealer/staff/customer role hierarchy for BD ISP reseller model
- RADIUS HA with dual-VPS synchronous replication
- Starts at $10/month — no price hikes on existing plans
Where WHMCS falls short
- No built-in RADIUS — requires BlissRADIUS add-on ($30–$130/mo) or self-managed server
- No MikroTik API — router automation requires custom development
- No CoA support — cannot disconnect/reconnect sessions on billing events
- No FUP enforcement — no bandwidth quota management
- No OLT or GPON management
- bKash/Nagad via community marketplace modules — no official support
- Prices rose 84–135% over 6 years with no grandfathering
- Designed for hosting companies, not broadband ISPs
Why South Asian ISPs end up on WHMCS
WHMCS is everywhere in the BD/PK hosting industry. When an ISP operator first needs billing software, WHMCS is the obvious search result — especially if they already run a small hosting business. The low entry price ($34.95/month for 250 clients) and the large marketplace of community modules make it look like a complete solution.
The gap becomes painful fast
The problem surfaces the moment you need real ISP features. Connecting WHMCS to a RADIUS server requires separate infrastructure, a separate RADIUS management tool (usually daloRADIUS), and a custom WHMCS module to bridge billing events to RADIUS. MikroTik CoA — the standard way to disconnect a subscriber's session when they expire — has no WHMCS hook without custom development. FUP enforcement, SNMP monitoring, OLT management — none of it exists in WHMCS.
The bKash module situation is illustrative: there are several community bKash modules on WHMCS Marketplace, each maintained by different developers, with different update schedules, and none officially supported by WHMCS. When bKash changes its API (which it does regularly), you are at the mercy of a third-party developer to release an update.
The real cost of WHMCS for ISPs
When you add up the real costs — WHMCS license, BlissRADIUS or custom RADIUS server, bKash/Nagad modules, WhatsApp automation module, developer hours to integrate and maintain — a WHMCS-based ISP setup costs significantly more than a purpose-built platform like iBilling. And that is before accounting for the engineering time spent maintaining integrations instead of running the network.
Bottom line: if you run a web hosting business that also offers broadband, WHMCS may be acceptable. If you are a broadband-first ISP in South Asia, WHMCS is the wrong foundation. iBilling ships everything you need in one platform, purpose-built for the RADIUS + MikroTik + bKash + dealer-hierarchy workflow that defines the BD/PK ISP market.
Ready to switch?
14-day free trial. Migration support included on Growth and above. Most ISPs go live in 48 hours.