Network & MikroTik Control

Anyone can "talk to MikroTik." The difference here is that your database intent and the physical router state are treated as separate things the system reconciles. Four distinct status fields track it: physical enabled/disabled, server reachability (C/NC), live presence (Online / Offline-with-timestamp / Left) and the PPP session address — so the UI can surface a "billed-active but actually-offline" mismatch a single on/off flag could never show.

Creating a customer auto-provisions the PPP secret, hotspot user or static queue, with the speed profile read straight from the router (package name must match the profile exactly). Pay a bill and the customer is re-enabled on the router automatically; disabling drops the live session immediately. And if a router is unreachable, the operation isn't swallowed — it's enqueued in a durable retry queue (de-duplicated, up to 10 attempts, every 2 minutes, aware of 400+ tenants) so a power outage never loses a paid customer's reconnection. For ISPs that need it, an optional FreeRADIUS layer runs per-server alongside the API path, adding NAS roaming/zone restriction and instant CoA disconnects.