git-crypt vs pass-tomb
A side-by-side comparison of two self-hosted password managers options — licensing, setup difficulty, resource needs, and what each one replaces.
Not the right match-up?
git-crypt
Transparent file encryption for secrets stored in git
VS
pass-tomb
Encrypted storage extension for the pass manager
| Feature | git-crypt | pass-tomb |
|---|---|---|
| Category | Password Managers | Password Managers |
| License | GPL-3.0 | GPL-3.0 |
| Language | C++ | Shell |
| Setup difficulty | Easy | Hard |
| Min. RAM | 32 MB | 64 MB |
| Deployment | binary, source | binary, source |
| GitHub stars | ★ 9,837 | ★ 435 |
| First released | 2013 | 2017 |
| Replaces | HashiCorp Vault, AWS Secrets Manager | 1Password, KeePass |
Why pick each one
Choose pass-tomb if…
- Released under the GPL-3.0 license
- Written in Shell
- Tiny footprint — runs in 64 MB RAM
Frequently asked questions
Is git-crypt or pass-tomb better?
git-crypt is the stronger all-round pick: it has both the larger community and the simpler easy setup. Consider pass-tomb if its specific feature set fits your needs better.
Are git-crypt and pass-tomb free and open-source?
Yes. git-crypt is licensed under GPL-3.0 and pass-tomb under GPL-3.0. Both can be self-hosted at no software cost.
Can I run git-crypt and pass-tomb with Docker?
git-crypt: check the project docs for container support. pass-tomb: check the project docs for container support.