Your repository knows how to build your app. Why shouldn't it know where to find its secrets?
We've all been there. A new developer joins, someone shares a .env file, credentials get copied around, and keeping everything in sync becomes another maintenance task.
That's why I built Envilder.
The idea is simple: define an envilder.json that maps your application's environment variables to secrets already stored in AWS Systems Manager Parameter Store or Azure Key Vault.
For example: "DATABASE_URL": "/myapp/dev/database-url"
No actual secrets in Git. Just references that your team can version, review, and share across local development, CI/CD, and runtime.
And you don't have to change how you work:
- Pull secrets into your existing
.env, preserving comments, formatting, and unrelated variables. - Push new or updated secrets back to your cloud provider, useful for bootstrapping and rotation.
- Exec applications, tests, or scripts with secrets injected into the process environment, without creating
.envfiles. Especially useful with AI coding agents, without pasting credentials into chats.
The same contract also works with GitHub Actions and native .NET, Python, and Node.js SDKs.
No new secrets manager. No servers to maintain. No unnecessary infrastructure.
Just a lightweight, free, open-source toolkit built for developers and small teams who value simplicity, security, and minimal friction.
Want to see how it works?
- Watch the demo - See Envilder in action.
- Get started - Install it and try it yourself.
- Explore the project on GitHub - Check out the source code, contribute, or leave a star.
If you find it useful, I'd really appreciate your support!
