Alternatives
Products that do what envfix does
A tiny .env doctor for Node.js projects
- 1
- 2QT
2017 · github.com
- 3
- 4
- 5
- 6
- 7CF
2016 · github.com
- 8
- 9
- 10AB
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
- 11GE
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
- 12HV
2014 · gregosuri.com
- 13SV
It works on my machine" is still the most common deployment bug I kept running into the same stupid deployment issue. Everything works locally. Tests pass. I deploy. Production crashes. After digging through logs for an hour the problem ends up being something simple like: • a missing environment variable • something added to .env.example but not to .env • a config mismatch between environments The most common one for me was forgetting to add a variable locally after adding it to .env.example. So I built a small tool to catch this instantly. It compares .env and .env.example and tells you if…
Mar 2026 · npmjs.com
- 14IB
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
- 15
- 16
- 17IJ
.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
- 18SN
Stop-nagging is a Rust CLI tool I built to automatically silence those annoying upgrade prompts, telemetry, and advertising nags that plague our development tools. It works by setting environment variables and running configuration commands without modifying source code. * Fast, zero-config Rust binary * Linux, Windows and macOS compatible * Uses YAML for easy contribution of new tools * Never fails (exits 0) to avoid breaking CI pipelines * Respects existing environment variables * Works across multiple ecosystems (Node.js, Python, Rust, etc.) The tool is designed to be simple - run it once…
2025
- 19GE
2020 · github.com
- 20EL
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
- 21CT
2024 · github.com
- 22AA
We've rolled out a feature for openbase.com that we think is a DX game changer for Node devs. Since the emergence of ECMA Script modules, it's been a continuous guessing game as to what kind of exports a package has. That's never really been discoverable without using a site like unpkg, or installing the package and inspecting package.json. Openbase now displays the ES Module support level (e.g. type of exports) on all of their package pages. We added this feature because our devs are some of the folks continually caught off guard by installing an NPM dependency only to find out it's…
2022
- 23PE
Now that I have your attention (“Don’t you dare version control environment files!!”, “This can’t be safe.”) and before you tear me and my project to shreds, please allow me to take a moment to celebrate something small but meaningful: I’ve finally released a thing. Thank you. Motivation tl;dr: The existing tools and libraries for versioning and syncing environment files / secrets across team members and CI machines just didn’t cut it for me. So, I set out to create my own solution — one finally checks all my boxes. So what is places-env? (I encourage you to check the readme…
2024 · github.com
- 24KC
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
Ranked by how close each launch is in meaning, then by votes. Refine with a description →