Bloombase KeyCastle vs OpenKCM (Open Key Chain Manager)

Bloombase KeyCastle manages cryptographic keys and certificate authority certificates, including private signing keys, public verification keys, authentication keys, and data encryption keys. It supports key creation, import, protected storage, verification, validation, inquiry, and deletion. Bloombase says keys stored in KeyCastle cannot technically be retrieved in plain form; its specifications say capacity is limited by available system storage, not a preset key count. Listed algorithms include AES, RSA, SHA hashes, Camellia, SEED, ARIA, and post-quantum options such as CRYSTALS-Kyber and CRYSTALS-Dilithium. KeyCastle supports PKCS#11 hardware security modules, OASIS KMIP, and a listed FIPS 140-2 compliant Bloombase Cryptographic Module. It connects with key services from AWS, Google, IBM, Microsoft Azure, and Oracle. Certificate functions include X.509 and PKCS#12 import and export, validity checks, retrieval, and revocation checks. Administration includes web and command-line consoles, central configuration, SNMP, and syslog. Optional high availability supports active-active or active-standby operation; recovery options include configuration backup and restore and recovery quorums. Pricing is on request, and Bloombase says customers may request a 30-day evaluation kit.

OpenKCM (Open Key Chain Manager) is a free, open-source key management service for governing encryption keys and protecting data at rest. It supports BYOK key import and HYOK, which keeps master keys in a customer’s infrastructure. Its recursive L1–L4 hierarchy makes data keys dependent on higher-level keys. Governance and policy control are handled by CMK, while Krypton performs cryptographic execution; applications request key operations through the KMIP API.

The Gateway is designed to run near applications, such as in Kubernetes or a cloud VPC, and the same software can operate across AWS, Azure and on-premise environments. Customer root keys can remain in AWS, Azure or GCP key services, or on-premise HSMs, while OpenKCM holds a reference to the L1 key. A kill switch can halt downstream key use by removing that reference or revoking the root key. CMK connects to a corporate identity provider and sends audit logs to SIEM systems. The project’s CMK and Krypton components are actively being developed; encryption and decryption operations are in progress, while audit export, high availability and disaster recovery are planned for 2027.