I got tired of chasing .env files in Group chats, so I built a Git-native secrets manager

Viswajith MP — Wed, 23 Sep 2026 06:45:40 +0000

Tired of chasing .env files in team group chats?

We’ve all been there:

You pull the latest code, run the app, and it crashes. "Wait, did someone add a new env var?"

Someone pastes a block of plaintext secrets into a Slack or WhatsApp group. Now it lives in your chat history forever.

The dreaded 2 AM git add . that accidentally commits your local .env to the repository.

Switching to a staging branch but forgetting to swap your .env, resulting in experimental code hitting production data.

I got tired of being the unofficial IT department for my own projects, so I built EnvSeal CLI.

It’s not a cloud service, and it doesn't have a dashboard. It’s an offline, Git-native secrets manager built in Rust. Think of it as "Git for secrets": your vault is just an encrypted file (.envseal) in your repo.

It switches automatically with git checkout, resolves merge conflicts like code, and uses SSH/Age encryption so you can onboard teammates with a single command (envseal recipient add @github-handle). No cloud accounts, no shared master passwords, no telemetry.

If you're on a small team, working on side projects, or just want your secrets to live in Git without the overhead, I'd love for you to try it out and tear it apart.

Check out the repo: github.com/viswajith275/EnvSeal-CLI
Read the docs honest trade-offs: envseal-cli.vercel.app

How do you currently handle team secrets? Let me know your workflow (or your brutal feedback) in the comments!

DEV Community: Viswajith MP

I got tired of chasing .env files in Group chats, so I built a Git-native secrets manager