CyberArk Code Sign Manager - Self-Hosted vs sslTrus Remote Code Signing Service
CyberArk Code Sign Manager - Self-Hosted
docs.venafi.comsslTrus Remote Code Signing Service
nicsrs.comSide by side
| Figure | CyberArk Code Sign Manager - Self-Hosted | sslTrus Remote Code Signing Service |
|---|---|---|
| Price from | — | $6.25/mo |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | — |
| Plans published | 0 | 4 |
| Spec score · Code Signing Software | 7.9 (#9) | 7.2 (#21) |
| Deployment | Code Signing is installed as part of a standard Trust Protection Foundation installation, with Certificate Lifecycle and Monitoring, Key Lifecycle and Monitoring, HSM Backend, Authentication Server, Web Console, and Web SDK listed as required components. | After certificate issuance, users download lightweight signing tools for installation on a server or computer; critical encryption occurs in the cloud HSM. |
| Purpose | Protects and governs use of private code signing keys managed by Trust Protection Foundation. | The service provides remote cloud code signing for software applications. |
| 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. | NicSRS lists pre-sale consultation, online support, and a ticket system among its support channels. |
Plans
CyberArk Code Sign Manager - Self-Hosted
No plans published.
sslTrus Remote Code Signing Service
- sslTrus Cloud Code Signing Basic$75 a year
- sslTrus Cloud Code Signing Pro$285 a year
- sslTrus Cloud Code Signing Enterprise$640 a year
- sslTrus Cloud Code Signing Ultimate$2,860 a year
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.
sslTrus Remote Code Signing Service
sslTrus Remote Code Signing Service has no write-up on Specifiction yet; its figures are above.