I built a secrets manager because sharing .env files at work was painful!

Working in the financial industry means dealing with strict security policies. That is understandable when the systems you work on handle sensitive information, but those policies can also make simple development tasks surprisingly difficult.

One example was how we shared .env files.

Our policy required us to use an approved secure file-sharing channel. We could not send environment files through email or messaging apps. The process kept secrets away from insecure communication channels, so it did what it was supposed to do.

The problem appeared whenever something changed.

Updating one environment variable meant repeating the entire sharing process:

1. Update the .env file.
2. Upload the new version to the approved platform.
3. Generate a new secure link.
4. Notify everyone who needed the update.

A small configuration change became an administrative task. The security controls were necessary, but the developer experience was frustrating.

Turning the problem into a project

After dealing with this process many times, I started building my own secrets manager.

I called it Dopbase.

The idea was simple, secrets should remain encrypted and controlled, but developers should not have to keep passing updated files around manually. I wanted a system built specifically for managing secrets instead of treating them like ordinary files.

Dopbase came from a problem I experienced at work. It was not an imaginary use case or an attempt to build another developer tool for the sake of it. I needed a better way to handle a repetitive task while still respecting strict security requirements.

Security and developer experience can coexist

Working in finance taught me that security policies exist for good reasons. The problem is that a secure process can still be inconvenient.

Good developer tools should help teams follow security rules without adding unnecessary work. When the secure option is also the practical option, developers are less likely to look for shortcuts.

That is the problem I am trying to solve with Dopbase.

Dopbase is free and open source. You can search for it on GitHub or Google if you would like to explore the project.

I am sharing it because other developers may have faced the same .env file-sharing problem. If you have, I would be interested to hear how your team handles it.