Iam Engineer at a manufacturing company with 10,001+ employees
Real User
Top 20
Feb 23, 2026
I would assess StrongDM's ability to unify access across different systems in my organization as pretty good, despite sometimes facing issues using the platform, probably because of maintenance. Sometimes you are not able to retrieve the password, so it has happened. I'm not going to say that it's a perfect product, but I think they're slowly getting better, and as I said, in the future, this product has potential for hybrid solutions in my company, especially after they got acquired by Delinea. Regarding the continuous runtime authorization feature, I haven't utilized that feature in the product myself, but someone else in the organization has. I mostly work with StrongDM as an end user who has privileged accounts onboarded. I believe the importance of continuous authorization versus periodic checks is significant. Automatic credential rotation means we do not have to worry about manual checks repeatedly. It is a good solution for continuous authorization, although the challenge remains about how it will support larger organizations with many enterprise privileged accounts. I would definitely recommend StrongDM, especially for mid-sized to small organizations. If it's a large organization, I would suggest having them view a demo to see if they are ready to adopt it as a product. My overall review rating for StrongDM is seven out of ten.
Senior Data Engineer at a non-profit with 1,001-5,000 employees
Real User
Top 10
Oct 29, 2024
The communication is sufficient for implementing StrongDM from scratch. Sales and sales engineers are knowledgeable, providing helpful resources. I'd rate the solution nine out of ten.
Senior Devops Engineer at a transportation company with 51-200 employees
Real User
Top 10
Aug 16, 2024
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.
StrongDM offers an innovative solution for managing infrastructure access, focusing on security and compliance while ensuring streamlined operations. StrongDM simplifies infrastructure access by unifying management and auditing capabilities. It provides a seamless way for organizations to quickly secure sensitive data across all environments, enhancing access control without compromising efficiency. With a focus on integrating access data and compliance requirements, StrongDM is designed to...
I would assess StrongDM's ability to unify access across different systems in my organization as pretty good, despite sometimes facing issues using the platform, probably because of maintenance. Sometimes you are not able to retrieve the password, so it has happened. I'm not going to say that it's a perfect product, but I think they're slowly getting better, and as I said, in the future, this product has potential for hybrid solutions in my company, especially after they got acquired by Delinea. Regarding the continuous runtime authorization feature, I haven't utilized that feature in the product myself, but someone else in the organization has. I mostly work with StrongDM as an end user who has privileged accounts onboarded. I believe the importance of continuous authorization versus periodic checks is significant. Automatic credential rotation means we do not have to worry about manual checks repeatedly. It is a good solution for continuous authorization, although the challenge remains about how it will support larger organizations with many enterprise privileged accounts. I would definitely recommend StrongDM, especially for mid-sized to small organizations. If it's a large organization, I would suggest having them view a demo to see if they are ready to adopt it as a product. My overall review rating for StrongDM is seven out of ten.
The communication is sufficient for implementing StrongDM from scratch. Sales and sales engineers are knowledgeable, providing helpful resources. I'd rate the solution nine out of ten.
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.