MikroTik billing, RADIUS & hotspot on autopilot
BillFi speaks RouterOS API natively. Push PPPoE secrets, hotspot users, queues and firewall rules directly to any MikroTik — plus centralised Cloud RADIUS with CoA and disconnect for instant plan changes.
Native RouterOS integration for PPPoE, hotspot, DHCP and queue-based ISPs.
What you're probably fighting today
PPPoE secrets on each router are a nightmare at 5 sites. BillFi centralises AAA and lets any router authenticate any customer.
Simple queues get out of sync with the plan the customer bought. BillFi pushes them from the RADIUS reply, always in sync.
Which customer is on which router? BillFi tracks the NAS-IP for every active session and surfaces it in the customer profile.
Everything a MikroTik automation operator needs
No scripts, no scheduled tasks. BillFi talks API directly to every RouterOS 6 & 7 device you own.
Centralised PPPoE / Hotspot / DHCP AAA with encrypted secrets and per-tenant isolation.
Change a plan → BillFi issues Change-of-Authorization; suspend a customer → Packet-of-Disconnect drops the session.
Mikrotik-Rate-Limit reply attribute pushes tx/rx, burst and priority — no per-router queue management.
Payment pages, terms URLs and captive-portal assets auto-deploy to every hotspot router.
Optional firewall address-list pushes for suspended customers when RADIUS-only isn't enough.
Live in a weekend, not a quarter
Enter IP, API port, username and password. BillFi validates, imports interfaces and appears in the router list.
One command adds our RADIUS server. Existing PPP profile becomes 'use-radius=yes'.
New customer chooses a plan. BillFi provisions the PPPoE secret in the AAA store, not on the router.
Upgrade, downgrade, pause, resume — every change is a CoA to the live session, no reconnect required.
Plays nicely with your gear
Bring the vendors you already run. BillFi drops into the middle of your stack — no rip-and-replace.
Answers, before you ask
Does BillFi support RouterOS 7?
Yes — both 6.x LTS and 7.x are fully supported, including 7-only RADIUS attributes and the new IPv6 pool APIs.
What's the difference between local users and RADIUS?
Local users live on the router (doesn't scale). RADIUS centralises AAA — BillFi becomes the single source of truth for every PPPoE / hotspot user across every router you own.
Can I still run some local users during migration?
Yes. RouterOS falls back to local users if RADIUS doesn't respond. Migrate at your own pace, one profile at a time.
Does CoA really work in production?
Yes — RouterOS 6.43+ honours CoA and PoD reliably. BillFi retries on failure and confirms via accounting stop/start events.
Network management,
automated.
Join hundreds of ISPs across Africa, Asia, and Europe automating their billing, provisioning, and support with BillFi.