I have been using Tailscale for approximately one to one and a half years for one of my projects. My main use case for Tailscale during that project was connecting different GCP GKE clusters. I had different production, staging, and testing clusters, and we wanted a way to easily connect to any of the clusters. Tailscale allowed us to easily access any of the clusters we wanted from a local system.

I chose Tailscale for this setup because I was searching for different projects to connect different clusters, and I found Tailscale online. There were quite good reviews about Tailscale, which was one of the reasons I chose it to connect different clusters. Tailscale is quite easy to deploy and get started with.

The setup process and documentation for Tailscale stood out to me because the documentation is quite good and the setup is quite easy. You just need to install a single binary on your system and you are ready to go. You can easily connect to any of the systems that you want.

The best features Tailscale offers for me are how easily we can connect to different clusters and different systems. If I have a system somewhere around the globe and I want to connect directly from my local system, it is quite easy. I just need to have Tailscale binary on my system, and I can connect to that specific system.

I did not face any issues with latency or connection reliability while using Tailscale; it was quite seamless for me. Connecting was quite easy.

I discovered some ACL features while exploring Tailscale later on, and I think they are quite good. We can configure some IPs through which we can connect, and I think that is one of the good features Tailscale has.

I think Tailscale is quite good for me as I am not a power user. I have mostly used it for basic use cases, and I feel that nothing is missing for me. If there were any power users who have used Tailscale extensively, they might give some feedback on what can be improved upon, but for me, it was good and suitable. I cannot think of anything that needs to be improved upon.

I have been working in my current field for more than four years.

Tailscale is stable.

Regarding Tailscale's scalability, we did not use it at a large scale since our team is small, but I think it is good.

Tailscale customer support is good.

I did not previously use a different solution because we directly went with Tailscale. We did not have any other solution before that.

My main use case for Tailscale during that project was mostly about connecting different GCP GKE clusters. I had different production, staging, and testing clusters, and we wanted a way through which we could easily connect to any of the clusters. Tailscale allowed us to easily access any of the clusters we wanted from a local system.

The time saved by using Tailscale is significant because earlier, when we wanted to connect different clusters, we used to run GCP commands to connect them. With Tailscale, it was quite easy. We were still running the command, but we did not need the specific command anymore because it was just Tailscale binary, and it was quite easy to connect to any of the clusters we wanted. We have seen a return on investment from Tailscale since it was a time-saving tool for us. We did not need different GCP commands to connect to different clusters; it was just a single Tailscale binary through which we were connecting, making it a time-saving solution.

My experience with pricing, setup costs, and licensing for Tailscale is that since our team is quite small, about ten people, we did not take any license and the cost was zero for us because we were using Tailscale's open-source version.

Before choosing Tailscale, I thought about evaluating other options, but there was another tool called WireGuard, which Tailscale is based upon. I did not look for any other tool further because I felt that Tailscale was good and would do my job.

I advise others looking into using Tailscale to go for the documentation and just read over the things, as it is quite easy to set up. I think anyone can set up Tailscale. Tailscale is a good tool to use, and it is quite friendly without hassle to set it up. My rating for this review is nine out of ten.

My main use case for Tailscale is access to internal resources and supporting clients, having replaced two different VPN products I was using previously.

I have a number of applications that are running within my network. I have used the split DNS for accessing internal resources or supporting clients.

Using split DNS with Tailscale has helped me manage access and support my clients by being able to use my internal DNS servers easily within the network without needing to have full tunnel connections. It has worked great for exposing particular applications to clients who are shared to particular nodes on my tailnet.

The best feature Tailscale offers is the ease of use for managing WireGuard and the fact that the key management is completely transparent, both for the WireGuard tunnel connection and for the SSH functionality.

The transparent key management and SSH functionality have benefited me by completely eliminating a manual, tedious step of needing to manage keys, which felt like a significant security risk that something could go wrong in the key management process. With Tailscale, it just happens and works.

Tailscale has positively impacted my organization and consulting work by making remote connections easy, significantly reducing the friction and making this very reliable, even behind difficult networks with CGNAT or other situations that make establishing connections difficult using other means.

I think if there was a streamlined mechanism to self-host the control plane, that would be a significant help in certain regulatory environments where customers feel unsure about having an external party control authentication onto the tailnet. Even with Tailnet Lock, there is still a concern that there are parts of the control plane that are opaque.

I have been using Tailscale since September of last year.

Tailscale is stable.

I have not hit the limits of Tailscale's scalability, which works well under automation and infrastructure as code. It is scalable from the perspective I am able to see.

I have not had much of a need to interact with customer support, but the only thing that I have used it for is to establish a custom OIDC identity provider, and the response felt quick and professional.

I previously used self-hosted WireGuard and OpenVPN connections because they had difficulty getting through in particular CGNAT connections, and that was the initial impetus for looking at Tailscale.

My experience with pricing, setup cost, and licensing was straightforward and seemed fair for the value that the product provides.

My company does not have a business relationship with this vendor other than being a customer.

I do not have any metrics to share. Qualitatively, it definitely feels as though time troubleshooting connectivity has decreased.

Support issues related to connectivity have dropped by about half, and while I do not have an exact measure, the amount of time spent working on connectivity issues has decreased significantly.

I did not purchase Tailscale through the AWS Marketplace.

I also evaluated Twingate and ZeroTier before choosing Tailscale.

My advice to others looking into using Tailscale is to give it a try and make sure that it suits your needs, but overall, it feels like a stable product that greatly simplifies VPN and remote connectivity needs. I would rate this product a nine out of ten.

I have been using Tailscale for three to four years now for personal use and for my volunteer and business work.

My main use case for Tailscale is maintaining my personal network that I use for family and friends. It is easy to set up on pretty much any device.

I use it for getting around port forwarding restrictions. For example, if I have a network on my school computer that I cannot port forward from, I can plug a VPN into it and port forward onto the VPN.

Tailscale has been beneficial for hosting game servers with friends online. It is useful for situations where you need to get around firewalls and restrictions. You need a VPN to secure your networking because many of these game servers do not have encryption by default when they are small games. It is helpful to be able to set that up.

The best features Tailscale offers include ease of startup. Once you log in on your Google account, you can add other people's Google accounts or use emails if they do not have one. There are all sorts of options available. I used it a while ago to set up, so I am not sure how the current setup options are, but it is very useful in that aspect.

Tailscale has been very helpful for setting up a VPN network in various locations when you might not have the time to set up port forwarding or configure servers on each end. When you just want something quick and ready to go, it is the solution for you. It is really good for that.

This quick setup with Tailscale has saved me probably days of work that I would have spent learning how to configure traditional VPN solutions, more traditional solutions like WireGuard, where I would have had to learn their entire configuration process and it would have taken days just to set that up. After that, I would have had to replicate it on every machine I use.

I think Tailscale can be improved by enhancing the free side of things. It is really useful for people who are students or personal users who are not business users to keep going with the free version because it expands your user base. If you can get people to realize that this is actually a good product, they will be willing to pay for the paid version.

The process of adding other users with their Google accounts or emails was challenging at first when I was figuring out how to add other emails. I thought I would have to sign in on my Google account each time, but once I discovered that you could invite people, that was when it really took off.

My advice for others looking into using Tailscale is to make sure it has the features you need for the payment plan you are willing to go for. There are multiple payment plans, and if you want more users or more devices, you have to pay more, but make sure it has what you need for the payment you are willing to offer.

I mainly use Tailscale for remote access to my services. I have my whole server setup at home, which is a Proxmox cluster where I have a couple of services running on the backend, and I want to access those services remotely such as websites, some Docker containers, and some stacks. I install Tailscale on those applications so that I can access them remotely from my PC, whether at home or somewhere else. I turn on Tailscale and use it.

I have a mixed environment in my backend, which includes a couple of Windows VMs, all my servers being Linux-based, my Mac environment, my iPhone, and my MacBook that I bring outside, so I install Tailscale on those devices. I also have my router in pfSense where I install Tailscale as well.

I use Tailscale mostly on-premises to access all of my services. I could deploy it on cloud services such as AWS or Azure, but I already have my own environment, so everything is just within the premise.

I find troubleshooting to be very easy with Tailscale, as I turn it on everywhere I go, and I can access my services remotely and securely without worrying about a certificate or anything. Another advantage of Tailscale is that sometimes I need to be physically at home to troubleshoot or to do something for myself or for my business. Tailscale has this service called Exit Node, so when I am outside, I turn on Tailscale and enable the Exit Node. I install this in two devices in my home lab, allowing me to route my network through those devices even if I am physically outside, which means other companies see me staying at home doing my work.

MagicDNS is really good because I do not have to remember the IP address of all of my devices or services, and I also use split DNS as well, where some of the networking requests actually go through my pfSense router and bounce to some of the local devices that I have here.

One thing I want Tailscale to improve is their user interface for Arch Linux, which is one of the devices I have that I installed Tailscale on, but they do not have the native package with full features, a capability I really want them to develop. Another enhancement would be to allow a graphical interface for more power users. Sometimes I want to run things on the website or user interface, so I wish to control advanced access control lists with a good user interface, and that would really be helpful.

I have been using Tailscale for two years, and it has been going great.

Tailscale has been very stable in my experience, with no issues so far. I would suggest for other users that when you want to upgrade the service or the app for security reasons, sometimes Tailscale app, especially on iOS, might break, so it is better to see any updates and maybe wait for a couple of days for feedback before upgrading the apps.

Tailscale's scalability seems very good, as I install it and currently have around twenty or thirty apps running on my web admin in Tailscale. I believe Tailscale uses AWS services as a base, so I think they have no issues scaling up the services.

So far, I do not have any issues with Tailscale. If I do, I go to Reddit, which I think is one of the official channels for them, and there are a lot of Tailscale staff that respond in that channel, allowing me to ask questions there.

I had been using another service before, which is WireGuard, but the thing for WireGuard is that I had to open ports on my router to be able to use it remotely. Tailscale uses WireGuard technology, and the speed is the same, but the setup for Tailscale is very easy, which is a very good point.

Before Tailscale, I used WireGuard, but I had to open a hole in my firewall for port forwarding. After finding out that Tailscale is a very easy mesh P2P network, I completely switched to Tailscale because it is very easy.

I think Tailscale is very easy to use, and that is the best thing that I would add here.

I find the process of installing Tailscale on all those different devices fairly easy, where I just run a command, a CLI command, to install it. There are two ways: I either find the command by adding the device from Tailscale user interface, or I just run the command directly on the device, and they will give me a link to click to activate the device. However, one thing that I want to add for Tailscale is that sometimes I need a very simple user interface to control my services. Most of my devices can install it and have a native setup with a user interface, but I have Arch Linux on one PC, and I could not find the applications from Tailscale that natively support that app.

I notice a lot of time saved with Tailscale because it is very easy to set up, and I think it saves around forty percent of the time to turn on and manage my remote environment. Everything is pretty smooth.

Before choosing Tailscale, I evaluated other options such as Cloudflare, Cloudflare Zero Trust, and some services such as Headscale as well. However, when I bumped into Tailscale and tried it, it hooked me right away, primarily for its remote access, easy setup, and multi-environment support.

Tailscale has been helping my organization a lot, primarily for security, as I do not have to open up any port in my router, which is really helpful. There are other options to access my services and applications remotely, such as Cloudflare Tunnel, but that again exposes risk to the public. Even with their zero trust network, it still feels somewhat risky. However, for Tailscale, everything is encrypted in the mesh network, the speed is really good, and I really appreciate that. Tailscale also offers it for free for three users and up to one hundred applications or nodes, and I am still using that, which is really good. I think for others, if they want to try Tailscale, they can register for free first and try it out; there is no harm in that.

I am still using the free tier of Tailscale, but I have a lot of services under it. Pricing seems good because they offer, as I mentioned, up to three users and one hundred apps or services for free, so I am still trying it out, and the service and the speed are pretty good.

I recommend that Tailscale users take advantage of the offering of a free tier and try it first. I give this product a review rating of eight out of ten.

My main use case for Tailscale is mesh networking, wherein prior to Tailscale, especially on personal infrastructure, I needed to have a VPN setup that required port forwarding enabled from my ISP side. The main issue with that is that mostly ISPs do not provide static IP addresses as well as port forwarding on personal plans. The most important feature I have seen in Tailscale is its use of NAT traversal to enable internal network access to the outside world in a secure, peer-to-peer manner. Essentially, it replicates the corporate IT VPN infrastructure at a smaller scale, allowing anyone without much technical know-how to install and configure Tailscale. For example, if you want to connect to your home server and route all your traffic through it, that can be achieved simply by using the exit node option in Tailscale, which I find really impressive.

Furthermore, the Magic MagicDNS feature allows me to associate domain names with services running on each individual Docker container in my home lab, enabling access to them as dedicated websites within the Tailnet. If I disconnect from the Tailnet, I cannot access these services, adding another layer of security. I use TSD-Proxy for this, which is an add-on endorsed by Tailscale.

On the corporate side related to my project with Alliance, I have used Tailscale to mimic the corporate IT environment where everything is accessible only within the intranet, not the outside world.

During COVID-19, I collaborated with friends from different locations, one of whom was in the Gulf while I was in India. There was a scenario where I needed a personal VPN connected to a server in the Gulf to perform government-related tasks. My friend was not very technical, primarily being in commerce, but by explaining how to install Tailscale and enabling his laptop to act as a server and an exit node, I was able to get a seamless VPN connection without going through the ISP for a static IP or port forwarding, just one click. This was a very impactful personal use case.

On an enterprise level, I previously mentioned my project with Alliance, where the judges were really impressed with the mesh-to-mesh VPN demonstration that did not require much configuration. They even expressed interest in implementing it at a corporate level. Additionally, as mentioned, with Docker containers, there are various add-ons available. For an efficient setup, I recommend using TSD-Proxy alongside Docker containers, allowing for better management of exit nodes and accessibility settings based on flags set during container creation.

Tailscale has positively impacted my organization by enabling rapid prototyping, especially with junior teams collaborating from various locations. When accessing remote machines over SSH or protocols like RSTP for CCTV cameras, Tailscale allows us to establish a mesh VPN with just a few clicks. Otherwise, configuring a VPN server by ourselves would involve OpenVPN or WireGuard and obtaining permissions from ISPs, a considerable hassle, particularly when some team members are not technical, such as project managers. Tailscale has simplified collaboration significantly at the organizational level.

MagicDNS is one standout feature, along with role access control (ACLs) that enhances the security of my Tailnet. Plus, there is the usual multi-factor authentication, the ability to run exit nodes, and having one of my nodes function as a subnet router, allowing access to my internal LAN from the outside without hassle. Those are a lot of features. Moreover, you do not really need in-depth security knowledge to get started with Tailscale, and since it is an open-source project audited by many people globally, you can trust its foundation. Tailscale is based on WireGuard, a very secure protocol for VPNs.

With MagicDNS, I find it helps tremendously as I run multiple containers, making it hard to remember all the IP addresses. MagicDNS simplifies this by letting me configure domain names, enabling seamless access to web pages or services within my Tailnet in a short time. Secondly, ACLs help in deciding the permissions for exit nodes, allowing access only to specific resources they need, streamlining the process. For everything else, I can set the appropriate permissions in the ACL list without needing to be a network analyst.

Regarding improvements for Tailscale, it abstracts its internal workings from the end user, which is great for those not familiar with networking. However, I would appreciate a graphical view, perhaps through something Grafana, displaying how packets are transmitted, involved intermediaries, and current active nodes. This kind of feature would enhance user experience and technical awareness. A developer's mode versus a normal user mode could be beneficial, in my opinion.

I do not have any additional thoughts on the needed improvements besides those already mentioned.

I have been using Tailscale for almost two to three years.

Tailscale is stable; it has never given me downtime on their side, and if there is downtime, it is due to issues on our side, not from Tailscale.

Tailscale's scalability is impressive due to the available Docker images, offering numerous options across platforms. Scalability is not a concern at all, and platforms like Kubernetes can also utilize it, making it highly adaptable.

In terms of customer support, the product is so good that personally, I never needed to use customer support, although the networking team at my organization may have. However, for my use case, I have not had to reach out for support because everything is so seamless. Even hobbyists can find valuable information shared voluntarily in subreddits, so with such a quality product, individual customer support needs diminish significantly.

Before Tailscale, we used an OpenVPN server, but due to networking constraints and the difficulty in managing credentials among individual users or junior developers connecting from different locations, we opted for Tailscale and have been very satisfied with it.

I did not evaluate other options prior to choosing Tailscale; I had heard great opinions online, which made me fixated on it, and I am convinced I made the right choice since it has served me well for a long time now.

Since using Tailscale, we save time through the enhanced rapid prototyping it enables. Cost savings are also notable, especially personally, as static IPs or port forwarding often result in additional charges from ISPs. For someone interested in IT or as a hobbyist, Tailscale is a great option to explore VPN dynamics at an individual level. Furthermore, thanks to Tailscale, corporate companies no longer need to provide static IP or port forwarding capabilities for employees, which translates into significant savings, especially for larger companies with many employees.

I advise others considering Tailscale to go for it if their needs align with ours. There is no better option than this. Corporate VPN setups tend to be overly complex, and for small to medium enterprises, Tailscale is precisely what is needed. It is just great; go for it.

We use Tailscale because we work for so many companies and each company has their own way of allowing their employees to connect to their infrastructure. We use Tailscale primarily for this purpose. For example, if there are Kubernetes clusters and engineers need to connect to the cluster to run their local applications against it, they connect using Tailscale. Additionally, we sometimes establish connections between on-premises and cloud environments. The first case involves ensuring that clients' employees have access to resources such as Kubernetes clusters, and the second case involves making connections between on-premises and cloud infrastructure, which makes it easier to connect.

Let me give you a quick simple example of how I've used Tailscale for one of my clients. One of our clients wanted their engineers to be able to connect to the cluster internally instead of going through the public internet. We introduced them to Tailscale and set up the tailnet in Tailscale. The tailnet in Tailscale enabled us to install a Tailscale operator on each cluster. For instance, if our client has ten clusters, we install the Tailscale operator to expose the subnet router of each environment to the tailnet. Users can connect to the tailnet, and since the subnet router is already exposed to the tailnet, they can have access to their clusters through the subnet routers that are already exposed to the tailnet. This is how they can connect to the Kubernetes cluster. The reason is because we don't want users to connect through the public internet, and in the setup of the Kubernetes cluster, we only allowed one or two specific VPN connections. The only way we can allow employees to connect is through the tailnet. We installed a Tailscale subnet router on each cluster, which exposed the cluster VPC and networks in the tailnet. When employees connect to the tailnet, since the subnet router is already exposed to the tailnet, they can connect through the tailnet.

There is another scenario where clients are trying to access their on-premises data to the cloud. Instead of using a cloud VPN, which would be a headache and could cost a lot, we decided to use Headscale. Headscale is similar to Tailscale because Tailscale is the enterprise version while Headscale is the open source alternative. We set up Tailscale for them on-premises and on the cloud. We set up a Tailscale tailnet on the cloud, and we set up a subnet router on-premises and another subnet router on the cloud. Both subnet routers will connect to the tailnet on the cloud and expose their VPCs. The one on the cloud will expose its VPC to the tailnet and the one on-premises will expose its VPCs to the tailnet. Machines on-premises can connect to machines on the cloud through the tailnet connection. The machine in the tailnet that is on-premises serves as a subnet router, and the one on the cloud also serves as a subnet router that routes traffic from the cloud to the tailnet, while the one on-premises serves as a subnet router that routes traffic from the on-premises to the tailnet.

When a connection needs to be established, for example from the cloud to the on-premises, we create a routing policy that says if you want to talk to a specific IP which is on on-premises, go through the subnet router. The same thing applies with the on-premises as well. If you want to talk to a specific IP on the cloud, go through the on-premises subnet router. This way, it connects to the tailnet which has exposure of the cloud IPs, and the connection is made.

I would say one of the best features Tailscale offers is the ACL, the Access Control List. Tailscale has positively impacted my organization very well. We don't have any VPN issues or VPN connection issues typically, and we don't really maintain them. We just make sure the tailnet is available. Tailscale has really helped in terms of security because users can be in another part of the world. Instead of them connecting to the company environment through the local network there, they can switch on their Tailscale and once they switch on their Tailscale, they don't have to connect over their internet; they just go through Tailscale to access company infrastructures. In terms of security, it is very good.

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.

I have been using Tailscale since I joined CloudKites, which is almost three years now. I would say three years.

Tailscale is very stable. I haven't had any issues with it, and it has always been stable. It is good.

Tailscale is a SaaS platform, so Tailscale scales it themselves. This is why, as I said earlier, I don't have any issues with stability, as it scales on their end. However, if I am installing a subnet router, scaling it is also easy. You probably just need only one pod or one node to expose your VPC or your network to the tailnet. In terms of scalability, there is no issue there. It is a ten out of ten.

Tailscale customer support is cool, but we miss the human interaction. The support is all right.

Tailscale customer support is very good. They always want to help every time. I would give it a ten out of ten.

Previously, we have used a cloud VPN. I think it can be a little stressful, especially if you have so many environments to maintain. It is not combined into one. If you have ten clusters, you have to maintain them individually. There is no single interface where you can manage all ten cloud VPNs; you have to be managing them separately.

As I mentioned, we have explored cloud VPN. There is another one I have heard about which is NordLayer. I haven't tried it, but I think it is just purely a VPN. It is not something that you can use to expose subnet routers, exit nodes, and other features that Tailscale offers. I think it is just a pure VPN. Personally, cloud VPN is the only one we have explored, but it does not have enough capabilities compared to Tailscale.

I think Tailscale has shown a return on investment in terms of time saved because it is a SaaS platform. It provides time savings instead of maintaining a VPN. You just make sure you have a Tailscale account, then you install the subnet router or exit node on any of the environments you want to use it on. You just set them up and you should be good.

I would tell others looking into using Tailscale to go ahead if they can evaluate their infrastructure setup or how they want employees to access that infrastructure, and if they have their finances for it, then sure, you can go. Tailscale is a very good product for companies and teams generally, particularly for infrastructure, DevOps teams, and developer teams. It is very good for them. They should go ahead and use Tailscale. However, if money is going to be an issue, they can look into open-source products. However, with open-source products, you still have to maintain the infrastructure on how you set up the tailnet. Aside from that, go ahead with Tailscale if you don't want to manage the infrastructure of your entire tailnet. Just use the normal Tailscale product.

Personally, I don't really have much other improvement to suggest. It is cool the way it is. Aside from the two things I mentioned regarding ACL format and multiple tailnet switching, Tailscale should be solid.

I don't have much else for Tailscale. I just think it is a good product for people to use, especially if they want to make sure the connectivity is secured, and if you want to establish connections in many ways that are possible. Overall, I give Tailscale a rating of eight out of ten.

My main use case of Tailscale is for creating a VPN between Kubernetes services in Oracle Cloud, other servers, and my PC to connect with them, and I also use it to expose some services, so instead of port forwarding some services of Kubernetes, I use Tailscale, which makes things very easy and usable.

Regarding exposing services, I use Grafana and for Tailscale, I expose that service so I can access it through the VPN instead of port forwarding the service. I also use it to expose a Kafka UI service, and I use Kafka in my job.

The best feature I like in Tailscale is the Tailscale operator, which is a very intelligent way to connect your Kubernetes cluster with any other device.

In my job, Tailscale has reduced the amount of work and headache of having a VPN between servers and cloud, so instead of following a longer and complex process of having a site-to-site VPN and a device with a fixed public IP to connect with the cloud and other spots in Morocco, especially in Tangier, Tailscale simplifies all of that.

It reduces work, so I was supposed to have a complex job that requires technical knowledge to do some networking tasks, but Tailscale provides a very straightforward solution to avoid a lot of work.

I still do not have any issues in mind that need improvement, but if I think about a new feature or something to be improved in the future, I may share it with you.

I have been using the solution for about seven months.

Tailscale is very stable in my experience.

Tailscale's scalability is actually so good; I have not faced any downtime or issues, so every time I use Tailscale, I get what I expect.

Before Tailscale, I used Headscale, which is an open-source implementation of Tailscale. I deployed Headscale to avoid dependencies, but it had many downsides; it did not have an operator for Kubernetes and needed many features, so Headscale was not enough. I also used OpenVPN, but it does not have the integrations and intelligence that Tailscale has, so I am satisfied with Tailscale and I will continue to use it for many months.

I evaluated Headscale, but it was not enough compared to Tailscale.

I think it is a very good solution; however, I think a ten is something very perfect, and I feel Tailscale has many things to do in the future, such as getting more integrations into other things.

For others looking to use Tailscale, I want to tell them you will not regret it ever; Tailscale is a very good and useful solution.

I think it saves me time and money since the current tier I use is the free one, so it saves money and time, and that is good. I give this review a rating of eight out of ten.

I use Tailscale to connect from outside my local network. I set it up on my server and on multiple clients, including my smartphone (iPhone), laptop, MacBook, and TVs, as well as my parents' TVs which are far from my home. Basically, all the devices that I use to connect to my server.

For the most part, I use it to connect to my media server, which contains a collection of media. I also use it as a DNS server. Since my server has DNS, it spreads to all the devices which I am connected to.

I also use it to connect via SSH to start other clients via Wake-on-LAN. I have been using it every day since June 2025, and it has never given me a problem. I also contacted support for some questions, and the support was great. I am actually really impressed by the product and its support.

The features that I love the most are the simplicity of setting it up. I can do it in about two minutes. I just download the app on the client, use a QR code or a key, and set it up. Another feature is Tailnet, which allows me to manage the devices and organize them.

Because I have been using it since June 2025 and never used it before, coming from a very basic level of knowledge, it was really simple to learn and set up. For me, using Tailscale on all my devices is a definite choice.

I do not think there is anything that I wish would have been better because, honestly, for my use case, it has everything I need. I read that people complain about the maximum number of users that can use it under one account, but that is not my use case. For my use case, it has nothing more that I need. It has everything, and it is perfect for my use case.

I have been using Tailscale since I built my home server, which was in June 2025.

Tailscale is really stable.

Until now, with 20 devices, I still have not encountered any limitation. There is no limitation for now.

I only used customer support one time to ask a question that I do not remember, honestly, but the customer support is really great since they responded really quickly and provided very explanatory answers.

At my home, I never used any other service, but in my previous job, I used OpenVPN. However, it was already set up. I did not know how to set it up. It was a bit more problematic because it had connection problems, but I do not have much experience to analyze and talk about it.

Setting up a Tailscale environment took me maybe 10 minutes on the server and two minutes for every device. With about 20 devices, I set up all my environments in about an hour. If I had to use another VPN service, for example WireGuard, I can assume that it would have taken me far more than an hour, something like two hours at least. That is double the time, and Tailscale takes half the time to set up.

We were really engaged with this product. We talked about everything in my opinion, so I do not think there is anything that I would like to add to Tailscale.

As I said, I only use the basic license, so I cannot give any metrics on ROI. But if I had to think about a company or an organization that uses it, I would think that it surely gives a good ROI since it is really a good application and a good service.

Until now, all costs have been free. I never used a license. I never purchased or bought anything more than the basic free license.

I evaluated WireGuard, which I know is the base of Tailscale, but I chose Tailscale since it is more simple, as I said during this interview. That is the main and only reason I chose Tailscale over WireGuard bare metal.

For my use case, these are the main features that I use and have discovered so far. I do not think I have anything more to add in this area.

I would say to use it because, in my case, it really helped my organization with my setup. I would really suggest people use Tailscale if they ask me. I rate this product a 9.

Our main use case for Tailscale is to provide a VPN service where we can remotely log in or SSH into other devices on our network on Tailscale. We're using Headscale. We use it to perform updates, send information, ping certain cameras, and connect devices.

The company did use ZeroTier before, but we chose Tailscale for this use case because it has definitely been the better option of the two, providing faster service and easier installation.

I believe I have covered everything about our main use case. Tailscale is a very solid framework and is very useful for smaller companies if they want to start out or even bigger companies who want to have a robust network of devices that they want to manage.

The best features Tailscale offers are the web interface that allows you to see all of the networks, all the IPs that are active and whether they're offline or online. It is very useful when you have a lot of customers and different devices in different areas. The network connectivity feature is the best.

The web interface and network connectivity features help me in my day-to-day work because we can SSH into the device without knowing the public IP or having any other remote RDP services on that device. If we have the Tailscale IP, we're able to get into that device just as if it were on our LAN or as if it was wired. We use this capability day-to-day for devices all across the U.S.

Tailscale has positively impacted our organization by creating a streamlined appearance, and it is definitely apparent that it is one of the backbones of the company. Currently, if Tailscale goes down, our services are not operable. This has happened in the past but has been fixed multiple times. The newest version has fewer bugs than before.

I don't have specific metrics, but I definitely feel it is a lot faster going through the tickets using Tailscale and being able to troubleshoot on the network of the devices.

Tailscale could be improved by having a better way to troubleshoot. Sometimes our devices do go offline, but if we are able to have some sort of command where we can instantly turn off and turn back on the services at the IP, that would be great.

I believe that covers the needed improvements; it is already a pretty smooth experience.

I have been using Tailscale since I started my career, which was three years ago.

Tailscale is stable in my experience.

Tailscale is definitely very scalable. We haven't had any problems with our scalability, as we have over 300 to 400 devices that use Tailscale that we connect with and utilize on a daily basis.

I have not personally reached out to customer support, but I believe my manager may have when it went down one time.

We did use ZeroTier before; that was before I was employed, but some of our devices still have it installed. They marked up the price significantly, so we did not continue with them.

We deploy Tailscale on a private cloud using Headscale, and we use DigitalOcean to host the Headscale server so that we can use Tailscale on all the devices and connect them. We install Tailscale on the device and log in.

I haven't seen a return on investment with Tailscale based on metrics because we are not big enough to have the metrics or have time for the metrics, but on a personal note, it seems faster and is very streamlined.

I would tell others looking into using Tailscale to get it and use it. If they need an enterprise-level network, it is definitely one of the best solutions.

I was not involved in decision-making before choosing Tailscale; I am just utilizing the software, so I did not come up with the solution of Tailscale.

I rated this review a 9 out of 10.

My main use case for Tailscale is remote access to devices across networks.

In my church context, I can give you a quick specific example of how I use Tailscale for remote access: we have a Reolink doorbell that I access over the local network via the Reolink client apps or MPV, and it also has a cloud solution that is slow and unreliable. I use Tailscale to remotely connect to the doorbell and its NVR, and it is quick, nice, smooth, and great. Another example is in my homelab, where I have many devices in a rack, and I use Tailscale to connect to any of them for fast, reliable access since they can all be in one Tailnet. In the church context, I can use subnet routing to fully expose the entire subnet that the doorbell is on and access various other server computers remotely.

In the church context, I have a number of server computers running virtual machines on a Proxmox device, and I generally SSH into the Proxmox host or the virtual machines through Tailscale when I am outside of the church network. Tailscale gives me a list of all devices on the Tailnet, making it easy to copy the IP addresses and access everything flawlessly.

I would say the best features Tailscale offers are ease of use and ease of remote access. Compared to Tailscale's competitors that I have tried, such as ZeroTier, Tailscale allows you to access a device from another place in significantly less time. Tailscale is very fast, and WireGuard as a protocol is a great choice for a VPN solution because it is so quick, making things such as game streaming over Tailscale easy and fast.

Tailscale's security is fabulous, especially the access control features and the ability to use existing OAuth accounts for access. The user interface is very sleek and not cluttered, which I appreciate when I am on a device with a graphical interface or a command line interface. There are a couple of quirks with the command line interface that I believe are intentional design choices for the best.

Tailscale has positively impacted my organization by making the previously unusable doorbell with the cloud solution fast and reliable for remote access. Previously, conversations through it would be stuttery and hard to understand, with periods of no video feed. Tailscale fully fixed that issue. Accessing servers is easier, allowing me to SSH into the hypervisor or virtual machine seamlessly whenever I need to improve a feature or fix downtime issues. Tailscale managing the security for these critical functions is a beneficial aspect.

I do believe there are a couple of features and changes I would like to see with Tailscale. I initially got introduced to Tailscale in high school when I needed access to services running on my server, but due to deep packet inspection being in place, I could not use Tailscale. Tailscale's free plan effectively introduces people to the service, but I would love to see an anti-censorship VPN protocol implemented. When accessing my homelab, I usually have to resort to using VLESS host through 3X-UI, which is complicated. I would like Tailscale to provide more censorship-resistant options, such as Shadowsocks or VLESS, as fallback protocols.

I would like more anti-censorship protocols, such as VLESS or Shadowsocks, so I can effectively use Tailscale in environments with censored internet access that block WireGuard through deep packet inspection.

More anti-censorship VPN protocols are the main improvement I wish for. If Tailscale implemented these, I would use it for all my VPN needs and would likely use Tailscale entirely.

I have been using Tailscale for five years.

The user interface, documentation, and support for Tailscale are fabulous, and I have no complaints about the user interface. I might prefer a TUI instead of a CLI because I am often not using graphical applications, but the CLI is satisfactory. Overall, the interfaces are great, and the documentation is straightforward for setting up Tailscale on server devices. I only need to reference documentation for specific features such as enabling subnet routing.

My advice to others looking into using Tailscale is to do it; it makes remote access much easier.