4 ms·

Vault interests me but seems to come with a lot of complexity/requires an army of devops. There's a YC backed company called Envkey[0] that looks interesting +

Vault interests me but seems to come with a lot of complexity/requires an army of devops. There's a YC backed company called Envkey[0] that looks interesting + simple, but there is no option to self host yet [0] https://www.envkey.com/ https://www.envkey.com/

p10jkle 7y ago
Fair enough, Vault has a ton of features I guess most don't need. It's been cool for us, we are now using it for secrets, database credentials, and certificate management (more blog posts coming!). Next up is hopefully AWS creds management
zie 7y ago
I run vault at my org, we are a devops team of 2, and we do just fine. Vault can be tricky, because a failure in vault def hurts and can impact production pretty quickly. So take your time, and slowly move things to it, but vault is almost certainly worth your time and energy. Plus combined with nomad and consul and the rest of the hashi stack it's pretty easy, and hard to get wrong.
gingerlime 7y ago
I’ll plug envwarden[0] which is a simple wrapper to manage your keys as environment variables in Bitwarden (which can be self-hosted I believe). [0] https://github.com/envwarden/envwarden https://github.com/envwarden/envwarden
- peterloron 7y ago
  Yes, Bitwarden can be self-hosted. It is also a really nice secret management tool for humans, although it does have a CLI and API which can be used for machines.
danenania 7y ago
EnvKey founder here. Thanks for the mention! We're hard at work on a v2 that will be self-hostable as well as more powerful, flexible, and robust across the board so that it will be able to handle just about any configuration or secrets management scenario you can throw at it, from small teams to enterprise, while maintaining a simple, it-just-works approach. In the meantime, our app and client libraries implement true end-to-end encryption that is open source and well-documented[1], meaning that despite our current product being cloud-hosted, we could not access your secrets even if we wanted to. 1 - https://security.envkey.com/ https://security.envkey.com/

p10jkle 7y ago

Fair enough, Vault has a ton of features I guess most don't need. It's been cool for us, we are now using it for secrets, database credentials, and certificate management (more blog posts coming!). Next up is hopefully AWS creds management

zie 7y ago

I run vault at my org, we are a devops team of 2, and we do just fine. Vault can be tricky, because a failure in vault def hurts and can impact production pretty quickly. So take your time, and slowly move things to it, but vault is almost certainly worth your time and energy. Plus combined with nomad and consul and the rest of the hashi stack it's pretty easy, and hard to get wrong.

gingerlime 7y ago

I’ll plug envwarden[0] which is a simple wrapper to manage your keys as environment variables in Bitwarden (which can be self-hosted I believe). [0] https://github.com/envwarden/envwarden https://github.com/envwarden/envwarden

peterloron 7y ago
Yes, Bitwarden can be self-hosted. It is also a really nice secret management tool for humans, although it does have a CLI and API which can be used for machines.

danenania 7y ago

EnvKey founder here. Thanks for the mention! We're hard at work on a v2 that will be self-hostable as well as more powerful, flexible, and robust across the board so that it will be able to handle just about any configuration or secrets management scenario you can throw at it, from small teams to enterprise, while maintaining a simple, it-just-works approach. In the meantime, our app and client libraries implement true end-to-end encryption that is open source and well-documented[1], meaning that despite our current product being cloud-hosted, we could not access your secrets even if we wanted to. 1 - https://security.envkey.com/ https://security.envkey.com/