Twingate Private Access

What do you like best about the product?

From Devops perspective - it was easy to deploy, easy for the end users to use as well

What do you dislike about the product?

update azure and aws connectors is less intuitive

What problems is the product solving and how is that benefiting you?

As single devops in my company - saves me the overhead of creating VPN solution from scratch

What do you like best about the product?

At Autbank, we use Twingate to manage our clients' multiple AWS accounts; this has greatly simplified our management, as we simply deploy a connector within the client's network to centralize all access.
With permission management integrated via our Entra ID SSO, it is also extremely easy to grant specific permissions to specific individuals for a set period of time.

What do you dislike about the product?

At the moment, our use of Twingate isn't causing us any difficulties or problems; it is a very good tool for business.

What problems is the product solving and how is that benefiting you?

The centralization of multiple networks with different connectors certainly helps us a great deal in our day-to-day operations.

What do you like best about the product?

It is easy to get started for IT and for most users its set and forget. The UI could use some improvment, its not very intuitive for our non-technical staff. IT really likes it, it integrates with our other stack (Azure AD, SentinelOne) cleanly and we think its fairly well priced. A connector on a satellite office is legitly being ran by a Raspberry Pi and we notice no performance issues.Solid piece of tech, but not without it flaws.

What do you dislike about the product?

It's very clearly a developer first tool, and I lack some features that would make it more enterprise ready. I cant believe that there _still_ is no way to gracefully drain a connector before an upgrade, for example. To the plus side, its quite customizable and we've managed to solve that issue with the prometheus metrics that the connector provide, so we can always manage to find a window with no activity, but stuff like that shouldn't be needed.

We've also had some hard to diagnose issues where users just get signed out and cant sign back in again without restarting the Twingate service, which our end users cannot do.

What problems is the product solving and how is that benefiting you?

Granual access. It's huge because now we KNOW that our call center staff only have access to precisely what they need.

What do you like best about the product?

It's a lightweight product with low setup complexity, high reliability, great performance, and very low overhead. It saved us money, boosted our security posture, and increased our network performance when compared to our traditional IPSEC VPN.
The product itself has easy integrations with IaC providers (e.g. terraform), is very easy to use, and even provides free usage at home. This last part is highly underrated, as it lets the tech savvy among us experiment at home without bearing the risk of change in a production environment. Way to go folks!

What do you dislike about the product?

Automated deployments on new builds does require a few extra clicks from the user to get going.
Additionally (this is more of a Mac problem), we have a few issues with Mac OS & security posture being detected by Twingate. We've noticed specifically that when a Mac is operating in clamshell mode, it reports biometric as offline. We have a mandate for it to be enabled, but we can't rely on this specific posture check from Twingate.

What problems is the product solving and how is that benefiting you?

Remote access to specific resources that comes with high visibility. We've had a traditional VPN in the past, but connectivity for geographically distant users and/or users with unreliable connections was often experiencing high retransmission rates, and lengthy round trip times when talking to the concentrator. Setting up Twingate connectors at a network edge noticeably improved the experience for users who were seeing frequent retransmissions (specifically those using QUIC).

What do you like best about the product?

Easy to set up and deploy. Access control the at the network layer. Integrates with Google Workspace. Has a Terraform provider and GitHub Actions step.

What do you dislike about the product?

I don't have anything negative to say about it.

What problems is the product solving and how is that benefiting you?

It provides a nomadic workforce with access to private network resources in AWS.

What do you like best about the product?

Twingate provides a seamless and secure Zero Trust Network Access (ZTNA) solution that eliminates the need for traditional VPNs. The deployment is straightforward, and the cloud-native architecture makes it easy to scale without complex infrastructure changes. I particularly appreciate the granular access controls, which allow us to enforce least-privilege access effectively.

From a security standpoint, it enhances visibility and control over user access, helping strengthen our overall security posture. The integration with identity providers is smooth, and the user experience is excellent,end users can securely access resources without performance issues typically associated with VPNs.

Additionally, Twingate simplifies access management for both internal and external users, making it a reliable solution for modern distributed environments.

What do you dislike about the product?

One area for improvement is the logging and traffic monitoring UI. Currently, there is a lack of advanced search and filtering capabilities, which makes it difficult to quickly drill down into specific user activities or investigate incidents.

The interface could benefit from more intuitive navigation, along with robust filters (such as by user, resource, time range, and action) to simplify log analysis. Additionally, enhanced visibility into traffic patterns and more detailed audit logs would greatly improve the overall monitoring and troubleshooting experience.

What problems is the product solving and how is that benefiting you?

VPN with secure Zero Trust Network Access (ZTNA)

What do you like best about the product?

Its has a very fast connectivity, very reliable, connects well with any internet service provider, it was easy to implement, has a good customer support, it was easy to integrate with our MFAs. Highly secure. Interface its easy to use.

What do you dislike about the product?

There is not much to dislike about Twingate, however, once updated it might take a while to get use to the new upgrade, in the past we had to uninstall and install again for the VPN to start working properly.

What problems is the product solving and how is that benefiting you?

Online security, protect our tools, and all of our softwares.

What do you like best about the product?

Our team really appreciates the ability to create groups and manage team resources through them. We also find it very easy to implement.

What do you dislike about the product?

Managing temporary access for external users can sometimes be challenging.

What problems is the product solving and how is that benefiting you?

For our team, it assists in monitoring usage on our internal website and supports our efforts to achieve SOC2 and HIPAA compliance.

What do you like best about the product?

Migrating from a bastion server with SSH keys, trying to keep all of those in place and uptodate was cumbersome. Using Terraform to manage Twingate users, groups, service accounts, tokens, connectors, and resources fits into the "Infrastructure as Code" paradigm nearly perfectly.

What do you dislike about the product?

There is a "click-ops" of policy management. It would be nice to have them also managed via Terraform. It would also be nice to have MFA at the resource level. Depending upon workflow, the simple friction point of needing to authenticate can be enough to block a bad thing. Currently, even if the resources were in separate groups, each with the MFA enabled, if as soon as you have authenticated, all resources in all groups that require authentication are now accessible. I believe there is a plan to go with per-group authentication.

What problems is the product solving and how is that benefiting you?

Moving from a single Bastion server running SSH, using IaC, was cumbersome. Twingate significantly simplifies that, but also allows us to now use external pipelines to access the resources in a sensible manner using service accounts, as well as exposing private endpoints to the appropriate members in a secure fashion.

What do you like best about the product?

The best part in Twingate is the simple admin experience. After adding the Gateway to infrastructure, it's easy to add resources and manage policies. This is very useful when you have to manage a large number of resources, which is our case. Also, onboarding internal users is so easy with the Twingate client; we collected a lot of great feedback about the client app for all OS.

What do you dislike about the product?

No dislikes about Twingate. Maybe the pricing would be a problem if the number of seats is so high.

What problems is the product solving and how is that benefiting you?

We have multiple private cloud environments, with microservices and internal tools. Using Twingate, we can control the accesses and ensure that only allowed people can access resources.