MikroTik multi-tenancy: managing hundreds of customers and routers without going mad

How many times a day do you switch from one interface to another, from one set of credentials to another, from one system to another just to check the status of different customers' routers? If the answer is "too many", you are probably managing your MikroTik fleet the way it was done twenty years ago: separate folders, Excel sheets and the hope of not mixing up configurations.

The problem is not that this approach does not work. It works. The problem is that it costs you a fortune in time, errors and missed opportunities.

Folder-based management: a system that scales terribly

Let's take a concrete example. You have 50 customers, each with an average of 5 MikroTik devices. That is 250 routers. If you follow the "one folder per customer" logic (or worse, one Excel file per customer), here is what happens every time you need to:

Take a backup? You have to connect 250 times, download 250 files, organise them into 250 different folders, and hope you do not overwrite yesterday's. Average time: 2-3 hours if all goes well, plus the risk of forgetting some.

Check which customer runs which RouterOS version? You have to open 250 backup files or connect to 250 routers. Or you keep an Excel sheet you update by hand (when you remember). And when someone on the team changes something and does not write it down, you are back to square one.

Apply a security policy to every customer? You copy and paste the same script 250 times, hoping not to get a single comma wrong. And if you have to change that policy three months later, you start over.

The truth is that this approach is designed to handle 10-15 customers, not hundreds. Past that threshold, every action becomes a manual operation that eats time, introduces errors and stops you from scaling.

Multi-tenancy: not just a buzzword, a change of paradigm

Real multi-tenancy does not mean "I can see all customers from the same interface". It means the system is designed from the ground up to handle many customers natively, with separation of data, policies and permissions, but with operations that can be run centrally when needed.

In practice, it means you can:

See the status of all 250 routers in a single screen, filtered by customer, by model, by RouterOS version, by connection state. Without opening 250 windows, without connecting manually, without Excel sheets to keep in sync.

Apply a configuration to 10, 50 or 200 devices at once, while keeping complete separation between customers. If you need to add a firewall rule to every business router, you do it in 30 seconds. And if one specific customer needs an exception, you apply it to them alone without touching the others.

Delegate access to your end customers securely and under control. Customer A sees only their routers, customer B sees only theirs. You keep central control, but you no longer have to act as the middleman every time somebody wants to check a value or reboot a device.

Do comparative troubleshooting. If a customer calls saying "the connection is slow", you can compare their parameters with those of 10 similar customers and immediately tell whether it is an isolated or a systemic problem. With folder-based management, that is impossible without losing hours.

The hidden costs of not being multi-tenant

Let's talk real numbers. Suppose you manage 100 customers and every month you have to:

• Back up every router (say 400 devices): with the manual approach that is 4-5 hours a month. With OptiWize it is 0 hours, because it is automatic and daily.
• Check available updates and apply them where needed: 6-8 hours a month. With a multi-tenant system you see in 30 seconds which routers are out of date and you can plan updates in batches.
• Answer 10 first-level support requests ("is the router online?", "what IP does it have?", "can you reboot it?"): 3-4 hours a month. With a multi-tenant portal where customers can see their own devices, those calls are cut in half.

Total: around 15 hours a month spent purely on repetitive work.

At 50 EUR/hour (and that is a conservative figure), that is 750 EUR a month, 9,000 EUR a year. For a single technician. And you have not scaled by an inch.

But the biggest cost is the one you do not see: missed opportunities. While you spend hours on backups and manual configuration, the competitors who automated those operations are acquiring new customers, developing new services and improving their margins.

How it works in practice

OptiWize was designed as a multi-tenant system from the first line of code. It is not a sysadmin tool with a "customer view" bolted on. It is a platform built for people who have to manage hundreds of devices across dozens or hundreds of different customers.

Separate but standardised onboarding: every customer has their own onboarding process, but you define reusable templates. New customer? You pick the "residential WISP" or "company with SD-WAN" template, enter the specific data and the system does the rest. You do not reconfigure everything from scratch every time.

Granular visibility with central control: from the dashboard you see every device of every customer, but you can filter, group and operate only on the ones you care about. Need to apply a security patch only to Premium contract customers? One click. Need to give a customer visibility on their routers without seeing anybody else's? The access policies are already there.

Unified but contextual monitoring: the monitoring system does not spin up an instance per customer (which would be an operational nightmare). It uses multi-tenant logic where every alert, every metric, every log is automatically tagged with the customer it belongs to. You see everything in one panel, but when an alert arrives you immediately know whose it is, where it is and what priority it has.

Per-customer backup and versioning: backups are automatic and daily for every device, but organised by customer natively. Want to see the configuration history of customer X over the last 30 days? It is there, with an automatic diff telling you what changed. Want to roll back? Two clicks. Want to export all of a customer's backups because they are switching provider? One command.

The real value: freeing up time to do business

The point is not just "saving hours of manual work", even though that alone would justify the investment. The point is that a well-built multi-tenant system lets you change your business model.

Instead of selling "router configuration" at 100 EUR per device, you can sell a "managed service" at 10 EUR/month per device. Instead of intervening every time a customer has a problem, you can offer proactive monitoring as part of the package. Instead of being the bottleneck for every operation, you can delegate first-level tasks to customers and focus on the ones that add value.

And when customer number 101 arrives, you do not need to hire another technician or work evenings. Because the system scales, and you do not have to.

The question to ask yourself

If you had to manage twice the customers you have today, could you do it without hiring anybody or working weekends? If the answer is no, the problem is not how good you are or how hard you work. The problem is that you are using tools designed for another era.

Managing separate folders worked when customers were few and devices even fewer. Today, in a world where an average WISP has hundreds of CPEs and a system integrator manages dozens of sites per customer, you need a different approach.

OptiWize is not just a management tool. It is a multi-tenant system built for people who want to scale without going mad. Automatic backups, unified monitoring, mass provisioning, centralised troubleshooting, all with native per-customer data separation.

Because managing MikroTik devices in 2025 with 1990s logic is not being traditional. It is just throwing money away.

Want to see how OptiWize multi-tenancy works in practice? Get in touch for a personalised demo and find out how much time (and how much money) your current approach is costing you.