Skip to content
SPECIFICTION
Get listed

CyberArk Code Sign Manager - Self-Hosted vs Sigstore

CyberArk Code Sign Manager - Self-Hosted

docs.venafi.com

Sigstore

sigstore.dev

Side by side

FigureCyberArk Code Sign Manager - Self-HostedSigstore
Price from—Free
Free plan—Yes
Free trial——
Open source—Yes
WebYesYes
WindowsYesYes
macOSYesYes
LinuxYesYes
APIYesYes
Self-hostedYesYes
Plans published02
Spec score · Code Signing Software7.9 (#9)8.3 (#7)
PurposeProtects and governs use of private code signing keys managed by Trust Protection Foundation.Sigstore is an open source project for improving software supply chain security.
SupportThe maker says existing customers can continue to access product documentation, support, and guidance, and should use their existing support path for product-specific help.Community support is provided through Slack and GitHub issues, with repository CODEOWNERS identifying project maintainers.

Plans

CyberArk Code Sign Manager - Self-Hosted

No plans published.

CyberArk Code Sign Manager - Self-Hosted pricing →

Sigstore

  • FreeFree
  • Public-good Sigstore serviceFree

Sigstore pricing →

In their own words

CyberArk Code Sign Manager - Self-Hosted

CyberArk Code Sign Manager - Self-Hosted protects and governs private code signing keys managed by Trust Protection Foundation. Keys can be held in the platform’s Secret Store or on an HSM. Administrators can set restrictions based on purpose, user, and IP address, and configure whether signing requires approvals. Approval flows can have multiple levels, limited-use approvals, and expiration options; approvers receive email notifications to review requests. The system audits key use, and APIs expose event logs and signing statistics. REST APIs can request signing, manage projects and environments, set user rights, inspect logs, and approve or reject requests. Identities and groups can be added through Active Directory or an LDAP provider and assigned roles in signing projects. Clients are available for Windows, Linux, and macOS, with interfaces including CSP/KSP, PKCS#11, GPG, and macOS Keychain; .NET is listed for Windows. GPG private keys remain within Trust Protection Foundation while public keys and private-key stubs synchronize to workstations. Installation is part of a Trust Protection Foundation deployment and requires several listed components, including Certificate Lifecycle and Monitoring, Key Lifecycle and Monitoring, HSM Backend, Authentication Server, Web Console, and Web SDK. Pricing is on request.

Visit docs.venafi.com

Sigstore

Sigstore is a free, open source project for signing and verifying software artifacts to improve supply chain security. It supports release files, container images, binaries, software bills of materials, and more. Signatures use temporary keys, so developers do not have to manage signing keys; events are recorded in a tamper-resistant public log for audit. Its components include Cosign, Fulcio, Rekor, OpenID Connect, and Policy Controller. Cosign signs and verifies artifacts and stores signatures in an OCI registry. Fulcio issues temporary certificates to authorized identities, while Rekor keeps signed metadata in a searchable ledger. OpenID Connect authenticates users through providers such as GitHub and Google. The trust root uses The Update Framework and is maintained by five keyholders from different companies and academic institutions. Sigstore provides GitHub Actions, documents GitLab CI installation, and offers official clients for Go, Java, JavaScript, Python, Ruby, and Rust. It supports API, Linux, macOS, Windows, and self-hosted environments. One integration caveat is that Cosign has no API stability guarantees, does not follow semantic versioning, and is not recommended for application integration because of its dependencies.

Visit sigstore.dev