OpenKCM (Open Key Chain Manager)
openkcm.io
- Linux
- API
- Self-hosted
What OpenKCM (Open Key Chain Manager) is
OpenKCM (Open Key Chain Manager) is an open-source key management service for governing encryption keys and protecting data at rest. It supports importing customer keys through BYOK and keeping master keys in the customer’s infrastructure through HYOK. Keys follow a recursive L1–L4 hierarchy, with data keys dependent on higher-level keys. Its design separates governance and policy control in CMK from cryptographic execution in Krypton; applications request operations through the KMIP API. The Gateway is intended to run near applications, such as in Kubernetes or a cloud VPC, and the same software can run across AWS, Azure, and on-premise environments. Root keys can remain in AWS, Azure, or GCP key services, or in on-premise Thales or Entrust HSMs, while OpenKCM keeps a reference to the customer’s L1 root key. A kill switch can stop downstream key use by removing that pointer or revoking the root key. CMK connects to corporate identity providers and sends audit logs to SIEM systems. The project’s CMK and Krypton components are actively being developed; encryption and decryption are in progress, while audit export, high availability, and disaster recovery are planned for 2027.
Who it suits
OpenKCM is intended for regulated-data organizations, enterprises with regional key-management needs, SaaS platforms seeking BYOK or HYOK, and developers of encrypted storage solutions. It may suit teams prepared to work with a project whose components are still in development.
Good to know, and what to watch
- Apache-2.0 licensed open-source repositories
- Supports BYOK and HYOK key models
- Customer root keys can remain in external stores
- KMIP API for application key operations
- Gateway can run in cloud or on-premise environments
- CMK and Krypton are actively being developed
- Encryption and decryption are in progress
- Audit export, high availability, and disaster recovery are planned for 2027
The verdict
OpenKCM offers a customer-controlled key hierarchy and separates governance from cryptographic execution. Its stated development status and roadmap matter for teams evaluating it for operational use.
What the maker publishes
- Architecture
- OpenKCM separates governance and policy control in CMK from cryptographic execution in Krypton. source
- BYOK and HYOK
- It supports importing customer keys (BYOK) and keeping master keys in the customer’s own infrastructure (HYOK). source
- Cryptographic operations
- The Krypton execution plane wraps and unwraps keys using keys temporarily loaded into secure memory. source
- Deployment
- The documentation describes deploying the Gateway near applications in a Kubernetes cluster or cloud VPC, and says the same Gateway software can run across AWS, Azure, and on-premise environments. source
- Development status
- The project documentation says the CMK layer can be tried through its repository instructions and Krypton is in active progress. source
- Edge deployment
- The Krypton Gateway is described as running in an application environment such as Kubernetes or a VPC. source
- External key stores
- The trust model names AWS, Azure, and GCP key services and on-premise HSMs as locations for customer root keys. source
- Governance and execution
- The trust model separates the CMK governance plane from the Krypton cryptographic execution plane. source
- Identity and audit
- The CMK component connects to a corporate identity provider and outputs audit logs to SIEM systems. source
- Integrations
- The trust model names AWS, Azure, and GCP external KMS services and on-premise Thales or Entrust HSMs as locations for customer root keys. source
- Intended users
- The maker identifies regulated-data organizations, enterprises with regional key-management needs, SaaS platforms seeking BYOK or HYOK, and developers of encrypted storage solutions as intended users. source
- Intended users
- The maker identifies cloud-native organizations, enterprises with regional key lifecycle needs, SaaS platforms, and developers of encrypted storage as intended users. source
- Key hierarchy
- It organizes keys in a recursive L1–L4 hierarchy and describes data keys as dependent on higher-level keys. source
- Key management
- It supports key hierarchies, importing customer keys through BYOK, and keeping master keys in the customer’s infrastructure through HYOK. source
- Key security
- The trust model says the customer’s L1 root key remains in the customer’s external KMS or HSM, while OpenKCM holds a reference to it. source
- License
- The OpenKCM GitHub organization lists its CMK and Krypton repositories under the Apache-2.0 license. source
- Planned work
- The project roadmap lists encryption and decryption operations as in progress, while audit export, high availability, and disaster recovery are planned for 2027. source
- Project home
- OpenKCM says it is a project of Linux Foundation Europe. source
- Project status
- The project’s GitHub page says its CMK control plane and Krypton crypto layer are actively being developed and links to documentation and a roadmap. source
- Protocol
- OpenKCM describes KMIP as its standard API for applications to request key operations. source
- Purpose
- OpenKCM is an open-source key management service for governing encryption keys and protecting data at rest. source
- Purpose
- OpenKCM is an open-source key management service for managing cryptographic keys across services and regions. source
- Revocation
- OpenKCM describes a kill switch that can stop downstream key use by deleting the root-key pointer or revoking the root key. source
Checked against the maker's pages on 5 Oct 2026.