Iterative Billing vs Gradius
TL;DR: Gradius is the more focused choice for teams prioritizing hotspot and PPPoE billing, subscriber workflows, and MikroTik management with fewer modules to configure. Iterative Billing is better suited to ISPs that want billing plus NOC and device management features (RADIUS/CoA, SNMP, OLT, TR-069), but should expect more setup and verification of scope per market.
Run ISP billing, network ops, and accounting in one place

Cloud billing and subscriber management for ISPs

Iterative Billing vs Gradius at a glance
Scores are 1–10 per criterion. The highlighted cell wins its row; tied rows carry no marker.| Criteria | ||
|---|---|---|
| Pricing How clear, predictable, and potentially cost-effective pricing is, including minimums, setup fees, revenue share, and how easy it is to estimate total monthly cost. | 7wins More numeric detail (including caps), but still complex and date-sensitive. | 6 Usage-based, but country-by-country totals are hard to confirm. |
| Billing and subscriber management (core ISP workflows) Strength of core ISP billing features, including packages, renewals/expiries, suspensions, subscriber records, hotspot vouchers/captive portal flows, and operational controls tied to billing events. | 8 Covers core billing plus adds control layers like built-in RADIUS. | 8 Strong focus on hotspot and PPPoE billing with automation. |
| Network operations and device management Breadth and usefulness of NOC and device management tools beyond billing, such as monitoring, topology/maps, RADIUS/CoA, OLT provisioning, and CPE management (TR-069). | 9wins Broad ops suite: RADIUS/CoA, SNMP, network map, OLT and TR-069. | 6 Primarily billing-first, with some fiber/OLT claims to verify. |
| Payments and African market fit Support for African payment rails (mobile money, local gateways), reconciliation/automation, local currency support, and practical suitability for operators across African markets. | 8 Explicit list of regional rails, but availability still varies by market. | 8 Strong Africa positioning with local currency pricing and common gateways. |
| Integrations and ecosystem compatibility How well each product connects to common ISP infrastructure and third-party tools, including MikroTik, OLTs, payment processors, and operational workflows. | 8wins Broader named integrations across payments and network tooling. | 7 MikroTik-first, with payment and OLT integrations to validate. |
| Ease of implementation and day-to-day usability Expected deployment effort, configuration complexity, learning curve for staff, and how quickly a typical ISP can become operational. | 6 Broader suite can be powerful, but usually needs more setup and training. | 7wins Narrower scope likely reduces rollout complexity. |
| Support, reliability, and trust signals Evidence of support quality, uptime/reliability history, SLAs, customer reviews, and overall confidence signals for production use. | 5 Limited independent reviews and no verified SLAs surfaced publicly. | 5 Support tooling is mentioned, but service quality is hard to verify. |
How clear, predictable, and potentially cost-effective pricing is, including minimums, setup fees, revenue share, and how easy it is to estimate total monthly cost.
Strength of core ISP billing features, including packages, renewals/expiries, suspensions, subscriber records, hotspot vouchers/captive portal flows, and operational controls tied to billing events.
Breadth and usefulness of NOC and device management tools beyond billing, such as monitoring, topology/maps, RADIUS/CoA, OLT provisioning, and CPE management (TR-069).
Support for African payment rails (mobile money, local gateways), reconciliation/automation, local currency support, and practical suitability for operators across African markets.
How well each product connects to common ISP infrastructure and third-party tools, including MikroTik, OLTs, payment processors, and operational workflows.
Expected deployment effort, configuration complexity, learning curve for staff, and how quickly a typical ISP can become operational.
Evidence of support quality, uptime/reliability history, SLAs, customer reviews, and overall confidence signals for production use.
Both Gradius and Iterative Billing target internet service providers that need to automate subscriber onboarding, package renewals, and payments, commonly across PPPoE, hotspot, and mixed wireless and fiber deployments. They are often compared by African WISPs and fiber operators because they both emphasize mobile-money friendliness and operational automation, two necessities in many markets where customers prefer M-Pesa-style rails and field teams need lightweight tooling.
At a high level, Gradius presents itself as a cloud billing and subscriber-management system with core ISP workflows: hotspot captive portals and vouchers, PPPoE packages with expiry automation, MikroTik management, payment gateways (including mobile money where available), SMS notifications, and staff roles with ticketing. Its positioning suggests a narrower, billing-first scope that may be easier to adopt if you already have separate monitoring or accounting tools.
Iterative Billing positions itself as a broader suite, combining billing and payments with network operations and back-office capabilities. Beyond PPPoE and hotspot, it advertises built-in RADIUS with CoA, SNMP monitoring and analytics, a live network map, Huawei OLT provisioning, TR-069/ACS for CPE management, accounting features, and mobile apps. For operators trying to reduce tool sprawl, that breadth can be compelling, but it also increases the need to validate which modules are mature, supported in your market, and included in your commercial plan.
In both cases, publicly verifiable evidence on uptime history, support responsiveness, and real-world customer sentiment is limited, so most decision-making will hinge on product fit, a country-specific price quote, and a short pilot on your own network.
Full analysis, criterion by criterion
Each criterion below breaks down the same 1–10 scores product by product, with the reasoning behind each rating.Pricing
How clear, predictable, and potentially cost-effective pricing is, including minimums, setup fees, revenue share, and how easy it is to estimate total monthly cost.
▾
Pricing
How clear, predictable, and potentially cost-effective pricing is, including minimums, setup fees, revenue share, and how easy it is to estimate total monthly cost.
Gradius
6Gradius publishes usage-based pricing (2.5% of paid hotspot revenue plus a per-active PPPoE user fee that varies by country), and it mentions a local monthly renewal floor. However, public Kenya numbers appear inconsistent across sources (one mentions KES 500 base plus KES 20 per PPPoE user), so a current quote is needed for accurate comparisons. The model can scale smoothly, but it is harder to forecast without the exact local fee card.
Iterative Billing
7Iterative Billing lists specific rates, for example in Kenya it is described as KSh 15 per active PPPoE/static-IP customer per month, a 2% hotspot revenue fee (capped at KSh 3,000), plus a KSh 1,000 monthly minimum and KSh 1,000 setup fee. Outside Kenya it is described as $0.135 per active customer, 2% hotspot revenue, with a $9 minimum and $9 setup. The main drawback is complexity (caps plus minimums) and the stated effective date should be confirmed before budgeting.
Billing and subscriber management (core ISP workflows)
Strength of core ISP billing features, including packages, renewals/expiries, suspensions, subscriber records, hotspot vouchers/captive portal flows, and operational controls tied to billing events.
▾
Billing and subscriber management (core ISP workflows)
Strength of core ISP billing features, including packages, renewals/expiries, suspensions, subscriber records, hotspot vouchers/captive portal flows, and operational controls tied to billing events.
Gradius
8Gradius emphasizes hotspot billing (captive portal and vouchers), PPPoE packages, and expiry automation, which are the day-to-day essentials for many WISPs and small fiber operators. It also lists staff roles and support tickets, which can help operationalize customer care around billing events. Public information is strong on feature claims, but there is limited independent validation of depth (for example edge cases around proration, migrations, or complex corporate accounts).
Iterative Billing
8Iterative Billing includes PPPoE/static IP and hotspot management, voucher flows, and payment-linked service activation, which matches common ISP billing needs. Its inclusion of built-in RADIUS with CoA suggests tighter coupling between billing status and access control. As with Gradius, the functional breadth is mostly vendor-described, so it is worth testing your specific lifecycle flows (renewals, grace periods, suspensions, and reinstatement) in a pilot.
Network operations and device management
Breadth and usefulness of NOC and device management tools beyond billing, such as monitoring, topology/maps, RADIUS/CoA, OLT provisioning, and CPE management (TR-069).
▾
Network operations and device management
Breadth and usefulness of NOC and device management tools beyond billing, such as monitoring, topology/maps, RADIUS/CoA, OLT provisioning, and CPE management (TR-069).
Gradius
6Gradius clearly positions around billing, subscriber management, and MikroTik-related operations, and it also advertises fiber/OLT management and synchronization with several OLT vendors plus SmartOLT. The limitation is that publicly verifiable detail on OLT coverage, supported models, and production readiness is limited. If OLT provisioning is central to your rollout, validate device compatibility and workflows before committing.
Iterative Billing
9Iterative Billing explicitly advertises NOC features (SNMP monitoring, outage history, loss/latency/throughput metrics) and a live network map, plus Huawei OLT provisioning and TR-069/ACS CPE management. This scope can reduce tool sprawl for teams that currently stitch together multiple systems. The tradeoff is implementation and ongoing configuration effort, and you should verify which device families and dashboards are included in your plan.
Payments and African market fit
Support for African payment rails (mobile money, local gateways), reconciliation/automation, local currency support, and practical suitability for operators across African markets.
▾
Payments and African market fit
Support for African payment rails (mobile money, local gateways), reconciliation/automation, local currency support, and practical suitability for operators across African markets.
Gradius
8Gradius advertises local-currency pricing across many markets and mentions mobile money and local gateways, plus Stripe and PayPal for international cards. This is a good fit for multi-country operators or those expecting local payment preferences. The key uncertainty is which payment integrations are fully live per country and whether any require custom setup or extra fees.
Iterative Billing
8Iterative Billing names multiple African payment options including M-Pesa Daraja (Paybill, Till, STK Push), Pesapal, Flutterwave, Paystack, MTN MoMo, and WaafiPay. The specificity is helpful when planning regional expansion. As with any payment stack, confirm which rails are supported in your country, settlement timelines, and whether you get automatic reconciliation or need manual mapping.
Integrations and ecosystem compatibility
How well each product connects to common ISP infrastructure and third-party tools, including MikroTik, OLTs, payment processors, and operational workflows.
▾
Integrations and ecosystem compatibility
How well each product connects to common ISP infrastructure and third-party tools, including MikroTik, OLTs, payment processors, and operational workflows.
Gradius
7Gradius highlights MikroTik management and claims all plans include unlimited MikroTik routers, plus hotspot and PPPoE billing. It also mentions multiple payment gateways and OLT synchronization options. The main limitation is uncertainty about integration maturity across different markets and device vendors, so a proof-of-compatibility test is important.
Iterative Billing
8Iterative Billing lists MikroTik RouterOS v6/v7 support, Huawei OLT tooling, TR-069/ACS, and a wide set of payment gateways, which indicates stronger coverage across ISP domains. This can simplify procurement and vendor management if you want one suite. Confirm the exact integration method (native, partner, or custom) and any constraints like supported RouterOS/OLT firmware versions.
Ease of implementation and day-to-day usability
Expected deployment effort, configuration complexity, learning curve for staff, and how quickly a typical ISP can become operational.
▾
Ease of implementation and day-to-day usability
Expected deployment effort, configuration complexity, learning curve for staff, and how quickly a typical ISP can become operational.
Gradius
7Because Gradius is positioned around billing and subscriber workflows, it likely involves fewer modules to configure than an all-in-one ops suite. That can mean faster time-to-value for small teams focused on payments, packages, and access control. There is limited independent usability evidence, so expectations should be validated via a trial using real provisioning and payment scenarios.
Iterative Billing
6Iterative Billing’s wider feature set (monitoring, mapping, OLT, TR-069, accounting) can reduce tool switching, but typically increases initial configuration and onboarding effort. This may be worthwhile for more mature operators with dedicated NOC processes. Public sources do not include usability benchmarks, so plan for a structured pilot and admin training time.
Support, reliability, and trust signals
Evidence of support quality, uptime/reliability history, SLAs, customer reviews, and overall confidence signals for production use.
▾
Support, reliability, and trust signals
Evidence of support quality, uptime/reliability history, SLAs, customer reviews, and overall confidence signals for production use.
Gradius
5Gradius lists support tickets as a feature, but publicly available sources do not provide verified SLAs, response-time commitments, or an uptime track record. Independent customer review coverage is also limited, reducing confidence. If reliability is critical, request SLA terms, incident history, and references during procurement.
Iterative Billing
5Iterative Billing is positioned for African ISPs, but there is little publicly verifiable evidence on uptime history or support responsiveness, and some listings report no reviews yet. Without third-party feedback, risk assessment relies on direct vendor diligence. Ask for support coverage by country, escalation paths, and operational references from similar networks.
Verdict: which should you choose?
The verdict weighs the criterion scores against who each product serves best.Choose Gradius if your priority is straightforward ISP billing and subscriber management (hotspot plus PPPoE), especially when you want a simpler surface area focused on packages, expiries, payments, SMS, and MikroTik operations. Its usage-based model can work well for smaller to mid-sized operators, but you should confirm the exact country pricing (including any local minimum) and which payment and OLT-related integrations are actually available in your market.
Choose Iterative Billing if you want a single platform that goes beyond billing into NOC visibility and device provisioning, for example built-in RADIUS with CoA, SNMP monitoring, network mapping, Huawei OLT workflows, and TR-069/ACS. The tradeoff is higher implementation complexity and more variables in pricing (per-active-customer fees, hotspot revenue share, caps, minimums, setup fees). For most ISPs, the best next step is a pilot that validates your critical flows (PPPoE auth, payment reconciliation, suspension/reactivation, vouchers, and reporting), then compare the total monthly bill at your current subscriber counts and hotspot volumes.
Some details in this comparison could not be fully verified. Please double-check the following before making decisions:
- Exact current pricing for Gradius in Kenya could not be independently verified because public references appear inconsistent; confirm via a direct quote.
- The effective date and current applicability of Iterative Billing’s published pricing (notably references to October 1, 2026) could not be independently verified; confirm current terms before budgeting.
- Uptime history, incident frequency, and formal SLA terms for both Gradius and Iterative Billing could not be verified from publicly available sources.
- Country-by-country availability and maturity of specific payment and OLT/TR-069 integrations for both products could not be verified; some integrations may require custom setup or may not be available in every market.
- Independent customer sentiment (reviews, case studies with measurable outcomes) is limited for both products, so support quality and long-term reliability cannot be confidently compared.
Iterative Billing vs Gradius FAQs
Which is better for a small WISP that mainly needs PPPoE and hotspot billing?
▾
If you want a billing-first system with hotspot vouchers/captive portal, PPPoE packages, payment collection, and basic operations, Gradius is positioned as the simpler, more focused option. Iterative Billing can also do PPPoE and hotspot, but its broader modules may add setup overhead you do not need at the start.
Which platform is more suitable if I want monitoring, network maps, and device provisioning in the same tool as billing?
▾
Iterative Billing advertises the stronger NOC and device management bundle, including SNMP monitoring, outage history, a live network map, Huawei OLT provisioning, and TR-069/ACS. Gradius mentions fiber/OLT capabilities too, but public detail is thinner, so you would want to validate depth and compatibility.
How do the pricing models compare for Kenyan ISPs?
▾
Iterative Billing is described with explicit Kenya figures (KSh 15 per active PPPoE/static-IP customer per month, 2% hotspot revenue fee capped at KSh 3,000, plus KSh 1,000 minimum and KSh 1,000 setup). Gradius is described as usage-based (2.5% hotspot revenue share plus a per-active-PPPoE-user fee that varies by country), but public Kenya numbers appear inconsistent, so you should request a current Kenyan quote before comparing totals.
Do both support African payment methods like M-Pesa, and can they also take cards?
▾
Both products emphasize mobile money and local gateways. Gradius mentions mobile-money and local payment gateways plus Stripe and PayPal for international cards, while Iterative Billing lists M-Pesa Daraja options and aggregators like Pesapal, Flutterwave, and Paystack (availability varies by market). In either case, confirm your specific country’s supported rails and reconciliation behavior.
What is the biggest risk when choosing between them today?
▾
For both Gradius and Iterative Billing, the biggest gap is limited independently verifiable evidence about reliability, SLAs, and support responsiveness. A short pilot that tests real subscriber lifecycles (payment to activation, expiries, suspensions, and reinstatement) plus vendor diligence (references, incident history, and contract terms) will reduce selection risk.
