I would say that in terms of Tailscale, if I have so many tailnets I need to connect to, there are some issues in the login process that need a little bit of attention from the Tailscale team. Sometimes, you would probably need to restart your entire system for it to connect. As a DevOps as a Service engineer, I have so many clients that are using Tailscale, and I would need to connect to maybe five different tailnets because they are different clients. Client A might have a Tailscale, Client B, Client C, and so on. When changing between tailnets, sometimes it hangs. Sometimes you might need to restart your entire system. This is a bit of a headache in that aspect. However, I believe if you are just using a particular tailnet, just one, then it is quite easy and there won't be any headache. For me, I think it can be improved in the aspect of having multiple tailnets to connect to. A good refresh on the Tailscale side and the backend side to refresh the connection anytime there is a new connection to be made would be helpful. Instead of needing to restart the system, it should be able to refresh itself. The connection side and connecting to multiple Tailscale instances can be problematic, and sometimes you have to restart your system when switching between them. The ACL sometimes is like another language on its own entirely. It is fine, but they need to make it in a YAML format instead of the current format because it is quite new and something you have to go and study. If they can make it like a YAML format, that would be better. Aside from the switching which I mentioned and the fact that you have to relearn their ACL, if the ACL could be in a YAML format instead of JSON format, that would be beneficial. I don't think there is much they can do about the switching of tailnets, but if they can have a YAML format of the ACL, that would be good. Every other thing is a ten out of ten. The connection-wise is easy to set up and easy to install. It is good to have things connected all together from on-premises, from so many environments, and even exit nodes as well. It is good overall. The pricing, I think Tailscale can be a little bit on the higher side. It is not for teams with just small users. If you want to set it up for small users and a small startup, I don't think you can afford it and might need to go to other open-source alternatives. It is good for teams that have maybe fifty plus users or one hundred users. In terms of pricing, I would say it is on the higher side, but it is worth it. The price is worth the functionality. As a user, I would say it is more on the higher side, but based on its functionality, it is worth the price.
