Alternatives
Products that do what Lemonade Password Manager does
Simple, secure, with an Env Vault for your .env files
- 1ES
2017 · envkey.com
- 2
- 3
- 4
- 5
- 6
- 7LH
I got tired of: - .env files committed to Git (seen it happen 100+ times) - API keys shared in Slack - Wondering who has access to what secrets So I built Liberty - a CLI tool that replaces .env files with hardware-bound encryption. How it works: $ pip install liberty-secrets $ liberty add DATABASE_URL postgresql://... $ liberty add STRIPE_KEY sk-... $ liberty exec npm start Secrets are encrypted with a key derived from your machine's hardware (CPU ID + machine ID + disk serial). If someone steals your .liberty vault file, it's useless on their machine. Features: - Hardware-bound…
Jan 2026
- 8
- 9
- 10
- 11
- 12
- 13
- 14SR
Hi Guys, I built SecretEnv to help solve one common thing that I have seen at every org, that I have worked at. We always had more than one password/credential manager. Service tokens maybe in Vault, AWS SSM etc and some team specific service account or temp account credentials being store in another password store such as 1Password or Keeper, there was never one single credential store. This is where SecretEnv comes in play, it runs any command with secrets injected as env vars, sourced from whatever combination of backend your team already uses. I am sure there are other tools as well…
May 2026 · github.com
- 15
Password manager encrypting and storing in your Google Drive
2020
- 16
- 17IC
2021 · passpilot.com
- 18
- 19
- 20IJ
.env files have always felt archaic, insecure, clunky and honestly just not fun to work with. I see my friends (and myself) accidentally committing them all the time. Managing secrets across projects becomes a mess of copy-pasting keys into scattered env files with no real way to sync anything. So I built better-env: a secure, developer-friendly alternative to .env. Store your secrets once in a global encrypted store, and load them per-project at runtime. I’d love feedback on whether this feels useful beyond solo devs, and what you’d want for teams or CI setups. Fully open source:…
Nov 2025 · better-env.dev
- 21KC
Hi HN, I built KeyEnv because I was tired of the "can you Slack me the Stripe key?" workflow. The problem: My team's secrets lived in a mix of Slack DMs, shared Google Docs, and .env files that definitely weren't in .gitignore at some point. Enterprise tools like Vault required more DevOps time than we had. Doppler was close but felt heavier than we needed. What KeyEnv does: keyenv init # link project keyenv pull # sync secrets to local .env keyenv run -- npm start # inject secrets, run command That's basically it. Secrets are encrypted client-side (AES-256-GCM) before leaving your machine.…
Jan 2026 · keyenv.dev
- 22HV
2020 · github.com
- 23
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →