How Fortanix DSM and Google Cloud KMS differ on scope, key custody, deployment and cost.
| Fortanix DSM | Google Cloud KMS | |
|---|---|---|
| Type | Confidential computing KMS | Cloud KMS |
| Scope | Keys, secrets, tokenisation | Encryption keys |
| Deployment | SaaS + on-premise | SaaS (GCP) |
| Key custody | Intel SGX enclaves; FIPS 140-2 Level 3 | HSM tier FIPS 140-2 Level 3; External Key Manager for off-cloud keys |
| How it works | Data Security Manager runs key operations inside confidential-computing enclaves rather than conventional HSM appliances, presenting one key management plane across multiple clouds and on-premise. Also covers tokenisation and, increasingly, post-quantum readiness. | Key rings and key versions with explicit rotation, offered in software, HSM and external tiers. External Key Manager is the differentiator: the key stays in your own system and Google calls out to it, so the cloud can be denied access by design rather than by policy. |
| Pricing* | Enterprise quote | Metered per key version + operations |
| Free tier | No | No |
| Licence | — | — |
| Best for | Multi-cloud estates with strict key custody | GCP workloads and hold-your-own-key rules |
Choose Fortanix DSM for multi-cloud estates with strict key custody. Choose Google Cloud KMS for gcp workloads and hold-your-own-key rules.
* Published list pricing (vendor pricing pages, August 2026).