Do you actually need a MikroTik router?
No. This is one of the most common assumptions we run into, and it's simply not true. A WiFi billing system needs one thing from your hardware: the ability to redirect an unpaid customer to a payment page and let them online once they've paid. MikroTik does this well and is common in Tanzania — but it is one option, not a requirement.
Any access point or router that speaks RADIUS — the open standard for exactly this job — can do the same thing, often with less setup than MikroTik needs.
What works instead of MikroTik
| Hardware | How it connects | Notes |
|---|---|---|
| TP-Link Omada (EAP) | RADIUS | UpesiNet hosts the Omada controller for you — no controller of your own needed |
| Cudy | RADIUS / UAM | Built-in captive portal on the device itself, firmware 2.4.4+ |
| Cambium | RADIUS | Enterprise-grade, common in larger hotspot deployments |
| Ubiquiti/UniFi | RADIUS | Also hosted for you, same as Omada |
| Ruijie, Ruckus, OpenWrt, Grandstream, Meraki | RADIUS | All connect the same way |
Every one of these plugs into UpesiLipa the same way: the access point checks a customer's payment against our RADIUS server, and we tell it yes or no in real time. Nothing to install on your side beyond the access point itself.
The one thing Omada and UniFi need that MikroTik doesn't
Omada and UniFi are built around a controller — a piece of software that manages the access point. Running your own controller means a computer that has to stay on. UpesiNet removes that requirement entirely: we host the controller for every operator, on our own servers. You adopt your access point onto omada.upesilipa.com, and from that point on it behaves exactly like any other billing-ready device — no separate machine to keep running, no separate cost.
Cudy — the simplest of the three
A Cudy access point needs nothing hosted at all. Its own captive portal screen points straight at your UpesiLipa pay page — set the firmware to 2.4.4 or newer, put it in Wireless Router mode, and paste in your pay page link. That's the whole setup.
Cambium — for bigger sites
Cambium's enterprise access points are common where an operator is covering a larger area — a market, a compound, several buildings. They speak RADIUS the same way Omada does, and connect to the exact same billing backend with no special-case setup.
MikroTik or RADIUS — which should you actually pick?
- Already own MikroTik? Use it — UpesiLipa connects to it natively, nothing extra to buy.
- Starting from zero, want the least to manage? TP-Link Omada with our hosted controller means nothing on your end but the access point itself.
- Want the absolute simplest single box? Cudy's built-in portal needs no controller of any kind, hosted or otherwise.
- Covering a large area? Cambium's enterprise APs are built for that scale.
None of these is the "correct" choice over another — it comes down to what you already own and how much coverage you need. UpesiLipa bills correctly on all of them.
Already own Omada, Cudy or Cambium hardware?
UpesiLipa connects to it directly — no MikroTik, no controller of your own to run. UpesiNet hosts what needs hosting.
Ask a Question on WhatsApp Get Started Free at UpesiLipa.comFrequently asked questions
Can I run a WiFi billing system without a MikroTik router?
Yes. UpesiLipa supports RADIUS-based hardware directly, including TP-Link Omada, Cudy, Cambium, Ubiquiti/UniFi, Ruijie, Ruckus, OpenWrt, Grandstream and Cisco Meraki — no MikroTik needed at all.
Do I need to buy or run my own Omada controller?
No. UpesiNet hosts an Omada controller for every operator at no extra cost — adopt your access point onto it and it's immediately ready to take mobile money payment.
Can I mix MikroTik and non-MikroTik sites on one account?
Yes. One UpesiLipa account can run a MikroTik site at one location and an Omada, Cudy or Cambium site at another, all reporting into the same dashboard.
Does pricing change if I don't use MikroTik?
No. The same plans and pricing apply regardless of which hardware you connect — see UpesiLipa's pricing for details.