git-crypt vs One-Time Secret
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
One-Time Secret
Share sensitive credentials with self-destructing links
| Feature | git-crypt | One-Time Secret |
|---|---|---|
| Category | Password Managers | Password Managers |
| License | GPL-3.0 | MIT |
| Language | C++ | Ruby |
| Setup difficulty | Easy | Easy |
| Min. RAM | 32 MB | 256 MB |
| Deployment | binary, source | docker, bare-metal |
| GitHub stars | ★ 9,837 | ★ 2,894 |
| First released | 2013 | 2012 |
| Replaces | HashiCorp Vault, AWS Secrets Manager | 1Password, Doppler |
Why pick each one
Choose One-Time Secret if…
- Great for one-off credential sharing
- Easy to self-host
Frequently asked questions
Is git-crypt or One-Time Secret better?
Neither is universally better. git-crypt has the larger community; both share a easy setup difficulty, so the decision comes down to features and licensing.
Are git-crypt and One-Time Secret free and open-source?
Yes. git-crypt is licensed under GPL-3.0 and One-Time Secret under MIT. Both can be self-hosted at no software cost.
Can I run git-crypt and One-Time Secret with Docker?
git-crypt: check the project docs for container support. One-Time Secret: yes.