Building a better way to manage environment variables and application secrets

I built a tool called Envie because I was tired of the chaos around environment variables, API keys, and other secrets.

If you’ve ever:

• Juggled multiple .env files (.env.local, .env.prod, .env.debug… and forgotten which one is actually being used)

• Wasted time digging through Slack threads or web dashboards just to find the right API key to debug a production issue

• Accidentally committed (or had your AI commit) a secret or left sensitive files lying around on your machine

…then you know the pain that led me to start this project.

What is Envie?

Envie is an open-source, self-hostable CLI + service for managing secrets and environment variables.

• Cleaner workflow → No more dumping .env files on disk.

• Team-friendly → Stop passing credentials around in chat. Use Envie with fine grained access control.

• Safer by default → Less chance of secrets leaking (especially with AI tools scanning local files).

• Built for real-world dev setups → Works well with monorepos, Turborepos, and projects with lots of apps/packages.

• General secrets manager for production use: Self hostable and open source

Think of it as a more modern, developer-friendly alternative to dotenv and scattered .env files.

Contributors welcome! Check out Envie on GitHub: https://github.com/ilmari-h/envie