goraz v0.2.0

goraz compared with HashiCorp Vault, OpenBao, SOPS and gopass

goraz is young and hasn't been audited. All the projects below have far longer track records. Choose goraz when its design fits your need and you accept that.

Which should I use?

You needConsider
Central control, instant revocation across many servers, teams and policiesOpenBao or HashiCorp Vault
Short-lived database or cloud credentialsOpenBao or Vault
Encrypted config files reviewed in git, with cloud KMSSOPS
To encrypt a file for someoneage
A team password store in gitgopass
A desktop password manager with browser integrationKeePassXC or Bitwarden
A hosted service you don't run yourselfDoppler or 1Password
Secrets for a few services without running a server, and token issuing in Gogoraz

How goraz differs

gorazVault, OpenBaoSOPSgopass
Needs a serverNoYesNoNo
Item names hiddenYesAt restNo, by designNo
Detects older filesYes, with limitsOut of their threat modelNoNo
Per-service accessA separate encrypted filePoliciesSeparate filesPer-store recipients
Dynamic credentialsNoYesNoNo
Team sharingNoYesYesYes
Merge-friendly in gitNoNot applicableYesPer file
Issues API tokens for your appYesIts own tokensNoNo
Independent auditNoneVault, 2026; none found for OpenBaoNone foundNone found

Where this comes from

The full research, with sources, is in the comparison of earlier projects. What goraz leaves out is in the feature matrix.

Edit this page on GitHub