The components you mentioned include a large amount of third-party code from all over the world and rely on many external libraries. This is very different from something like WireGuard. Just performing a proper security audit on such a codebase would be a massive effort, and there could be unknown vulnerabilities or even backdoors, creating real supply-chain risk.
If MikroTik were to officially include this in RouterOS, they would be responsible for it. As we’ve seen before, even when an issue is not caused directly by MikroTik’s own code, the CVE is still assigned to MikroTik (for example, CVE-2025-10948: Cve-2025-10948
). RouterOS is released to all customers, including governments and enterprises, so the bar for security and liability is extremely high.
Using containers is not difficult anymore. If you’ve watched MikroTik’s recent container tutorial videos, you’ll see that using containers together with Socksify is already quite straightforward:
https://www.youtube.com/watch?v=ECRjxpb5IgE
On normal devices (including generic Linux, OpenWRT, etc.), deploying similar client or server software is also quite complex, and in many cases even harder to troubleshoot than on MikroTik. If you haven’t experienced that complexity, it’s usually because someone else has already done the work for you—by providing prebuilt packages, system images, or one-click scripts. RouterOS can do the same (not by Mikrotik, but by community, creating useful script, container image); it just requires people to build and maintain those solutions. There are already many container images on the forum optimized specifically for running on RouterOS.
Additionally, you can even run OpenWRT, Linux, or any environment you like inside a container, and operate your services there in whatever way you prefer.