CyberArk Secrets Manager vs Secrets Manager

CyberArk Secrets Manager centrally stores and governs credentials used by applications, containers, CI/CD pipelines and other workloads across cloud, on-premises and hybrid environments. It handles API keys, tokens, passwords, certificates and database credentials, with policies to rotate, expire and retire secrets while tracking ownership and expiration. Organizations can use managed SaaS or run it in a customer data center, including where data residency or air-gap requirements apply. Applications and containers can authenticate through application attributes and role-based controls, and key events are recorded in tamper-resistant audit logs. Its SaaS service assigns workloads cryptographic SPIFFE identities based on verified attributes; the identities expire in hours and cannot be shared or reused. Listed integrations span DevOps, CI/CD, automation, PaaS and public cloud tools. The product page describes a distributed, high-availability design. CyberArk was founded in 2005 and is headquartered in Santa Clara, California. Pricing is on request; the product page directs visitors to request a demo.

Secrets Manager is a free, open-source, self-hosted system for storing application secrets in encrypted form, managing them through a web interface, and injecting them into processes with a command-line tool. Users organize secrets by organization, project, and environment, import.env files, edit or reveal values, keep versions, roll back, and soft-delete entries. The `secrets run` command supplies environment secrets to a child process and its descendants without creating a.env file. Documented workflows cover Node.js, Python, npm, and Next.js; CI or deployment can use an API URL, token, and environment ID. User and service-account grants can be scoped to projects or environments, and revealing values requires explicit permission. AES-256-GCM envelope encryption uses a separate data key per value, while plaintext values are not stored in the database. Audit events include secret reveals, and values are withheld if audit writing fails. Docker Compose starts PostgreSQL, Redis, backend, and frontend; local Kubernetes manifests are also provided. A user-generated master key is mandatory and lost keys make secrets unrecoverable. The repository is MIT licensed.