No. 30 of 40 ·Secrets Management Tools

VMware Secrets Manager

Linux · Self-hosted · API

Freedom report

One barScore 5.3

Free tierNo free tier on record
Open codeNo open-source code on record
Runs widely1 of 6 device platforms
DocumentedPlans, terms and facts published

VMware Secrets Manager is ranked #30 of 40 in secrets management tools on Freedom251. It runs on API, Linux, Self-hosted.

Compared on secrets management tools

Kubernetes integration: Yes
Deployment model: self_hosted
Audit logs: Yes

Best VMware Secrets Manager alternatives

See all 20

Two bars Envshed Free tier No. 1$5/mo6.6 Two bars Keyway Free tier No. 2€9/mo6.6 Two bars Kubermatic Kubernetes Platform Free tier No. 3Free6.6 Two bars Phase Free tier No. 4$10/mo6.6 Two bars SikkerKey Free tier No. 5$29/mo6.6 Two bars dotenvx Free tier No. 6$5/mo6.5

The record

Purpose: VMware Secrets Manager is a cloud-native secrets store for securely storing configuration and dispatching it to workloads.
Kubernetes requirement: VSecM is designed to run only on Kubernetes, not as a standalone binary or outside Kubernetes.
Identity: VSecM uses SPIFFE as its identity control plane for workload authentication.
Secret delivery: Secrets can be changed dynamically at runtime without rebooting workloads, and can be delivered through a sidecar, init container, SDK, or Kubernetes Secret.
Secret history: VSecM records creation and update timestamps and keeps version history for secrets.
Transformations: VSecM supports GoLang transformations on secrets and interpolation of stored secrets onto Kubernetes Secrets.
Federation: VSecM supports federation of secrets across namespaces and clusters.
Data protection: Sensitive data is stored in memory, while data saved to disk and backups are encrypted.
Resilience: Workloads can continue using existing secrets when a VSecM component fails, and the component can recover state from an encrypted backup.
No admin token: VSecM requires no admin token for operation, though users may provide a root token and then manually unlock after a crash.
Installation: VSecM installs into a Kubernetes cluster using Helm charts or Makefile targets; the documented prerequisites include Helm, kubectl, a running cluster, and make.
Resource limits: The project notes that in-memory storage limits capacity and says a couple of gigabytes of RAM can hold many plain-text secrets.
Project status: The project is in active maintenance mode while development focuses on SPIKE v1.0; new feature implementations are deferred during this period.
Security response: The stated target is to fix confirmed medium-or-higher severity vulnerabilities within 60 days and respond initially to vulnerability reports within 14 days.

Where it ranks on Freedom251

Best Secrets Management Tools in 2026#30 of 40

Is VMware Secrets Manager yours?

Claim it for free: prove the domain, then correct facts, plans and screenshots. An editor reviews every change.

Claim it free Promote VMware Secrets Manager

Sources

vsecm.com/documentation/welcome/overview/· checked 5 Oct 2026
vsecm.com/documentation/architecture/philosophy/· checked 5 Oct 2026
vsecm.com· checked 5 Oct 2026
vsecm.com/documentation/welcome/about/· checked 5 Oct 2026
vsecm.com/documentation/usage/installation/· checked 5 Oct 2026
vsecm.com/documentation/operations/security/· checked 5 Oct 2026