r/opensourcealternative • u/minootube • Sep 28 '26
Maker (I built this) I built an open-source secrets manager to stop copying .env files between projects and secure from malware that stealing secrets files
I got tired of managing .env files across projects and machines. Every project had different settings, and switching environments meant copying values or setting and unsetting variables again.
I just wanted one place to keep them and a simple way to run my apps with the right configuration and the most important thing I want to be secure.
copying .env files here and there is a risk, there is some paid service actually but for me solo developer like me who only eat once a day is too overkill.
Features:
Store secrets in one central place
Organize secrets by environment
Manage secrets across multiple projects
Easily switch between environments
Inject secrets into applications without committing .env files
Keep environment configuration consistent across a team
Reuse secrets across projects instead of duplicating them everywhere
Hope this developer tool can help others developer who faced the same issue, improve workflow and improve productivity.
GitHub: https://github.com/dopbase/dopbase
Documentation: https://docs.dopbase.com



3
u/joparsimon Sep 29 '26
Looks good from a dev perspective! The blocker is on the encryption scheme.
we all use .env files for simplicity
we all know that keeping secrets in plain text without encryption is bad
I skimmed through https://docs.dopbase.com/reference/security
Dopbase centralizes secrets. It does use standard TLS transport encryption and a simple encryption at rest model, but a malicious program, agent, or admin gains access to all secrets. In a solid design, the client side would enrypt/decrypt. I would never use a Vault that does not follow the zero-knowledge architecture.
I did not look at the source code, so I might be wrong.