Most platforms make you pick: deep MikroTik & RADIUS control, or modern billing and self-service. ProxRad gives you both — purpose-built for the way ISPs actually run their networks.
How a MikroTik/RADIUS-native platform stacks up against the two alternatives most operators evaluate.
| Feature | ProxRad | Legacy RADIUS tools | Generic billing SaaS |
|---|---|---|---|
| MikroTik RouterOS API (deep) | ✓ | ~ | ✗ |
| Native RADIUS (MS-CHAPv2 / PAP) | ✓ | ✓ | ✗ |
| Instant CoA speed changes | ✓ | ~ | ✗ |
| Multi-tier FUP (6+6) & free-hours | ✓ | ~ | ✗ |
| TR-069 CPE / WiFi management | ✓ | ✗ | ~ |
| Account-sharing detection | ✓ | ~ | ✗ |
| Reseller hierarchy + white-label | ✓ | ~ | ~ |
| Prepaid cards & QR/PDF invoices | ✓ | ✗ | ✓ |
| Customer self-service portal + mobile app | ✓ | ✗ | ~ |
| Scales past 60K subs / node | ✓ | ~ | ~ |
| HA cluster + 30s failover | ✓ | ✗ | ~ |
| Self-hosted OR cloud SaaS | ✓ | ~ | ✗ |
| REST API + API keys | ✓ | ~ | ✓ |
| Live bandwidth graphs (Torch) | ✓ | ~ | ✗ |
Comparison reflects typical capabilities of each category as of 2026; evaluate your specific vendor before deciding.
Three reasons operators consolidate onto ProxRad.
A deep RouterOS API integration with native RADIUS (MS-CHAPv2/PAP), instant CoA speed changes, and live Torch graphs — validated past 60,000 subscribers per node thanks to a batch-fetch architecture that sidesteps the RouterOS API broker bottleneck.
Billing, prepaid cards, QR/PDF invoices, multi-tier FUP and free-hours, reseller hierarchy with white-label, TR-069 CPE/WiFi management, account-sharing detection, and a customer self-service portal plus mobile app — one system instead of five.
Run ProxRad self-hosted on your own hardware or as a fully managed cloud SaaS. Either way you get a full REST API with API keys and an HA cluster option with 30-second failover to keep authentication online.