Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

VMware Secrets Manager

vsecm.com

  • Free plan
  • Linux
  • API
  • Self-hosted
7.4 Club score Visit vsecm.com

What VMware Secrets Manager is

VMware Secrets Manager, also called VSecM, is a free, open-source secrets store for Kubernetes workloads. It keeps sensitive values in memory and encrypts data written to disk and backups. Workload identity uses SPIFFE, with SPIRE as the default identity control plane and other SPIFFE-compatible options supported. Secrets can reach applications through a sidecar, init container, SDK, or Kubernetes Secret, and can change at runtime without rebooting workloads. VSecM records creation and update times, preserves versions, supports GoLang transformations, and can federate secrets across namespaces and clusters. Its SDK can retrieve rotated values without an application restart. Installation uses Helm charts or Makefile targets and requires Helm, kubectl, a running cluster, and make. The project runs only on Kubernetes, is distributed under the BSD 2-Clause License, and offers community help through Slack and GitHub Issues.

Who it suits

VSecM suits teams already operating Kubernetes clusters that need workload identity, runtime secret delivery, and versioned secret management. It is intended for self-hosted deployments rather than standalone installations.

Good to know, and what to watch

  • Free and open source under BSD 2-Clause
  • Supports several Kubernetes secret delivery methods
  • Runtime rotation avoids application restarts
  • Maintains secret versions and timestamps
  • Can federate secrets across namespaces and clusters
  • Runs only on Kubernetes
  • Plaintext storage is limited by memory
  • FIPS mode is off by default
  • Secretless recovery may require manual root-key entry

Free and open source

Free

Open source

The verdict

VSecM provides Kubernetes-focused secret storage with multiple delivery paths, identity controls, and runtime rotation. Its Kubernetes-only design and in-memory capacity model are central considerations for deployment planning.

What the maker publishes

Compatibility
VSecM is designed to run on Kubernetes only and is not intended to run outside Kubernetes or as a standalone binary. source
Data protection
Sensitive data is stored in memory, while data saved to disk and backups are encrypted. source
Encryption
The production documentation says VSecM Safe encrypts secrets using age, or AES-256-GCM in FIPS-compliant environments. source
Federation
VSecM supports federation of secrets across namespaces and clusters. source
FIPS mode
FIPS mode is off by default and can be enabled by setting VSECM_SAFE_FIPS_COMPLIANT to true. source
Identity
VSecM uses SPIFFE as its identity control plane for workload authentication. source
Identity integration
VSecM uses SPIRE as its default identity control plane, and SPIFFE-compatible identity control planes can also be used. source
Installation
VSecM installs into a Kubernetes cluster using Helm charts or Makefile targets; the documented prerequisites include Helm, kubectl, a running cluster, and make. source
Kubernetes requirement
VSecM is designed to run only on Kubernetes, not as a standalone binary or outside Kubernetes. source
Legacy workloads
VSecM can create Kubernetes Secret objects for workloads that cannot use its SDK or Sidecar integration. source
License
The VSecM code is distributed under the BSD 2-Clause License. source
No admin token
VSecM requires no admin token for operation, though users may provide a root token and then manually unlock after a crash. source
Operational limit
VSecM Safe keeps plaintext secrets in memory, so the quantity of secrets is limited by the memory allocated to it. source
Project status
The project is in active maintenance mode while development focuses on SPIKE v1.0; new feature implementations are deferred during this period. source
Project status
The project says it is in active maintenance mode, prioritizing security fixes while deferring new feature development until SPIKE reaches v1.0. source
Purpose
VMware Secrets Manager is a cloud-native secrets store for securely storing configuration and dispatching it to workloads. source
Purpose
VMware Secrets Manager is a Kubernetes-native key-value store for securely storing and dispatching secrets to cloud-native workloads. source
Resilience
Workloads can continue using existing secrets when a VSecM component fails, and the component can recover state from an encrypted backup. source
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. source
Rotation
The VSecM SDK can retrieve rotated secrets without requiring the application to restart or be evicted. source
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. source
Secret delivery
Secrets can be delivered to workloads with the VSecM SDK, Sidecar, or Init Container, or persisted as Kubernetes Secret objects. source
Secret history
VSecM records creation and update timestamps and keeps version history for secrets. source
Secretless mode
If operators opt out of Kubernetes Secrets for root-key protection, they must manually provide the root key again after VSecM Safe restarts or is evicted, crashes, or rescheduled. source

Checked against the maker's pages on 11 Oct 2026.