Alternatives
Products that do what KeyEnv – CLI-first secrets manager for dev teams (Rust) does
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.…
- 1SR
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
- 2

- 3

- 4

- 5

- 6

- 7

- 8LH
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
- 9ES
2017 · envkey.com
- 10

- 11

- 12IJ
.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
- 13GE
Hi! I've been frustrated with the secret sharing situation in serverside javascript land for a while; the common thing is to just toss .env files around on Slack to get someone's app working, or involves some kind of convoluted setup to get a blob from a storage and turn it into environment variables via commands I have to copy paste every time. But everyone uses secret storage providers, e.g. shared password vaults, cloud secrets, etc., so why not leverage those as URIs in a JSON file that can be checked in to source control? I want something simple that would just generate the darn .env…
2025 · github.com
- 14PO
Hello HN! We are developers and security researchers making tools for developers to encrypt data at an application level while maintaining sole control of their keys. We believe that data should always be encrypted unless it is part of an active computation. Encryption is relatively easy, but key management is challenging. There are plenty of encryption tools and SDKs that are out there (Hashicorp Vault, AWS KMS etc.) but we are focusing on ease and speed of implementation, developer experience and self custody of keys. A few months ago, we quit our jobs and started full time on Phase. So…
2023 · github.com
- 15IB
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
- 16KF
2018 · krypt.co
- 17

- 18EM
2018 · github.com
- 19CT
2024 · github.com
- 20AB
I'm the creator of node.js' dotenv. I'm making a better dotenv called dotenvx. * run anywhere (cross-platform) * multi-environment * encrypted envs What do you think?
2024 · github.com
- 21EL
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
- 22AO
I’ve lost count of how many times a junior engineer accidentally pushed something into a dev branch that either contained secrets/credentials etc. or that leaked those into logs/std. out. Secure-log prevent logging for apps on production, scan for Secrets and remove them from logging. No more console.log().
2024 · github.com
- 23SS
Hi HN! I've been building a project that handles high-value credentials in-process, and I wanted something more robust than just zeroing memory on drop. A comment on a recent Show HN[0] made me realize that awareness of lower-level memory protection techniques might not be as widespread as I thought. The idea here is to pull out all the tools in one crate, with a relatively simple API. * mlock/VirtualLock to prevent sensitive memory from being swapped (eg the KeePass dump) * Core dump exclusion using MADV_DONTDUMP on Linux & Android * mprotect to minimize exposure over time * Guard…
Mar 2026 · github.com
- 24TS
Hello Hacker News community! I'm currently working in financial risk management within the banking sector, and I began my career as a Data Science specialist. For quite some time, my friend and I have been developing a small pet project just for fun. This tool has repeatedly helped us save time when testing various hypotheses and machine learning models. The core idea is to combine different scripts—created in various programming languages and virtual environments—within a minimalist graphical interface. Whether you're building models, running a local neural network, or sending requests to…
2024
Ranked by how close each launch is in meaning, then by votes. Refine with a description →