Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

KeyRack

keyrack.io

  • Free plan
  • API
  • Self-hosted
6.8 Club score Visit keyrack.io

What KeyRack is

KeyRack is an open-source key management coordination layer that you deploy in your own infrastructure; it is not a hosted cloud KMS. It tracks key hierarchies, coordinates rotation, and delegates cryptographic operations to configured backends. Its KEK-wrapping hierarchies support namespace-scoped rules and cascade operations. Authorization is checked for every operation through an external policy decision point such as Cedar or OPA. KeyRack does not bundle an identity provider, but can integrate with OIDC-compliant providers including Keycloak, Auth0, Okta, Azure AD, and Google Identity Platform.

Backend options include PKCS#11, HashiCorp Vault Transit, a KMIP client, and in-process software for development and testing. Audit events can be sent to NATS, files, or stdout, with BLAKE3 hash-chain linking and optional Ed25519 signing. Non-exportable keys in an HSM or Vault provider remain there; authorized export operations can allow exportable keys to leave. The self-deployed core is free under AGPL-3.0-or-later. Commercial extensions are separate, with pricing available by contacting KeyRack. TLS is opt-in for gRPC, and the REST listener serves plain HTTP; the maker recommends HTTPS termination at a reverse proxy.

Who it suits

KeyRack is aimed at teams in regulated industries, multi-cloud platforms, SaaS providers using HYOK, and OpenStack operators. It suits organizations prepared to deploy and operate key-management software in their own infrastructure and use an external policy decision point.

Good to know, and what to watch

  • Self-deployed open-source core is free.
  • Authorization is checked on every operation.
  • Supports PKCS#11 and HashiCorp Vault Transit backends.
  • Audit events can include BLAKE3 hash-chain linking.
  • REST listener serves plain HTTP.
  • TLS is opt-in for gRPC.
  • GCP Cloud KMS and Azure Key Vault shims are not implemented.
  • KeyRack does not bundle an identity provider.

Commercial licensing

—

Open source core

Free

Free plan

Getting started

  1. Open https://keyrack.io/
  2. Deploy the AGPL-3.0-or-later core in your own infrastructure
  3. Configure a key backend such as PKCS#11, Vault Transit, KMIP, or in-process software
  4. Connect an external policy decision point such as Cedar or OPA
  5. Integrate an OIDC provider if needed
  6. Choose NATS, files, or stdout for audit events

Limits to check

The free Open source core is self-deployed under AGPL-3.0-or-later. HA clustering, key pooling, management UI, vendor HSM adapters, KMIP server, and AWS KMS or Barbican shims are commercial extensions; GCP Cloud KMS and Azure Key Vault shims are roadmap items.

The Club's review

KeyRack is a self-hosted coordination layer for teams managing key hierarchies and directing cryptographic work to their own backends. It fits regulated organisations, multi-cloud platforms, HYOK SaaS providers and OpenStack operators that already run identity and policy services. The free core is capable and adaptable, but choosing it means taking on deployment and security configuration rather than adopting a finished cloud KMS.

Overview

KeyRack sits between applications and systems that hold or process keys. It tracks customer-managed keys, coordinates wrapping and rotation, and delegates cryptographic operations to PKCS#11 HSMs, HashiCorp Vault Transit, a KMIP client or an in-process software provider for development and testing. Non-exportable keys remain in an HSM or Vault backend; exportable keys can leave through an authorised export operation, so custody depends on the key policy you choose.

This is software for your infrastructure, not a hosted service. Your team operates the deployment and its surrounding controls. KeyRack does not include an identity provider, and authorisation is delegated to an external policy decision point such as Cedar or OPA, with a check on every operation. The REST listener uses plain HTTP and gRPC TLS is opt-in; HTTPS therefore needs to be terminated at a reverse proxy as part of a deliberate production design.

Key features

Hierarchies, rotation and policy

KEK-wrapping hierarchies, namespace-scoped rules and cascade operations provide a structured way to organise keys and apply changes across related keys. That is useful when teams need consistent rotation or separation between namespaces, but it also requires a policy design that matches those boundaries. External policy evaluation keeps decisions centralised, though it adds another service that must be available and correctly configured.

Backend choice and custody

The provider set covers HSM access through PKCS#11, Vault Transit, KMIP and a software backend for non-production work. This lets an organisation keep raw material in an existing protected system instead of moving it into KeyRack. It does not remove the need to control export permissions: authorised exports can still expose exportable keys.

Audit and interoperability

Audit events can go to NATS, files or standard output. BLAKE3 hash-chain links help reveal alteration in the event stream, while Ed25519 signing is optional rather than automatic. Commercial shims accept standard AWS SDK requests and the OpenStack Barbican REST API, making migration or compatibility easier for those ecosystems. GCP Cloud KMS and Azure Key Vault shims remain roadmap items, so those cloud integrations are not a current capability.

Identity and operations

OIDC-compatible providers including Keycloak, Auth0, Okta, Azure AD and Google Identity Platform can supply identity, but none is bundled. Issues are handled through GitHub, with a separate responsible-disclosure process for vulnerabilities. That is a workable community-support model for teams able to operate the project themselves, less so for organisations expecting a vendor-operated control plane.

Pricing

Open source core

The Open source core costs nothing. It is self-deployed under AGPL-3.0-or-later and provides the base coordination layer without a hosted option. This is the natural fit for engineering teams that can run infrastructure and accept the licence and operational responsibilities. Commercial extensions are separate.

Commercial licensing

Commercial licensing uses custom pricing, with evaluation access arranged by contacting KeyRack. It adds HA clustering, key pooling, AWS KMS and Barbican shims, a management UI, vendor HSM adapters and a KMIP server. Organisations needing those integrations or higher-availability operating patterns should budget for a commercial conversation rather than assuming the free core includes them.

Platforms

KeyRack is offered as an API-oriented, self-hosted deployment. It is not a web-hosted KMS or a desktop application, so platform choice centres on the infrastructure where your service, policy decision point and cryptographic backends run.

Who it's for

Choose KeyRack when your organisation must keep control of deployment and key custody, already operates HSM, Vault or KMIP infrastructure, and can provide OIDC identity plus Cedar or OPA-style policy decisions. Regulated industries, multi-cloud platforms, HYOK SaaS providers and OpenStack operators are the clearest matches. It is a weaker fit for a small team seeking a turnkey cloud KMS, bundled identity, or encrypted listeners without additional configuration.

Pros and cons

Pros

  • Free, open-source core: self-deployment avoids a service subscription and allows teams to align operation with their own infrastructure.
  • Backend flexibility: PKCS#11, Vault Transit, KMIP and a development software provider cover several custody models.
  • Structured control: hierarchies, namespace rules, cascade operations and per-operation policy checks support complex governance.
  • Verifiable audit delivery: NATS, files and stdout outputs, with BLAKE3 chaining and optional Ed25519 signatures, give operators multiple collection paths.

Cons

  • Operational burden: you run the service, identity integration and policy decision point yourself.
  • Transport defaults need attention: REST is plain HTTP and gRPC TLS is opt-in, so a reverse proxy and careful configuration are required.
  • Several useful integrations are paid: AWS and Barbican shims, HA, UI, vendor adapters and KMIP server require commercial licensing.
  • Cloud coverage is incomplete: GCP Cloud KMS and Azure Key Vault shims are not implemented.

Alternatives

Thales CipherTrust Data Security Platform is a better choice when you want a freemium platform with a free Community Edition, web and Linux options, and a free trial. Fornetix Key Orchestration Platform suits buyers seeking a paid, full-featured product with a 30-day trial and quote-based VaultCore plan. Oracle Cloud Infrastructure Secret Management is preferable for an OCI-native API and web service with a free allowance covering 5,000 secrets per tenancy and 30 active versions per secret. Entrust Certificate Manager is a paid, cross-platform certificate-management option with pricing supplied by Entrust. Kleopatra is the simpler free, open-source certificate manager for Linux and Windows. Cryptsoft KMIP Server is an alternative for organisations wanting a C or Java KMIP server SDK under a paid licence. Eviden KMS targets paid deployments with per-CPU pricing, included connectors and any number of servers. Fortanix Data Security Manager is worth considering for a full-featured 30-day SaaS trial rather than a free permanent plan.

For a wider comparison, see Key Management Software.

Verdict

KeyRack is a strong choice for infrastructure teams that need an open-source, self-hosted coordination layer over HSM, Vault or KMIP backends and can operate external identity and policy services. Its main reason to choose it is control across hierarchies, custody and rotation without committing the core to a hosted KMS. Look elsewhere if you need bundled identity, encrypted listeners by default, broad managed-cloud coverage or vendor-operated availability without buying extensions.

The verdict

KeyRack provides a self-hosted coordination layer for key hierarchies, rotation, and backend cryptographic operations. Teams should account for its external identity and policy dependencies, as well as the stated network security limits.

Questions people ask

Is KeyRack free?

The Open source core costs nothing and is licensed under AGPL-3.0-or-later. Commercial extensions use separate licensing; contact KeyRack for pricing and evaluation access.

Where does KeyRack run?

KeyRack is deployed in infrastructure you operate. Its listed platforms are API and self-hosted.

Does KeyRack include an identity provider?

No. It can integrate with OIDC-compliant providers including Keycloak, Auth0, Okta, Azure AD, and Google Identity Platform.

Which key backends are supported?

Providers include PKCS#11, HashiCorp Vault Transit, a KMIP client, and in-process software for development and testing.

Can KeyRack keep keys inside an HSM?

Yes. Non-exportable keys remain in the HSM or Vault provider, while authorized export operations can release exportable keys.

What the maker publishes

Audit
Audit events can be delivered through NATS, files, or stdout and include BLAKE3 hash-chain linking; Ed25519 signing is opt-in. source
Backends
Available providers include PKCS#11, HashiCorp Vault Transit, KMIP client, and in-process software for development and testing. source
Commercial limits
GCP Cloud KMS and Azure Key Vault shims are listed as roadmap items and are not implemented today. source
Deployment
KeyRack is software you deploy in your own infrastructure, rather than a hosted cloud KMS. source
Identity
KeyRack does not bundle an identity provider and can integrate with OIDC-compliant providers including Keycloak, Auth0, Okta, Azure AD, and Google Identity Platform. source
Integrations
The commercial AWS KMS shim accepts standard AWS SDK requests, while the commercial Barbican shim exposes the OpenStack Barbican REST API. source
Intended users
The maker identifies regulated industries, multi-cloud platforms, SaaS providers using HYOK, and OpenStack operators as audiences for KeyRack. source
Key custody
With non-exportable keys in an HSM or Vault provider, raw key material remains in that backend; exportable keys may leave through authorized export operations. source
Key hierarchy
It supports KEK-wrapping hierarchies with namespace-scoped rules and cascade operations. source
Policy
Authorization is delegated to an external policy decision point such as Cedar or OPA, with authorization checked on every operation. source
Product
KeyRack is an open-source key management coordination layer that tracks key hierarchies, drives rotation, and delegates cryptographic operations to HSM backends. source
Security limits
TLS is opt-in for gRPC, and the REST listener serves plain HTTP, so the maker recommends terminating HTTPS at a reverse proxy. source
Support
The maker directs users to GitHub issues for project issues and to a responsible disclosure process for security vulnerabilities. source

Checked against the maker's pages on 7 Oct 2026.