← Directory

Vault

HashiCorp Vault is a centralized secrets management platform that provides secure storage, dynamic secret generation, and identity-based access control for…

  • Backup
  • Plugins
  • Security
  • Tools & Utilities
HashiCorp Vault is a centralized secrets management platform that provides secure storage, dynamic secret generation, and identity-based access control for API keys, credentials, and encryption keys. It helps homelab administrators and DevOps teams automate secret rotation, encrypt data at rest, and enforce fine-grained access policies without manually distributing credentials across services.

Platform availability

Available on 2 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

75/100 Good

Maintained
100last commit 8 days ago
Popular
9136,350 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
208 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 17 days ago

GitHub stars
36,350
Open issues
1455
Last commit
2026-10-07
Latest release
v2.1.2
Activity
rising

Checked 8 days ago - source: GitHub (hashicorp/vault)

Resources & Compatibility

Minimum requirements: 8 GB RAM, 16 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Tell Vault Agent where its settings live If you use Vault Agent (an optional helper that fetches or renders secrets), pass your HCL (a settings-file format) file with -config. Without the correct path, the agent won't know how to reach Vault or produce secret files for your apps. source
  • Check that secret paths are mounted After Vault is running, use `vault secrets list` to see mounted paths like private/ or shared/. If a path your app expects is missing, Vault is up but the app can't find its secrets. source
  • Keep snapshot files in a known local folder If you restore a backup, make sure the snapshot file (.snap) exists at the exact local path you give to `vault operator raft snapshot load`. A missing or wrong path means the restore won't run, so you may not be able to recover secrets. source

Fetched 17 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why might Vault Agent not create secret files for an app?

Pass Vault Agent the correct HCL settings file path with -config. Without that path, the agent cannot reach Vault or render the expected secret files.

How does Vault protect secrets before they are written to storage?

Vault encrypts data before writing it to persistent storage. This means access to the raw storage alone is not enough to access the secrets.

What observability information should I use when troubleshooting Vault?

Use the observability data Vault provides to help resolve issues. It is part of the basic troubleshooting workflow.

Answers sourced from developer.hashicorp.com, developer.hashicorp.com, github.com

Community

Collected 11 days ago - public community threads