MikroDash
Real-Time Open-source command center for MikroTik RouterOS v7. Streams live CPU, traffic, wireless clients, DHCP, WireGuard, firewall and geo connection data straight from the router API to your browser over a WebSocket. Alerts, reports, config management and zero-touch provisioning. One static Go binary, self-hosted, Docker-ready
Runs with mockssource: GitHubGoMITcommit 2269c083b8d1
Go, MIT licensed. The project labels itself: dashboard, docker, fleet management, golang, homelab, mikrotik, mikrotik router and mikrotik routeros.
MikroDash runs, with stand-ins for the services it depends on. An Argusic agent installed it in 42 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Go source builds and all Go tests pass; 94 of 96 web tests pass with polyfills for Node.js v18 gaps; the mikrodash binary starts and serves HTTP on port 3082, redirecting to /login
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Web tests failed: require('typescript/unstable/sync') is ESM-only in TypeScript 715 minutes
- Web tests failed: ReferenceError: CustomEvent is not defined in Node.js v1810 minutes
- Web tests failed: ReferenceError: crypto is not defined in Node.js 18 CJS files8 minutes
- dashboard-wiring test module list out of sync with ported code (27 problems)5 minutes
- config-management test assertion failed: expanded row not open (pre-existing port issue)
- Install time
- 42 minutes
- Cold machine to finish
- 42 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- go test ./... exited 0 (all packages ok); node web/test/run.mjs exited 0 (94/96 pass); go build ./cmd/mikrodash/ succeeded; /tmp/mikrodash -data /tmp/test-data -listen :3082 started and curl returned 302 on GET /
- Model tokens used
- 911,360
- Exact commit tested
- 2269c083b8d1
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
echo "Now: $(date +%H:%M)" # Simple minutes calc echo "Elapsed roughly 27 minutes"' in /work/repo succeeded in 0ms: Build start: 01:20 Now: 02:02 Elapsed roughly 27 minutes 2026-10-17T02:02:12.882896Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce… 2026-10-17T02:02:21.019037Z ERROR codex_core::session: failed to record rollout items: thread 01a14… 2026-10-17T02:02:21.019077Z ERROR codex_core::session: failed to record rollout items: thread 01a14… tokens used 911,360
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 42 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 8 dashboard projects Argusic has installed and timed, MikroDash was the 7th fastest to reach a running state, and 6 of 8 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.19 |
Topics (from GitHub)
dashboarddockerfleet-managementgolanghomelabmikrotikmikrotik-routermikrotik-routerosnetwork-monitoringrouterosself-hostedwireguard
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mikrodash)Questions
- Does MikroDash run?
- MikroDash runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 42 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test MikroDash?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2269c083b8d1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test MikroDash?
- The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does MikroDash take to install?
- 42 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does MikroDash need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing MikroDash?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does MikroDash compare with the alternatives?
- Of the 8 dashboard projects Argusic has installed and timed, MikroDash was the 7th fastest to reach a running state, and 6 of 8 reached one at all.
- Where is the evidence for MikroDash?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.