We use Twingate for remote access.
What is our primary use case?
How has it helped my organization?
We were able to add Twingate into our infrastructure without having to change our infrastructure or how people work.
We reaped the benefits of Twingate immediately because it replaced an alternative solution with a lot of overhead.
Twingate helped reduce access-related support tickets by 80 percent.
Twingate streamlines onboarding for our company, especially for the engineering team, by automating resource access through directory integrations. New employees generally require no manual configuration within Twingate, saving us significant time and effort.
The resiliency is directly proportional to the level of control we exert over its components. We can manage Twingate connectors to support high availability, ensuring the system is as reliable as needed. This flexibility and control enhance Twingate's resiliency capabilities significantly.
What is most valuable?
I appreciate Twingate's developer-first approach, particularly its excellent developer tools for deployment and management. Their strong support for Terraform, Kubernetes, and other innovations simplifies the process for developers. At the same time, Twingate remains easy to use for end users.
What needs improvement?
Twingate's lack of native support for Windows Server is a significant limitation. While it hasn't directly affected my company, I've encountered this issue when assisting others. Additionally, the inability to group resources, which often comprise a single service, necessitates an independent setup for each. This creates substantial overhead when configuring Twingate with SaaS applications.
For how long have I used the solution?
I have been using Twingate for two years.
What do I think about the stability of the solution?
Twingate's stability has improved considerably, although it remains imperfect, potentially due to our deployment methods. On a scale of one to ten, with ten being the most stable, the client side would receive a five, while the connector side scores a nine.
What do I think about the scalability of the solution?
I would rate the scalability of Twingate nine out of ten.
How are customer service and support?
The technical support is excellent in terms of quality and response time. They follow up on older tickets even months later if a related feature change occurs. It's one of the best support experiences I've had with a SaaS product.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We replaced our SSH Tunneling solution with Twingate to improve performance. While Windows clients still face a performance ceiling of a few hundred megabits per second, Twingate delivers significantly better latency and throughput compared to other options.
How was the initial setup?
The initial deployment was straightforward and completed by one person in four hours.
What about the implementation team?
The implementation was completed in-house.
What's my experience with pricing, setup cost, and licensing?
Twingate's pricing is fair.
Which other solutions did I evaluate?
In evaluating various VPN solutions, including Cloudflare WARP, Tailscale, traditional options like WireGuard and OpenVPN, and an alternative called Perimeter 81, Twingate emerged as the clear winner. It surpassed the competition in performance and affordability while being significantly more straightforward to deploy.
What other advice do I have?
I would rate Twingate eight out of ten.
We previously used Twingate for internal security during its beta phase, but discontinued its use due to added licensing costs. We now use NextDNS, a more affordable alternative that provides similar functionality and integrates with Twingate. Essentially, Twingate white-labels NextDNS for their internet security features, but we opted to subscribe to NextDNS directly for cost savings.
Twingate requires minimal maintenance to remain current.
Which deployment model are you using for this solution?
Public Cloud

