Skip to content
SPECIFICTION
Get listed

CyberArk Code Sign Manager - Self-Hosted vs DigiCert Software Trust Manager

CyberArk Code Sign Manager - Self-Hosted

docs.venafi.com

DigiCert Software Trust Manager

digicert.com

Side by side

FigureCyberArk Code Sign Manager - Self-HostedDigiCert Software Trust Manager
Price from——
Free plan——
Free trial——
Open source——
WebYesYes
WindowsYesYes
macOSYesYes
LinuxYesYes
APIYesYes
Self-hostedYes—
Plans published01
Spec score · Code Signing Software7.9 (#9)8.3 (#5)
Key protectionGPG private keys can be stored in the Trust Protection Foundation secret store or on a connected HSM, and the private keys do not leave Trust Protection Foundation.Keys can be stored in FIPS 140-2 Level 3 or Common Criteria EAL4+ HSMs, with regional key storage options.
PurposeProtects and governs use of private code signing keys managed by Trust Protection Foundation.Software Trust Manager protects software supply chain integrity through code signing, policy enforcement, and controls over key usage and access.

Plans

CyberArk Code Sign Manager - Self-Hosted

No plans published.

CyberArk Code Sign Manager - Self-Hosted pricing →

DigiCert Software Trust Manager

  • Software Trust ManagerPriced on request

DigiCert Software Trust Manager 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

DigiCert Software Trust Manager

DigiCert Software Trust Manager governs and automates software signing across artifacts, tools, and teams. Signing workflows can run after security checks and cover containers, binaries, and other artifacts, including Windows packages, Java archives, Android APK/AAB files, and macOS application and installer formats. Teams can use Signing Manager Controller, command-line tools, or the Click-to-sign graphical application, and connect workflows through native connectors, GitHub Actions, CLI tools, and APIs. Role- and team-based access, policy templates, workflows, and approvals govern high-risk signing actions. Logs link signed items to an actor and time for audits and incident response. Keys can be stored in FIPS 140-2 Level 3 or Common Criteria EAL4+ HSMs, with regional storage options. Threat detection includes software composition analysis, static binary analysis, Apple notarization scans, and DAST. Use requires a DigiCert ONE host environment, API key, client authentication certificate, and certificate password; two-factor authentication is required for all users. Pricing is on request, and a 30-day trial is listed.

Visit digicert.com