1Password vs HashiCorp Vault

• Securely stores passwords & sensitive data
• Integration with iPhone's password solution (ability to utilize 1Password info rather than Apple keychain items)
• Integration with Mac Touch ID
• Ability to access multiple accounts within a single interface (and search them all -- or not -- as needed)

Read full review

• Automated revocation of credentials via leases
• Provides many plugins for federated authorization through different platforms
• Dynamic credential generation

Read full review

• If a certain login needs to be placed in two vaults (e.g., for two different teams), any updates must be applied to both instances which creates a bit of a management hurdle. We could create a 'special' vault for those types of items, but that could lead to a lot of extraneous vaults. This is particularly relevant when using the "Guest" feature, as many of the credentials have to be duplicated, and then they won't sync to the Guest vault if they're updated in the Team vault.
• When using the 1Password iPhone app, the search field takes *forever* to populate results, making the search function essentially unusable. Instead, I typically use the alpha-scrolling and then manually navigate to the item I'm looking for.
• If I view a specific vault within the desktop app, the next time I use the browser extension the results are also restricted to that vault. In order to get it to look at all vaults again, I have to open the desktop app and change it back to "all vaults" there — there's no way to select the vault within the browser extension.
• The system walks you through the initial setup steps fairly well, but then setting up the apps can be a bit daunting. I'm planning to get my family members onto a personal plan, but the set up is so complicated that I have to wait until we're together so that I can help them through it. This also creates some difficulty when on-boarding new users for my business, as it takes a lot of effort to be sure they have access to all of the right areas (and then use / save that info in order to log in to the apps).
• Seems like the business plan should have more options to accommodate organizing credentials for many different clients. Right now, we just rely on consistent naming conventions to allow like items to group together (e.g., Client Name — Website Title), but it's not very elegant and can get lengthy. I know that tags are available for use, but I'm not sure that would achieve the desired result. Initially, I had considered using individual vaults for each client, but there are just too many to merit individual vaults.
• When using the browser extension, there's no preview of the username, so if you have two records with the same title (e.g., United Mileage Plus), you have to view it before filling to ensure it's the right one. This means that all records must have a unique name / identifier, which can lead to very lengthy titles. This is particularly relevant when you have access to client accounts, since you can't be renaming their items to match your own naming conventions.

Read full review

• Documentation for the API moves slower than changes in the API itself
• The database secret engine's API design isn't as elegant as it could be
• No support for revocation of all secrets under one path

Read full review

• We have been able to save at least 50% more time when setting up new users or removing users from our setup. Previously we had to log in and change passwords manually which took a lot of time and was not secure. 1Password has made this process easier for us and thus made us more efficient
• In terms of workflow, our teams are now able to share and have access to information quickly as they can accept or request password access from administrators and continue their work.

Read full review

• Helped us reach our security compliance goals.
• Helped us strengthen our security position in our infrastructure by improving on poor secret management practices.

Read full review