Works on any host, any cloud
NoRouter does not depend on any cloud infrastructure.
What you need is just “remote shell” connectivity such as ssh, docker exec, or kubectl exec.
No routing configuration is needed
NoRouter does not need any messy routing configuration, because NoRouter works by transferring L3 packets over stdio streams of “remote shell” commands.
No root privilege is needed
NoRouter does not need any privilege such as sudo or docker run --privileged, because
NoRouter only uses loopback addresses such as 127.0.42.101, 127.0.42.102.