strongDM review

strongDM is an identity-security product for controlling access to infrastructure, databases, containers and CI/CD pipelines across cloud and on-premise environments. It is now part of Delinea. The core idea is to replace standing permissions with time-bound, policy-based access, then enforce least privilege when an action happens.

The product is positioned for human users, AI agents and machine identities. Its feature set includes just-in-time access, runtime authorization, session recording and audit evidence. Infrastructure access covers cloud infrastructure, production databases, containers and CI/CD pipelines; unified audit reporting is intended to show who accessed what, when and how.

That makes strongDM more than an SSH gate. It is aimed at teams that want one access-control layer across several kinds of production systems. If you only need basic SSH access for a small fleet, the broader identity and audit features may be more product than you need.

strongDM’s main strength is breadth: the product is designed to apply access controls across infrastructure, databases, containers and CI/CD pipelines, rather than only SSH. Just-in-time access and runtime authorization are intended to reduce standing privilege, while session recording and unified auditability give teams evidence of who accessed what, when and how. Those features matter most when teams have several identity types and production systems to govern.

Some Reddit users report a positive operational experience. In one r/devops discussion, a commenter said StrongDM was easy to set up and operate, and valued support for SSH, SQL, Kubernetes and HTTP targets. Another commenter described access to databases, Kubernetes clusters and servers as easy to set up. These are individual reports, not a guarantee that every environment will be straightforward.

For a migration, the practical case is consolidation: if you currently manage access through separate tools and policies, strongDM’s stated coverage may reduce the number of access paths to oversee. Whether that trade-off pays off depends on the quote and the systems you need to cover.

The main drawback is price opacity. According to the pricing information, monthly and annual prices are not published; you need a custom quote. The available data lists no free plan, and a free trial is not published. That makes it hard to compare strongDM with alternatives before talking to sales.

The listed plan caps also matter:

• Essentials: up to 4 Engines, 15 Admins, 15 Business Users and 2TB storage.
• Standard: no Engine or Site limit, 15 Admins, 15 Business Users, 15 Servers and 4TB storage.
• Enterprise: no Engine or Site limit, 30 Admins, 30 Business Users, 30 Servers, 30 Workstations and 6TB storage.

Treat those limits as a checklist for your quote, not a full price comparison. In one Reddit thread, a customer said renewal pricing more than doubled; StrongDM’s CEO disputed that as typical and said renewals usually stay at the agreed rate unless licensing or package changes. Another user called the web UI basic and described a configuration snag with a non-standard Kibana data source. Those reports are anecdotal, but worth checking against your setup.

strongDM does not publish plan prices. The published pricing information lists custom quotes, with monthly and annual rates not published; you’ll need to contact sales to get a number. No free plan is listed, and trial availability is not stated. No add-ons are listed in the published pricing data.

• Essentials: For smaller teams with limited infrastructure. Includes up to 4 Engines, 15 Admins, 15 Business Users and 2TB of storage.
• Standard: Removes the Engine and Site limits, but still lists 15 Admins, 15 Business Users, 15 Servers and 4TB of storage.
• Enterprise: Keeps no Engine or Site limit and raises the listed caps to 30 Admins, 30 Business Users, 30 Servers, 30 Workstations and 6TB of storage.

The move from Essentials to Standard removes the Engine cap, but the published limits still constrain users, servers and storage. Enterprise raises those caps, though the price jump between tiers is not published. Get a quote that spells out billing terms and any costs beyond the listed allowances before comparing plans.

Switching effort depends on what you plan to bring under strongDM: the product covers infrastructure, databases, containers and CI/CD pipelines, plus human, AI and machine identities. Before committing, inventory the resources, identities and access policies involved, then ask strongDM what migration support is included and how existing session records and audit evidence can be transferred. The published materials do not describe migration steps, export formats or retention after cancellation, so get those details in writing.

We don’t have Reddit posts or comments in the published sources, so we can’t responsibly say what tends to make users leave. Ask about offboarding, policy and identity export, and access during a transition to another tool. StrongDM is now part of Delinea, but the published information does not explain how that affects data portability or product changes. Treat those as questions for sales, not settled facts. If you’re replacing it, map which access controls and audit records need an equivalent before setting a cutover date.