What is our primary use case?
The main use case is to manage our secrets, to secure machine credentials, API keys, certificates or tokens, and SSH credentials and encryption keys. All of these are secured in hybrid and multi-cloud environments through this tool.
Generally, I fit Akeyless Secrets Management into CI/CD pipelines. I have a lot of CI/CD pipelines and many cloud environments in AWS, Azure, and GCP. I manage all API keys and encryption keys through Akeyless Secrets Management. Akeyless Secrets Management offers multiple features including automated key rotation. There is a feature called Distributed Fragment Cryptography, which is a patented Zero-Knowledge encryption architecture provided by Akeyless Secrets Management. This is the main use case of Akeyless Secrets Management.
What is most valuable?
One thing I want to say about Akeyless Secrets Management is that many other secret management providers are available, but Akeyless Secrets Management helps us because it has a feature called automated secret rotation. This automated secret rotation automatically triggers a workflow to our hybrid cloud or cloud provider to rotate the secrets on a long-term basis, such as every three months or six months. This ensures the security of our organization better. This is a security best practice generally used in many organizations, but they implement it through their own scripts and CI/CD scripts. Now, with Akeyless Secrets Management, I do not have to do that. Akeyless Secrets Management provides this by default. It has helped us a lot because it reduces overhead for our organization.
The features mainly include that Akeyless Secrets Management supports multi-cloud and hybrid environments. It has a Universal Secrets Connector and can connect with other secret managers. It offers good compliance, automated secret rotation, temporary credentials, and dynamic secrets options. The main standout feature is the Zero-Knowledge architecture.
Automated secret rotation stands out most for me. This significantly lowers my manual effort. Without manual intervention, it is automated. Without manual overhead, it solves many issues.
What needs improvement?
I sometimes feel that there are documentation gaps in Akeyless Secrets Management. The documentation could be more detailed for advanced integrations and troubleshooting.
Some organizations feel that there is a trust concern because the secrets are stored in Akeyless Secrets Management and it is not open-sourced. It is completely closed-source. If something goes wrong or someone hacks Akeyless Secrets Management, there is a huge drawback. These are concerns my organization and many other organizations are facing.
The UI/UX could be better on the homepage and many other pages. Pricing transparency should also be improved. The pricing should include discounted pricing for regular customers or regular enterprise customers.
For how long have I used the solution?
I have been using Akeyless Secrets Management for around one year.
What do I think about the scalability of the solution?
Akeyless Secrets Management's scalability is very good. As of now, I have not experienced any issues.
How are customer service and support?
The customer support is good, but it is somewhat slower compared to other support systems. It could be faster.
Which solution did I use previously and why did I switch?
Before Akeyless Secrets Management, I used many other secret managers including in-built secret managers in AWS, AWS Vault, and HashiCorp Vault. Before that, I had to do it manually. With Akeyless Secrets Management, I was able to rotate it very quickly. The efficiency I can report is that around 40% to 50% of the efforts are not wasted in secret management.
Previously, I was using HashiCorp Vault and AWS Secret Manager. There were many issues with HashiCorp Vault and AWS Secret Manager, such as the lack of automated secret rotation and many compliance threats attached to those platforms. This is why I switched to Akeyless Secrets Management.
What was our ROI?
The metric is based on two or three factors including the time saved and the number of manual tasks reduced, as well as the before and after time. Based on those metrics, my organization's efficiency improvement is 40%.
Which other solutions did I evaluate?
HashiCorp Vault and AWS Secret Manager were the options I evaluated, but I did not get the results I was looking for. They do not have automated secret rotation, and they do not have a Zero-Knowledge architecture or this cryptographic design. Akeyless Secrets Management stands out because it combines SaaS simplicity with a Zero-Knowledge cryptographic design, reducing operational overhead without fully sacrificing control.
What other advice do I have?
The advice I will give to anyone looking into using Akeyless Secrets Management is to first evaluate what tool you need according to your organization's needs. Understand your organization's need and determine why you need this tool and whether it is necessary. Ask these questions and then choose any tool, not only this tool, but these questions need to be asked beforehand. Once you ask yourself those questions, then you will be confident that you need to use this tool. Always evaluate alternative options as well.
Use Akeyless Secrets Management as a temporary tool, not a permanent tool. Store a backup of your secrets somewhere. You should not completely rely on Akeyless Secrets Management because if Akeyless Secrets Management fails, everything fails due to a single point of failure. If you have a good backup, you will always be better positioned. These are the suggestions I would give. I gave this product a rating of 8.5 out of 10.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other