Keyfactor Platform vs OpenPubkey

Keyfactor Platform, through Keyfactor Command, gives PKI, security, infrastructure, and DevOps teams visibility into certificates and tools to govern their lifecycle. It can inventory certificates from certificate authorities, scan networks for unknown SSL/TLS certificates, and connect to key and certificate stores. Teams can automate enrollment, renewal, revocation, and provisioning, with self-service workflows available through a user interface or API. Listed enrollment protocols are SCEP, ACME, and EST. Administrators can set role-based permissions, protect private keys with retention and storage policies, and require enrollment or approval workflows. Integrations span CI/CD, cloud, HSM, IoT, ITSM, public and private certificate authorities, and web servers. Deployment options are on premises, as a hosted certificate lifecycle service, or as fully managed PKI in a single-tenant cloud platform. Keyfactor says Command has been tested for deployments with more than 500 million certificates. A 30-day trial is offered. Pricing is available on request, and there are no per-certificate fees listed.

OpenPubkey binds a user or workload identity established through OpenID Connect to a public key, so the identity can sign messages or artifacts. A PK Token represents control of an OIDC identity and its related private key at a particular time, provided the verifier trusts the identity provider. The project lists Google, Azure/Microsoft, Okta, OneLogin and Keycloak as compatible without changes to those providers; however, its client and verifier currently create and verify tokens from Google for users and GitHub for workloads. Current workload identity use requires GQ signatures. For user identity, they are unnecessary when the PK Token is not public. GQ signatures allow the identity provider’s signature to be stripped from an ID Token while preserving proof of that signature, preventing use against OIDC resource providers. OpenPubkey says it needs no additional certificate authority because the OpenID Provider fulfills that role. Public PK Tokens can reveal claims from an OIDC ID Token, potentially including a name or email address. The project is free under the Apache 2.0 license and is a Linux Foundation project; its repository says it is being prepared for version 1.0. The project directs technical questions to GitHub issues and offers a community Slack channel.