Billing and RADIUS must agree
When invoices, payments, plans, and RADIUS policies are disconnected, support teams spend time explaining why a customer paid but still cannot connect.
ISPAgents connects billing state to access policy so the operator can see and control the full path from payment to service state.
Supported RADIUS patterns
| Pattern | Description | |---|---| | Existing FreeRADIUS | Connect to the operator's current FreeRADIUS tables, policies, or workflow. | | ISPAgents Managed RADIUS | Use cloud-managed RADIUS regions with health monitoring and operational support. | | Hybrid rollout | Keep existing FreeRADIUS while moving selected plans, sites, or customers gradually. | | Router fallback | Use MikroTik direct control when RADIUS is not the right enforcement path. |
What ISPAgents adds
- Billing-driven access state.
- Plan-to-policy mapping.
- CoA restore and disconnect flows where supported.
- Support evidence for blocked, online, slow, or mismatched users.
- Regional RADIUS health visibility.
- Connector health and audit trails.
- Migration path from existing RADIUS servers.
FAQ
Do we have to move away from FreeRADIUS?
No. Existing FreeRADIUS support is important because many ISPs already have production RADIUS deployments. ISPAgents should integrate first and migrate only when the operator wants managed infrastructure.
When does managed RADIUS make sense?
Managed RADIUS makes sense when the ISP wants fewer servers to maintain, better regional redundancy, clearer health visibility, and faster deployment for new sites.