Alternatives
Products that do what Vaultlet does
Keep your secrets secret — straight from the terminal
- 1
- 2
- 3
- 4
- 5
- 6
- 7EH
Feb 2026 · github.com
- 8KE
Keeper is an embeddable secret store (Argon2id, XChaCha20-Poly1305 by default). Four security levels, audit chains, crash-safe rotation. Vault is overkill for most use cases. This is for when you ge paranoid about env and need encrypted local storage that doesn't suck. No security through obscurity, hence, It's still early, so now's the best time to find weird edge cases, race conditions, memory leaks, crypto misuse, anything that breaks. The README has a full security model breakdown if you want to get adversarial.
Apr 2026 · github.com
- 9
- 10
- 11
- 12
- 13LH
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
- 14OS
2024 · github.com
- 15MS
2025 · github.com
- 16CA
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
- 17
- 18WA
just wanted to share ward, a tool i hacked together to encrypt and manage sensitive files in a vault folder. it's written in bash and meant to be cloned and then stored using git or version control. you don't have to store it that way, it's just why i created it. what ward does: encrypts the files in ./vault/ into a single .gpg file, checks to see if your files have been tampered with, generates totp codes if you need them to recover critical accounts. how to use it: clone the repo, toss your files into the vault directory, and run yarn encrypt. now commit your new [private]…
2024 · github.com
- 19
- 20
- 21VO
2020 · github.com
- 22KC
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
- 23KA
Hi HN, I made Keepr, a simple offline CLI password manager for developers who prefer keeping secrets local and working entirely in the terminal. Everything is stored in an encrypted SQLCipher database, protected by a master password. A time-limited session keeps the vault unlocked while you work, so you don’t need to re-enter the password constantly. Keepr never touches the network. It includes commands to add, view, search, update, and delete entries, plus a secure password generator and clipboard support. Technical details: - AES-256 via SQLCipher - PBKDF2-HMAC-SHA256 (1.2M iterations) for…
Nov 2025
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →