CyberArk Code Sign Manager - Self-Hosted vs LAAVAT PKI and Signing Platform
CyberArk Code Sign Manager - Self-Hosted
docs.venafi.comLAAVAT PKI and Signing Platform
laavat.ioSide by side
| Figure | CyberArk Code Sign Manager - Self-Hosted | LAAVAT PKI and Signing Platform |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | Yes |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Code Signing Software | 7.9 (#9) | 7.6 (#14) |
| Key protection | GPG 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. | Signing keys are generated inside AWS CloudHSM and never exist in plaintext outside the HSM. |
| Support | The maker says existing customers can continue to access product documentation, support, and guidance, and should use their existing support path for product-specific help. | The documentation directs users to contact [email protected] for unanswered questions. |
Plans
CyberArk Code Sign Manager - Self-Hosted
No plans published.
LAAVAT PKI and Signing Platform
- Custom quotePriced on request
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.
LAAVAT PKI and Signing Platform
LAAVAT PKI and Signing Platform has no write-up on Specifiction yet; its figures are above.