A deep-dive page for each key management service and secrets platform — what it protects, where key material lives, and what it costs.
The default if you are on AWS — a dollar a key, and every other AWS service already knows how to use it.
Microsoft’s answer, and the one that blurs keys, secrets and certificates into a single service.
The cleanest of the three cloud services, with the most serious answer for keys you refuse to hand over.
The tool that defined the category — now an IBM product under a licence that is no longer open source.
The community fork of Vault, made when the licence changed — same shape, genuinely open, no vendor above it.
Vault-shaped capability delivered as SaaS — and a key architecture where even the vendor cannot read your secrets.
The developer-first one — open source, self-hostable, and it does not require a platform team to adopt.
Config and secrets as a managed service — the least ceremony of anything here, and priced per seat.
Keys inside hardware enclaves, unified across clouds — built for people whose threat model includes the cloud provider.
The incumbent for regulated enterprises — the vendor auditors already recognise, with the hardware to match.