Commerce · alternatives · 2026
24 alternatives to Lockenv – Simple encrypted secrets storage for Git
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…
Lockenv is a password-protected vault tool for storing environment variables and secrets in Git repositories. Designed for teams seeking a simpler alternative to complex tools, it requires only initialization, password… Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1
Simple, secure, with an Env Vault for your .env files
Feb 2026 · lemonadepass.app · its alternatives →
- 2
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 · its alternatives →
- 3
GitGuardian▲132Detect secrets in source code, public and private!
2018 · gitguardian.com · its alternatives →
- 4
enject: Hide .env secrets from prAIng eyes: secrets live in local encrypted stores (per project) and are injected directly into apps at runtime, never touching disk as plaintext. - GreatScott/enject
Feb 2026 · github.com · its alternatives →
- 5
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 · its alternatives →
- 6
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 · its alternatives →
- 7
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 · its alternatives →
- 8
Vaulty▲90Ridiculously easy end-to-end encrypted data sharing
2023 · vaulty.tools · its alternatives →
- 9
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.)
Aug 2026 · usesesame.app · its alternatives →
- 10
- 11LH
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 · its alternatives →
- 12
AxKeyStore▲31Hi HN, I built AxKeyStore, an open-source CLI tool for managing secrets that uses your own private GitHub repository as encrypted storage. The idea is simple: → All encryption happens locally. → Secrets are stored as encrypted blobs in your private repo. → GitHub is treated as untrusted storage. → No plaintext secrets ever leave your machine. → No plaintext secrets are stored on disk. Most secret managers either require a hosted backend, a self-hosted server, or trusting a SaaS provider. I wanted something that: → Requires zero infrastructure → Uses tooling developers already have → Keeps…
Feb 2026 · github.com · its alternatives →
- 13
Generates self-contained HTML files protecting secret text content. - dividuum/html-vault
2020 · github.com · its alternatives →
- 14
Hi HN, I’m Daniel. I built Trust Vault. It’s a desktop open source app for protecting sensitive files using passwords, 256-bit master tokens, Shamir’s Secret Sharing, and HMAC integrity verification. We also built an Obsidian plugin. I’d appreciate feedback on the security model, UX, and potential use cases.
2025 · tvault.app · its alternatives →
- 15
Contribute to fmeringdal/covert development by creating an account on GitHub.
2023 · github.com · its alternatives →
- 16
Zero-knowledge secret manager for small dev teams
May 2026 · getvaultlite.com · its alternatives →
- 17
I built tinykv because I kept reaching for simple persistent storage in Rust projects but found existing solutions either too complex (sled) or unmaintained (pickledb). tinykv focuses on simplicity: JSON-based, serde-powered, with optional TTL. Perfect for CLI tools, game saves, config storage. Would appreciate any feedback from the HN community!
2025 · crates.io · its alternatives →
- 18
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 · its alternatives →
- 19
Hey everyone, English is not my native language. This post was polished with AI, but the content is mine. I run a small dev agency in Germany. Every week someone shares database credentials, API keys, or a .env file via Slack or email. Not because they don’t care: because there’s no frictionless alternative. Vault setups are heavy. Enterprise tools are expensive. I just needed: upload → share link → done. But encrypted before leaving the browser. So I built SecretDrop.dev. What it does Files encrypted client-side (AES-256-GCM, PBKDF2 600k iterations) Built entirely on WebCrypto No…
Feb 2026 · secretdrop.dev · its alternatives →
- 20
.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 · its alternatives →
- 21
- 22
A secure HashiCorp Vault for secrets, tokens, keys, passwords, and more. Automated deployment with Terraform on AWS. Configurable options for security and scalability. Usable with any applications and services hosted anywhere. - jcolemorrison/vault-on-aws
2020 · github.com · its alternatives →
- 23
Blockchain-powered password manager. Contribute to BlockProject/b-lock development by creating an account on GitHub.
2018 · github.com · its alternatives →
- 24KA
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 · its alternatives →
Also compare
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →