Alternatives
Products that do what VaultLite does
Zero-knowledge secret manager for small dev teams
- 1IO
Last month, we open-sourced Infisical (https://github.com/Infisical/infisical) - a simple, end-to-end encrypted tool to sync environment variables across your team and infrastructure. You can use it to store environment variables and inject them into your applications locally or into CI/CD and production infrastructure. It can be used with any language/framework and is platform independent with a super easy setup. We know secret managers exist but, in our experience, they’re too complicated, not comprehensive, not user-friendly, or a mix of all three — other…
2022 · github.com
- 2LS
Hi! I got tired of setting up tools I can't explain to a team in a few words like sops or git-crypt, just to store few files with environment variables or secrets, so I built lockenv as a simple alternative. It's basically a password-protected vault file you commit to git. No gpg keys, no cloud, just lockenv init, set a password, and lock/unlock the secrets. This tool integrates with OS keyring, so you're not typing passwords constantly. Should work on Mac/Linux/Windows, but I tested it only on linux so far. I am not trying to replace any mature / robust solution, just…
Dec 2025 · github.com
- 3
- 4
- 5
- 6E2
Hey HN, I'm so happy to finally show you all this release after years of hard work. I posted the first version of EnvKey to HN back in 2017 (https://news.ycombinator.com/item?id=15330757), then went through YC in W18 (https://news.ycombinator.com/item?id=16569534). EnvKey is an end-to-end encrypted configuration and secrets manager. It protects your organization's API keys, encryption keys, credentials, and other secrets, and makes it easy to run servers, scripts, tests, and everything else with the latest config. It also helps you avoid duplication in your…
2022 · v2.envkey.com
- 7EH
Feb 2026 · github.com
- 8
- 9RO
Finally open sourced an internal tool we've been using for managing secrets. It's similar to SOPS, but more opinionated, easier to configure/use correctly, and produces nicer git diffs. It also supports one-way encryption, so you don't have to know the private key to add secrets.
2023 · github.com
- 10
- 11
- 12KC
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
- 13
- 14
- 15
- 16
- 17LH
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
- 18VO
2020 · github.com
- 19
Secure zero-knowledge link sharing for developer credentials
Jun 2026 · secrettly.space
- 20SR
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
- 21KG
Hi HN, I've been building this tool for the past couple of weeks to solve a problem that seems universal across development teams: sharing environment variables securely. You know the drill - someone needs the staging database URL, so it gets shared over chat. Production API keys end up in plaintext files. Or you set up some complex secret management system that becomes a single point of failure during critical deployments. At Zerodha, we're a stock broker with strict regulatory requirements. Our infrastructure needs to be auditable, and our data must stay with us for instant recovery. But…
2025 · kiln.sh
- 22CD
Hi everyone! We started working on this project last year because a password manager that we used was being sold to another company and stopped offering their service. We were not happy with the alternatives that were available so we decided to give it a shot and build our own. We are now at a point where we have a working Beta and are looking for some feedback from the community. The main idea is to have data synchronization without a central server (single point of failure). When you create a Vault (inside which you can store your credentials and other sensitive data), you can "Link" it to…
2023 · cryptex-vault.com
- 23AL
2025 · github.com
- 24CA
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
Ranked by how close each launch is in meaning, then by votes. Refine with a description →