About
About RosRunner
The second device makes every task twice as long. The twentieth makes it a different job entirely. RosRunner is built for the part in between.
Why it exists
RouterOS already gives you decent tools for working on a single device, and WinBox is genuinely pleasant for that — nothing here is trying to replace it. The gap shows up somewhere else: when the same small task — check a version, collect an interface list, apply one line before a maintenance window — has to happen on more devices than you want to open one at a time.
And the tedious part is usually not the command itself. It is keeping track of which devices you meant, noticing the one that timed out, and being able to say afterwards what actually happened on each of them.
Underneath the application is a library that talks to RouterOS directly, with all four kinds of connection in it. The desktop application is what that work is for: one device list feeding running commands, port monitoring, the network map and the health check.
Four commitments the product is built around
Report the truth, including the awkward parts
"Completed" means the device reached the end of your commands, not that every line succeeded. An interrupted run is reported honestly as uncertain instead of being quietly sent again. Stale monitoring numbers say how old they are rather than posing as something just read.
Show the evidence, not just the verdict
Every audit finding carries the value it measured, and every conclusion on the network map can state its basis. A verdict that cannot be verified independently is a verdict that cannot be acted on with confidence.
Read before write, and always ask before changing
The health check and the network map only read. Running commands always confirms before it sends. The one change the monitoring window can make — cutting power to a port and restoring it — has to be enabled deliberately, and is confirmed again every single time.
Say what is missing before it matters
If the kind of connection you picked cannot read every check, the application says which ones will be missing before the run starts — rather than leaving you a set of gaps that look like passes.
Who makes it
RosRunner is published under the RosRunner name; the copyright holder is Jason Chang. It is commercial software under a paid licence, and licensing enquiries go by email to support@rosrunner.com.
No company history has been invented for this page, and there are no customer logos or testimonials. Nothing confirmed exists to present, so nothing is presented.
RosRunner is an independent product. It is not affiliated with, endorsed by or certified by MikroTik. MikroTik, RouterOS and WinBox are trademarks of their respective owners.
See whether it fits your work
The feature pages describe the current build. For anything they do not cover, contact support.