Alternatives
Products that do what Liberty – Hardware-bound secret manager (no more .env files) does
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…
- 1
- 2
- 3
- 4KC
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
- 5
- 6ES
2017 · envkey.com
- 7
- 8
- 9
- 10
- 11SM
This is a tool to manage encrypted local backups of secrets. The core idea is that it aims to be usable without depending on it, meaning that even if the software disappeared from the face of Earth tomorrow, your data would still be recoverable. It also integrates nicely with NixOS (which is what I use, though it does not require NixOS to be used). I have summed up a bit of explanation and some answers to reasonable questions in a blog post: https://baldino.dev/blog/secs-man/
Jun 2026 · github.com
- 12
- 13SR
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
- 14
- 15
I have been working on Sesame, an open-source password manager that keeps your vault local by default. You don't need an account to create or use a vault, and the hosted service never receives the vault itself. It's still early software and the independent security review isn't finished yet, so I am mainly interested in feedback, testing, and people looking through the code. (Linux support is yet to be released on v0.1.2, but currently is in the works.)
9d ago · usesesame.app
- 16
- 17CT
2024 · github.com
- 18IJ
.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
- 19CA
Hello HN! We're all spending more and more time making stuff with agents, but I've noticed that one of the things that is the most disconnected from my daily engineering workflow is dealing with secrets and credentials. It often involves a lot of click-ops, copying/pasting, and collaboration, and none of the secrets management products out there have truly scratched that itch. I built Capy to solve this. It's a secrets manager whose entire frontend is a developer CLI, and I find it extremely ergonomic to use by hand. You also don't need to leave the CLI to sign up for and use it! You…
Aug 2026 · github.com
- 20
- 21PA
2017 · github.com
- 22IB
Hi HN, I built Envs.AI, a free tool to solve the headache of managing environment variables across different environments and platforms. Envs.AI lets you store all your environment variables in one secure place and easily integrate them with Jenkins, Python, and other platforms in your tech stack. No more scattered .env files or sharing secrets through Slack messages. Some features: - Central repository for all env variables - Secure storage with proper access controls - Simple integration with CI/CD pipelines - Easy access via API for different languages and frameworks - Team…
2025 · envs.ai
- 23
- 24EL
When someone here told me to focus on something more useful than reinventing the wheel. So. EnvCloak, a lightweight and simple tool for securely managing sensitive environment files. The design focuses on simplicity - just a few intuitive commands using the Click Python library. I assume seamless integration with CI/CD workflows. The aim is to provide a streamlined solution without the need for clunky tools. If you're tired of complex configurations or bloated alternatives, this might be worth a look! I would appreciate any feedback, feature ideas or input on how to improve this…
2024 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →