AWS Key Management Service vs Bloombase KeyCastle
AWS Key Management Service
aws.amazon.comBloombase KeyCastle
bloombase.comSide by side
| Figure | AWS Key Management Service | Bloombase KeyCastle |
|---|---|---|
| Price from | $1/mo | — |
| Free plan | — | — |
| Free trial | — | Yes |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| API | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Encryption Key Management Software | 8.0 (#4) | 8.4 (#1) |
| Integrations | KMS integrates with AWS services including Amazon S3, Amazon EBS, Amazon RDS, Amazon DynamoDB, AWS Lambda, and AWS CloudTrail. | Listed integrations include RDBMS, generic LDAP, PKCS#11, OpenSSL, Java JCA/JCE, and web services. |
| Key protection | KMS uses hardware security modules validated to FIPS 140-3 Security Level 3 to protect key material and cryptographic operations. | Bloombase says generated or imported keys are stored and locked down in KeyCastle, with no technical way to retrieve their plain contents. |
| Purpose | AWS KMS creates and controls cryptographic keys used to encrypt data and digitally sign it. | KeyCastle manages the life cycle of private and public signature keys, authentication keys, data encryption keys, and certificate authority certificates. |
Plans
In their own words
AWS Key Management Service
AWS Key Management Service creates and controls cryptographic keys for data encryption and digital signatures. It centralizes key lifecycles and permissions, including separate control over administrators and key users. KMS supports symmetric encryption, asymmetric signing or encryption pairs, and HMAC generation and verification. The AWS Encryption SDK can use KMS as a key provider for local application encryption and decryption. Integrations include Amazon S3, EBS, RDS, DynamoDB, Lambda, and CloudTrail. With CloudTrail enabled, requests can record the user, time, API action, and key. AWS says hardware security modules validated to FIPS 140-3 Security Level 3 protect key material and operations, with plaintext keys kept only in volatile HSM memory. Multi-Region keys support cross-Region workflows; external key stores keep material in a customer-managed external manager. KMS scales with demand but has default key and request limits. The listed plan is $1 a month per KMS key, prorated hourly.
Bloombase KeyCastle
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.