StrongDM Reviews

We use it for zero-trust privileged access.

Any time we have a new resource, we can have it automatically picked up and provisioned based on tags to give the right people access to the right resources.

I don't have to think about giving anyone access to anything. All of the logging is handled for us, including for auditing purposes. Looking through the audit logs is not a painful experience. Everything is in one place if we need to go back and look at what happened.

I like the easiness of integrating it with all of our existing data sources. We've also found a few other use cases where we've been able to grant access to third-party resources that require IP-level whitelisting in addition to authentication for remote workers.

We started to use it as a client-side or split tunnel VPN. We are unable to overwrite the endpoints and direct traffic that way, but that's a technical limitation, and I understand why it's there.

I have been using it for about four years. 

We've had a few issues in the past, but those have all been resolved based on interactions with StrongDM and the addition of some new features to the product. For example, the egress routing functionality solved a fair amount of our problems. So, I don't think there are any outstanding issues that we're aware of or have complained about.

I would rate the stability a nine out of ten. The only reason it's not a ten is that there's some automated patching that happens in the background. This was years ago, but we had some issues where that were causing us problems, and we had no way of scheduling it at different times.

We haven't run into any issues with scalability at this point. 

The only issues we've encountered are when you have a very large amount of data sources, we're talking above 2000. Then, the routing algorithm for directing traffic on the StrongDM backend takes a little bit of time to figure out where to route traffic whenever you bring up and down relays or gateways.

We do not have any issues with StrongDM's scalability at the size of our organization right now.

That's how we got some of those feature requests in. We've only contacted support one or two times without a feature request. The support interactions have been minimal because of how good the documentation is.

The initial setup was fairly straightforward as we run everything in Docker. From that side, there wasn't much effort required from StrongDM. However, integrating it into our environment was completely on us.

The licensing is per user per month.  It's pretty close to the same or in line with all of the other pricing for tools that do similar things.

A first-time definitely needs to have some background experience with setting up services to run, but it's no different than onboarding any other service.

My recommendation: Do not change the gateway or relay names, and everything will be great. But that's only really a problem if you deploy within Kubernetes and use a deployment rather than a stateful set.

Overall, I would rate it a nine out of ten.