What is our primary use case?
We use Thycotic Secret Server for the lab environment. We have it as a vault for users and in a client project. We have set it as the users' mass login to the secret server so they have access to their SVN. It is for remote access, password changing, etc...
We use it on premise, mostly. I haven't used the cloud version, but we are discussing with the client about using the cloud deployment.
What is most valuable?
Its most valuables feature are its main purpose - the password changing and the Heartbeat so the user has access to only their SVN and does not have access to any other. Thycotic's access privileged management tool allows you to grant access to users for a specific period of time and with specific attributes and privileges.
What needs improvement?
In terms of what could be improved, the whole thing with distributed engines, et cetera, is a little bit tricky. Additionally, many clients wanted a more cloud version. I know there is a cloud version of Thycotic Secret Server, but a whole unified platform would be good, not like where you have to set up a connector with the distributed engine and then have the Thycotic Secret Server connect with all these. Making a simpler version of connecting different sites and synchronization of the groups that you already have. Then the secrets and folder templates would follow the current infrastructure pattern that the client has so you don't have to recreate new folders and secrets from scratch. In other words, more interoperability with other systems, for example if a user already has a Microsoft Azure subscription. So, the integration with Microsoft as well would be good.
For how long have I used the solution?
We have been using Thycotic Secret Server for about a year and a half.
Buyer's Guide
Delinea Secret Server
March 2025
Learn what your peers think about Delinea Secret Server. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
842,767 professionals have used our research since 2012.
What do I think about the stability of the solution?
In terms of stability, I would say, yes and no. We had some issues regarding the size of the disk space, which was a Thycotic side issue. There were many log files that they couldn't delete. And then we have another issue with the service account. We have to use another service account for Thycotic, and there was a mix-up with the database. All these issues were from the Thycotic side.
We're logging the tickets and I think there will be a resolution in the future.
What do I think about the scalability of the solution?
Scalability is okay.
We use it for lab environment uses. We have about 20 users, not too many.
It takes one person to deploy in our environment.
We do have plans to increase. We have a live contract and other client requests for Thycotic, including maybe the cloud deployment. I hope it is not as tricky as on premise. Maybe it's easier, I don't know.
How was the initial setup?
The initial setup depends on the client. That's why Isaid earlier that there should be a simpler version where we connect all the different sites, et cetera. Because for client installation and deployment, you have to set up two different servers for high availability, for example, and connect another through your site connectors for the distributed engines, and the client didn't have any load balancers. So, there were many issues and the Thycotic was a little bit tricky at that moment. It wasn't just a simple solution where you set up a server and you have it up and running.
The other thing is, and I think it's important, there is not much documentation on the internet. Besides the partner portal it would be nice if there was a blog or something that we could use. So for most cases, we have to open a ticket, either us as partners or on the client's side.
What's my experience with pricing, setup cost, and licensing?
What other advice do I have?
Thycotic Secret Server is a good solution for what it does. We are happy for that, but maybe they can improve some features. Let's say the keystrokes function doesn't work. We have reported that to Thycotic, but they still have many improvements to do.
On a scale of one to ten, I think Thycotic Secret Server is an eight - maybe.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.