← all articles

Why I Keep Coming Back to MikroTik

Unbranded rack router connected to an abstract cloud network

There are products you like because they are polished, and there are products you like because they keep proving useful when the work gets real. MikroTik sits firmly in the second category for me.

It is not the most fashionable networking brand. It does not always hide the complexity. In fact, part of the appeal is that it often refuses to pretend networking is simpler than it is. But once you get comfortable with RouterOS, the value proposition becomes very hard to ignore: capable hardware, deep control, sensible licensing, and a consistent operating model from physical routers through to virtual cloud deployments.

The CCR1009-7G-1C-1S+ is a good example of why MikroTik hardware appeals to me. It is a proper Cloud Core Router: rack-mountable, practical, and built around the idea that routing should be something you can shape precisely. With independent ports, an SFP+ uplink, RouterOS, and enough CPU to do real work, it feels like equipment made for people who actually need to move packets rather than admire a dashboard.

What I like most is that MikroTik does not force you into a narrow idea of how the device should be used. RouterOS gives you the building blocks: routing, firewalling, VLANs, VPNs, queues, monitoring, scripting, and service management. You can run it simply, or you can go deep. That matters, because real networks rarely stay inside the tidy diagram drawn at the start of a project.

The same thinking carries into the cloud with CHR, the Cloud Hosted Router. Being able to run RouterOS as a virtual machine means the skills, configuration patterns, and operational habits you build on the hardware carry into hosted environments. The mental model stays consistent.

That consistency is underrated. A lot of infrastructure work is not about finding the most exotic tool. It is about reducing the number of surprises. If I can use the same routing concepts, firewall rules, VPN patterns, and diagnostic commands across a physical CCR and a hosted router, I spend less time translating between platforms and more time solving the actual problem.

Then there is the hAP ax³, which is one of those devices that becomes more useful the more you travel. I like having a small router that already knows how to reach home. It has my VPN configuration, connects directly back into my network, and gives me a familiar private wireless network wherever I happen to be. Plug it into a hotel connection, join an upstream Wi-Fi network when that is the only option, and still have my own wireless side of the world behind it.

That is the practical magic of it. The hAP ax³ is not just a travel access point. It is a portable edge. My devices see the network they expect. My routing and VPN behaviour stays under my control. I do not need to reconfigure every laptop, phone, or tablet just because the building I am in has a strange captive portal or awkward network layout.

None of this means MikroTik is perfect. RouterOS rewards care. You need to understand what you are configuring, especially around firewall exposure, management access, updates, and backups. The same flexibility that makes it powerful can also make it unforgiving if treated casually. But I actually prefer that honesty. Networking gear should not encourage magical thinking.

The reason I like MikroTik is that it gives capable people a lot of capability for the money. It lets you build clean, practical network designs without immediately reaching for enterprise pricing or heavyweight controller stacks. It is just as happy sitting in a rack as it is running virtually in a cloud environment or travelling in a bag.

For me, the CCR1009-7G-1C-1S+, CHR, and hAP ax³ are different expressions of the same useful idea: own the routing layer properly. Understand it, shape it, carry it with you where needed, and keep it portable.

That is why I keep coming back to MikroTik. Not because it is the easiest platform to explain in a sales meeting, but because when I need something flexible, capable, and honest about what networking really is, MikroTik tends to be there waiting.

Matthew Ratcliffe, software developer and architect, Ballarat
Senior Software Engineer & Architect

20+ years across the technology stack — from greenfield builds to brownfield rescues. Based in Ballarat, VIC, focused on AI, healthcare and high-risk data systems. Full resume →

Share your thoughts