FreeRADIUS Foundations — Guided pilot
Guided pilot: signed Status-Server probing and opt-in SQL accounting import. CoA/Disconnect drivers have fake-transport proof only; live NAS mutation and full policy integration remain unqualified.
Integration status and evidence
Keep the current access policy authoritative
Guided pilot: The existing-FreeRADIUS path offers a signed Status-Server probe and opt-in SQL accounting import. These foundations do not establish customer synchronization or live policy changes.
Guided pilot: signed Status-Server probing and opt-in SQL accounting import. CoA/Disconnect drivers have fake-transport proof only; live NAS mutation and full policy integration remain unqualified.
Define the evaluation boundary
Before a pilot, agree on the server and network path to probe, approved credential handling, expected response and escalation owner. Use the approved onboarding process for credentials; never put them in a demo request.
Keep the incumbent authoritative for users, policies and accounting. Write down how a failed or missing probe will be investigated without changing subscriber policy.
Distinguish separate RADIUS paths
The paid-but-offline article explains bounded accounting-worker behavior. Opt-in accounting import is distinct from live policy enforcement; a fresh session record does not prove that a payment restored access.
Compare managed RADIUS Guided pilot options and the RADIUS guide, then review billing foundations against your actual requirements.
Frequently asked questions
Does the existing-FreeRADIUS adapter synchronize SQL users?
No. The Guided pilot includes signed Status-Server probing and opt-in SQL accounting import, not SQL/API user synchronization. CoA/Disconnect drivers have fake-transport proof only; live NAS mutation and full policy integration remain unqualified.
Does a successful probe prove subscriber access?
No. A probe response is separate from subscriber authentication and current session evidence. Managed RADIUS is a Guided pilot; it and the local accounting lab are separate evaluation paths.
Continue the operations map.
Controller Integration Planning
Guided pilot: External references, import preview/apply jobs, connector profiles, and sync-run records are foundations for a guided pilot. Live UISP and Splynx adapters still require implementation.
Open pageIntegrationsMikroTik Integration — Guided pilot
Guided pilot MikroTik RouterOS REST operations: backup/export and discovery foundations. Guarded writes and RouterOS 6 fallback remain product work.
Open pageSolutionsAutomatic Internet Suspension Software — Guided pilot
Guided pilot: Preview, queued jobs, approvals, result recording, and a mock-safe worker can be evaluated in a guided pilot. Live router/RADIUS mutation remains gated; automated suspension and restoration are not a shipped promise.
Open pageSolutionsCustomer Self-Service Foundations — Guided pilot
Guided pilot: Field-job lifecycle, serialized stock, basic tickets and subscriber portal flows have narrow synthetic-data proof and remain guided pilots. Physical installs and invite email delivery are unproven. The technician PWA, dispatch board, dedicated stock workspace and IPAM remain roadmap.
Open page