The enterprise version would require considering factors like the level of support needed, the amount of secret data being stored, and replication needs. But in my case, the open-source version works well. It's advisable for small to medium-scale organizations, but for large-scale organizations, you should go with the enterprise version.
Project Manager at a comms service provider with 201-500 employees
Real User
2022-03-30T11:55:40Z
Mar 30, 2022
It could do everything we wanted it to do and it is brilliant, but it is super pricey. To be fair to HashiCorp, we drove the price up with our requirements around resiliency. Because of the nature of our company, we don't really operate in the cloud. Our cloud presence is a couple of VMs. We're not even a hybrid. We don't have a public cloud. As we mature and as we're moving in the cloud direction, it would possibly be a lot cheaper because we'd just be paying for what we're using. That price was for a future-proofed quote of where we will need to be in three years. What we were looking for was colossal. We wanted redundancy clusters, multiple nodes, and multiple validations. It was a global reach, and it was a lot. It was going to cost us over a quarter of a million a year. I was quite frankly shocked. It is a lot of money. I know that we drove it up, and we were getting a lot for that. If we had more flexibility to go into the cloud, it would probably be a lot cheaper. My parent company did say that the pricing model changed this year and the price went up. They seem to be bringing themselves in line with general Microsoft pricing. Because HashiCorp has a free version, a lot of people were just using the free version and getting by on it, but if you want to have clusters and the scalability to have more clusters, you will have to upgrade. They do have different licenses, but they are very closed about their pricing. I was three months into the PoC before I could get a price. They don't offer it, and they don't lead with it. It is probably because it is very bespoke. We wanted it to do so many things, and that's why it was so pricey, but even to take it down, they have some confusing terms. They've got fixed costs, but there is a cost per client, and I found the definition of client fuzzy. So, you pay a certain price for every client that interacts with the vault or with HashiCorp, but what they call a client is quite loose. You could get up to a lot of clients very quickly. There are some elements of the pricing that I wouldn't be super keen on.
We are using the open-source version. At the moment, our cost is basically the engineer's work time and the infrastructure costs. But compared to the AWS Parameter Store, the AWS version is much cheaper than HashiCorp Vault.
I wasn't involved in licensing, although it is my understanding that many of HashiCorp products are free of cost. There are premium services you could purchase, however, our organization only used the free versions.
TechOps Engineer - Middleware & Containers specialist at EBRC -European Business Reliance Centre
Real User
2019-05-23T17:02:00Z
May 23, 2019
The community edition is a place to start, where the development framework is already in place. When moving to production it is easy to make the switch and there are no additional development costs. Once used in the framework, developers gain time to address authentication and authorization issues, which are managed once at the vault level and no more.
HashiCorp Vault is a cloud-agnostic solution used for security and secret management. Its valuable features include integration with other HashiCorp tools, token sharing, open source nature, cloud agnosticism, and on-the-fly encryption management.
The solution provides encryption of data at rest, in use, in transit, on the fly, and linked with applications. It is free to use, and the interface is simple to navigate. HashiCorp Vault has helped organizations with its multiple...
The enterprise version would require considering factors like the level of support needed, the amount of secret data being stored, and replication needs. But in my case, the open-source version works well. It's advisable for small to medium-scale organizations, but for large-scale organizations, you should go with the enterprise version.
The product is expensive. However, we use the open-source version.
Security is good, and pricing is also competitive. I would rate the solution's pricing a six out of ten, where one is low and ten is high.
The solution's cost is reasonable. Its automation features contribute to sustainability and cost-effectiveness.
It could do everything we wanted it to do and it is brilliant, but it is super pricey. To be fair to HashiCorp, we drove the price up with our requirements around resiliency. Because of the nature of our company, we don't really operate in the cloud. Our cloud presence is a couple of VMs. We're not even a hybrid. We don't have a public cloud. As we mature and as we're moving in the cloud direction, it would possibly be a lot cheaper because we'd just be paying for what we're using. That price was for a future-proofed quote of where we will need to be in three years. What we were looking for was colossal. We wanted redundancy clusters, multiple nodes, and multiple validations. It was a global reach, and it was a lot. It was going to cost us over a quarter of a million a year. I was quite frankly shocked. It is a lot of money. I know that we drove it up, and we were getting a lot for that. If we had more flexibility to go into the cloud, it would probably be a lot cheaper. My parent company did say that the pricing model changed this year and the price went up. They seem to be bringing themselves in line with general Microsoft pricing. Because HashiCorp has a free version, a lot of people were just using the free version and getting by on it, but if you want to have clusters and the scalability to have more clusters, you will have to upgrade. They do have different licenses, but they are very closed about their pricing. I was three months into the PoC before I could get a price. They don't offer it, and they don't lead with it. It is probably because it is very bespoke. We wanted it to do so many things, and that's why it was so pricey, but even to take it down, they have some confusing terms. They've got fixed costs, but there is a cost per client, and I found the definition of client fuzzy. So, you pay a certain price for every client that interacts with the vault or with HashiCorp, but what they call a client is quite loose. You could get up to a lot of clients very quickly. There are some elements of the pricing that I wouldn't be super keen on.
We are using the open-source version. At the moment, our cost is basically the engineer's work time and the infrastructure costs. But compared to the AWS Parameter Store, the AWS version is much cheaper than HashiCorp Vault.
I wasn't involved in licensing, although it is my understanding that many of HashiCorp products are free of cost. There are premium services you could purchase, however, our organization only used the free versions.
I am using the open-source version of Vault and I would have to buy a license if I want to get support.
The community edition is a place to start, where the development framework is already in place. When moving to production it is easy to make the switch and there are no additional development costs. Once used in the framework, developers gain time to address authentication and authorization issues, which are managed once at the vault level and no more.