# MikroDash

> Self-hosted cockpit for MikroTik RouterOS v7 gear: live WebSocket monitoring, RBAC plus OIDC sign-in, alerting, config backups and templates, zero-touch provisioning.

- **Category:** Network Monitoring
- **Licence:** MIT
- **Latest version:** v0.8.77
- **Open source:** oss
- **Languages:** Typescript, Go
- **Platforms:** Docker, Docker Compose
- **Tags:** Dashboard, Backups, Alerts, Dhcp, Homelab, Fleet Management, Firewall, Network Monitoring, Wireguard, Docker, Go, Golang, Self Hosted, Wifi, Mikrotik, Routeros, Zero Touch Provisioning, Network Configuration, Mikrotik Router, Mikrotik Routeros

## Description

MikroDash puts your MikroTik RouterOS v7 gear under one live web console, for homelab owners and network teams who would rather watch graphs than sit in Winbox. It talks to each router over the binary API (or API-SSL) and streams CPU load, traffic, wireless clients, DHCP leases, WireGuard peers, firewall state and geo-located connections into the browser through a WebSocket. On top of monitoring there is a drag-and-drop dashboard, more than fifty pages covering wireless, routing, tunnels, DNS, certificates and system settings, per-user roles with a read/write matrix that can scope access down to a single device, and OpenID Connect sign-in through providers such as Entra ID, Okta, Keycloak or Authentik. Alerts fire on up/down events, CPU, ping loss or configuration drift and travel over SMTP or webhooks to Telegram, Discord, Slack, ntfy and similar; scheduled backups keep diffs, a library of 21 configuration templates rolls out to the fleet with a canary router and auto-revert, history feeds CSV/PDF reports, and there is an embedded RouterOS terminal, a security audit with a score, an exportable audit log, and an optional AI assistant that works with any OpenAI-compatible endpoint, local models included. Zero-touch provisioning lets brand-new routers call home over a built-in userspace WireGuard server. Self-hosting takes one container that needs only a /data volume — a multi-arch ghcr.io image, a static Go binary, or even a container running on the router itself — though the app serves plain HTTP, so TLS belongs at a reverse proxy and the docs say never to expose it straight to the internet. It sits at version 0.8.x and is an independent community project, not affiliated with MikroTik SIA.

## Links

- [Homepage](https://github.com/secops-7/mikrodash)
- [Docker](ghcr.io/secops-7/mikrodash)
- [RouterOS container install walkthrough](https://raw.githubusercontent.com/SecOps-7/MikroDash/main/docs/routeros-container-install.md)
- [Collector architecture](https://raw.githubusercontent.com/SecOps-7/MikroDash/main/docs/Collector-Architecture.md)
- [GitHub issues](https://github.com/SecOps-7/MikroDash/issues)

---
Source: https://selfhost.directory/project/mikrodash