Aujas Automated Code Signing Platform vs CyberArk Code Sign Manager - Self-Hosted

Aujas Automated Code Signing Platform, or CodeSign, manages signing requests across software build and release processes. It routes approvals for projects, builds, and certificates, and records approval and file-signing activity. Signing keys and certificates can be held in an HSM or secure keystore, with access limited to authorized users and machines for approved requests. The platform supports signing through command-line integration, including parallel submissions, and can be included in DevOps pipelines. Listed options include basic, GPG, hash, force, append, MAGE, and WHQL signing; a malware scanner can inspect files before signing. Certificate support includes self-signed, standard certificates from any CA, and Extended Validation certificates. Aujas lists more than 50 supported file types, with plugins to add types, and support for Windows, Linux, and macOS. Deployment choices include a customer data center, public cloud, and managed cloud hosting. CodeSign is paid, with pricing on request; Aujas offers a scheduled demo covering platform features, architecture, and application flow.

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.