Does it cost anything, or do I need an account?
No and no. The tool is free and there is no account. You do not have to leave an e-mail address.
Do my passwords go to your server?
No. The tool runs in your browser and everything you type stays there, passwords and keys included. What we do measure is how the tool is used: which parts get switched on, which model is chosen, how often a board or a plan is built. Those are counts, not content. It is written down in the licence and privacy text.
Which RouterOS version is the script for?
For v7. Under System you choose which v7 version you generate for, so lines that differ per version come out right. For v6 there is the v6 import to convert to v7, but we do not generate v6 configurations.
Does it work on my model?
If it is in the list, yes. The ports, radios and Wi-Fi package come from our catalogue per model. If your model is missing, pick the nearest one from the same series, use Some other MikroTik at the end of the grid, or tell us. See Choosing your device.
What happens if I change the model halfway?
The sections go back to the defaults for that new device. Port names, radios and the default WAN simply differ per model. So pick your device first. See Choosing your device.
Can I do several devices at once?
Yes. In site mode you put a router, switches and access points together, fill in VLANs, SSIDs and the password once, and get a script per device plus checks across the whole site. See Multiple devices in one site.
Why can I not click a section?
Because it cannot apply to this device. The section says why: no wifi radio, no wired ports, or containers requiring ARM64 or x86. The same goes for roles in the wizard that are greyed out. See Advanced.
Can I add my own RouterOS lines?
Yes. At the bottom of every section in advanced mode is a box for extra lines. What you type there lands in the script right after that section's output. See Advanced.
Can I paste the script on a device that is already running?
You can, but it is not what it is built for. The script assumes the device is empty. To change something on a running router, use the import and the comparison: then you see exactly which lines are added and you can paste only that part.
Why do I have to reset first?
Because MikroTik's factory configuration already contains a bridge, addresses and firewall rules. A second set on top gives you duplicate rules and behaviour nobody can follow any more. Starting empty is the only way it stays predictable.
How do I get back if it goes wrong?
Three ways, in this order: the backup you made in step 1, the rollback script that sits next to your script, and otherwise a reset. Always paste with Safe Mode on, so RouterOS rolls everything back if you lose your connection. See Using the script.
What do I hand to the customer?
The handover sheet: a readable summary of ports, VLANs, addresses and Wi-Fi, with room for the date and a signature. Passwords are only on it if you tick the box. See Documenting and handing over.
My switch runs SwOS, does that work too?
Partly. SwOS has no command line, so there is no script to paste. You get a setup sheet saying tab by tab what to fill in, and a push script that is still in beta. See Switches running SwOS.
How do I know whether I have Wi-Fi everywhere?
Draw your floor plan with the real walls and place your access points; the map colours the signal per spot and per room. It stays an estimate, so measure after installing. See The Wi-Fi plan.
Can I keep the result?
Yes. Your work stays in your browser, per project. You can also export it as a file, as text or as a link. See Saving and sharing.
Is it safe to use for customers?
We use it ourselves. Two things to keep in mind: use /export hide-sensitive when importing a configuration you do not manage yourself, and remember that a shared link can be opened by anyone who has it.
Which languages is the tool in?
Dutch, English, German, French and Spanish. The manual follows the same addresses per language, so a link keeps working when someone shares it in another language.
What if the script does something I do not want?
Read it before you paste it: the whole configuration is on screen. If something we generate is wrong, report it and we will change it. That is exactly how the tool grew.
Why are there warnings on my configuration?
Because we would rather say something than quietly assume. An error is a real mistake, a warning is something to decide about deliberately. They point at the part they are about, and often at the chapter that explains it.
Can I have a say in what gets added?
Yes. The roadmap shows what is planned and lets you vote. If you need something else, use the form or Discord. Much of what is in the tool came from users' replies.