Alternatives
Products that do what OnlyNv does
Sync your .env everywhere automatically
- 1
- 2
- 3
- 4
- 5PE
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
- 6IJ
.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
- 7
- 8
- 9
- 10
- 11IB
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
- 12
- 13HA
2017 · github.com
- 14SV
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
- 15US
2020 · github.com
- 16
- 17SV
Hi HN, I've been waiting to post what I've been working on for a few weeks now:) Today we're launching LayerVault, which is a version control system made for designers. The URL is http://www.layervault.com LayerVault keeps track of what you're working on without adding extra steps to your process. The app runs in your toolbar and tracks changes you make to your files. Basically — each time you create or modify a file you’re working on, LayerVault saves a copy. You can then login, flip through its versions, and download a version from a few weeks ago. It's pretty neat — and we’ve built some…
2011
- 18HV
2014 · gregosuri.com
- 19LP
2016 · github.com
- 20GM
2013 · pypi.python.org
- 21GY
After a few years of development, I'm finally ready to show off an alpha version of graft! My goal was to get my local environment, terminal, ide, and preferences on any machine I connect to. I've set everything up the way I like locally, so why should it get muddied by an ssh/docker session? Graft solves this by transparently synchronizing files, comamnds, and open ports. There's a lot of work to do but maybe someone else can benefit from it now!
Mar 2026 · graft.run
- 22GE
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
- 23LH
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
- 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 →