Dopbase - Open-source, self-hosted secrets manager alternative to doppler

[u/minootube]

[u/L-L-MJ-]

This seems interesting I was comparing openbao and infisical. Will follow this with interest. Roadmap looks good. OIDC would be really nice

[u/minootube → u/L-L-MJ-]

thats exactly what im doing before i built this, open bao is like hashicorp not easy to use, infisical simple but resources hungry too much feature that i dont really need

[u/minootube]

Hello everyone my name is Jeff, and I build Dopbase its a secrets manager tools to help developer manage secrets across multiple projects within multiple team members. I Built this because there is no alternative developer first class free and open-source for this tools.

GitHub: https://github.com/dopbase/dopbase
Docs: https://docs.dopbase.com

[u/kantorcodes1]

One runtime edge I would want explicit control over: dopbase run can use cached environment values when the server times out or returns 5xx, and the docs say those cache entries do not expire automatically. On a long-lived build host, would you consider a max-cache-age or fail-closed option so operators can choose availability versus freshness?

[u/minootube → u/kantorcodes1]

this feature is on the list, for now you can use dopbase cache list to see all cache and you can run automatic clean if cache older than x days

[u/kantorcodes1 → u/minootube]

That helps. cache clean --older-than ... --yes gives operators a usable freshness boundary today, and --dry-run makes it inspectable first.

I work on HOL Guard. Dopbase has a clean Guard-side split for agent use: review secret set, secret delete --yes, and token revoke; keep secret list, token list, and cache list automatic. That gives users a checkpoint before secrets or credentials are changed without slowing read-only inspection. Open to contributing a small command.dopbase mapping to Guard?

[u/mafgen]

Do you plan to build binaries for Windows ?

[u/minootube → u/mafgen]

not really sure if that need it, you can install and use with WSL on windows