Open Source MikroTik Management: Where The Other Dude Fits
Why Open Source Matters for Network Management
Most MikroTik management tools are either closed-source commercial products or cloud-hosted services that require sending your device credentials and configuration data to someone else's infrastructure. For MSPs and network operators who take security seriously, that's a non-starter.
Open source MikroTik management means you can inspect every line of code that touches your routers. You can audit the credential handling. You can verify that configuration pushes work the way they claim to. You can deploy it on your own hardware, behind your own firewall, with no external dependencies.
This isn't an ideological argument. It's a practical one. When your management platform has access to every router in your fleet, you need to trust it completely, and reading the code is the only way to verify that trust.
Where The Other Dude Sits: Source-Available, Not Open Source
Worth being precise about, since this page is about open source and The Other Dude is not open source. It is source-available under the Business Source License 1.1. Every line is published on GitHub and you can read, audit, build and run all of it — but the BSL is not an OSI-approved licence, and calling it open source would be wrong.
What that means concretely:
- Free for self-hosted production use up to 250 devices. Above that, a one-time $499 commercial licence.
- Offering it to third parties as a hosted or managed service needs a separate commercial agreement.
- On 8 March 2030 the licence converts automatically to Apache 2.0, at which point it becomes open source in the ordinary sense.
The auditability argument above applies in full — that comes from the source being published, not from the licence. What the BSL withholds is the right to resell it as a service, and the right to run an unlimited fleet without paying for it.
What The Other Dude Provides
The Other Dude is a self-hosted, source-available platform for managing fleets of MikroTik RouterOS devices. The source code is on GitHub. You deploy it on your infrastructure. Your data stays with you.
Fleet visibility. Dashboard with device health, bandwidth utilization, alerts, and wireless metrics across your entire fleet. Virtual-scrolled device tables that handle hundreds of routers. Geographic map and network topology views.
Configuration management. Browse and edit the full RouterOS config tree from the web UI. Config restores and template pushes are applied inside a RouterOS safe-mode session — if the change cuts off the management path, the router reverts itself, without rebooting. Edits made directly in the config editor are applied immediately and are not rolled back automatically. Every change is stored in git with full version history and diff capability.
Automated backups. Scheduled configuration snapshots stored in git. Navigate the timeline, compare any two versions side by side, restore to any previous state with one click.
Monitoring and alerts. CPU, memory, disk, interface traffic, and wireless metrics stored in TimescaleDB. Threshold-based alerts with email, webhook, and Slack notifications. Maintenance windows to suppress alerts during planned work.
Security. Zero-knowledge SRP-6a authentication — your password never reaches the server. Per-tenant envelope encryption via OpenBao Transit. PostgreSQL Row-Level Security for tenant isolation. Immutable audit trail of every management action.
Multi-tenant. Full tenant isolation enforced at the database level. Each organization sees only their own devices. Designed for MSPs managing multiple clients from one platform.
Self-Hosted, No Cloud Dependency
The entire platform runs in Docker containers on your infrastructure. PostgreSQL for data, Redis for caching, NATS for real-time events. No phone-home, no license server, no external API calls except optional MikroTik firmware version checks.
Setup takes about ten minutes. Clone the repository, run the setup wizard, point it at your first router. The Quick Start guide walks through the full process.
Kubernetes deployment is also supported via the included Helm chart for operators who need container orchestration.
What Published Source Means in Practice
The source code for the entire platform — backend, frontend, poller, infrastructure — is available on GitHub. You can:
- Audit the security model and credential handling
- Read exactly what API calls the poller makes to your routers
- Verify that configuration pushes include rollback protection, that it has been tested on real hardware, and which push paths it actually covers
- Extend the platform for your specific needs
- Run it in air-gapped environments with no internet access
- Contribute improvements back to the project
The project uses optional anonymous telemetry for development diagnostics — disabled by default, and you can see exactly what it collects before enabling it. No usage tracking, no analytics, no data collection that you haven't explicitly opted into.
How It Compares
There are other ways to manage MikroTik fleets. Here's how they differ from a self-hosted approach with published source:
The Dude (MikroTik) — Good for topology discovery and basic monitoring. Not a configuration management platform. No multi-tenant support. No config versioning.
Commercial platforms (Unimus, Auvik, etc.) — Solve real problems, often well. But they're closed-source, typically cloud-hosted, and require sending device credentials to a third party. Pricing scales with device count.
Generic NMS (Zabbix, LibreNMS, PRTG) — Strong monitoring but not built for MikroTik configuration management. Won't let you browse the RouterOS config tree, push changes with rollback, or manage WireGuard overlays.
Scripts and automation (Ansible, SSH scripts) — Flexible but you're building and maintaining a platform yourself. Error handling, state management, rollback logic, and a UI are all your problem.
The Other Dude is purpose-built for MikroTik, source-available, self-hosted, and covers configuration, monitoring, backups, and security in one platform.