FreeRADIUS Integration
Keep your existing FreeRADIUS where it works, or move selected access workflows to Managed RADIUS early access after tenant launch signoff.
Integration status and evidence
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 should connect billing state to access policy only after the operator has mapped subscribers, NAS devices, policy names, CoA behavior, and rollback expectations.
RADIUS rollout patterns
| Pattern | Description |
|---|---|
| Existing FreeRADIUS | Validate the operator's current FreeRADIUS tables, policies, or workflow before writes. |
| Managed RADIUS early access | Use the ISPAgents-operated shared plane after tenant validation, launch signoff, health checks, and operational support gates. |
| Hybrid rollout | Keep existing FreeRADIUS while moving selected plans, sites, or customers gradually. |
| Router fallback | Use MikroTik direct control only when RADIUS is not the right enforcement path. |
What ISPAgents adds
- Billing-driven access-state evidence.
- Plan-to-policy mapping.
- CoA restore and disconnect flows only where the NAS and tenant policy support them.
- 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 as commercial early access after the ISP validates the cloud auth path, NAS secrets, failover behavior, support evidence, and tenant launch signoff.
Continue the operations map.
Controller Integrations
Pull devices, topology, and telemetry from external controllers — Ubiquiti UniFi, Cambium cnMaestro, and UISP — into one tenant-scoped pane, mapped to canonical devices. Read-only and safe. This is early access.
Open pageIntegrationsMikroTik Integration
Use MikroTik RouterOS as the network enforcement layer while ISPAgents coordinates billing, payments, support context, approvals, and audit evidence.
Open pageSolutionsAutomatic Internet Suspension Software
Design suspension and restoration workflows without losing control by connecting billing, payment evidence, RADIUS, MikroTik, custom agents, approvals, and rollback evidence.
Open pageSolutionsCustomer Self-Service App
A phone-first app for an ISP's subscribers — view plan and balance, track data usage, pay, and open support — branded to the operator. Account and usage are live today; CPE controls are on the way.
Open page