LAAVAT PKI and Signing Platform
5.6#18 in code signing softwareWebAPISelf-hosted
VisitLAAVAT PKI and Signing Platform vs SignPath
What both publish
| Fact | LAAVAT PKI and Signing Platform | SignPath |
|---|---|---|
| Deployment models | Customers can use a shared HSM, a dedicated LAAVAT-managed HSM, a customer-managed HSM in their AWS account, or on-premises deployment. | SignPath is offered as managed SaaS, self-hosted software or a hybrid deployment. |
| Headquarters | Tampere, Finland | Vienna, Austria |
| Integrations | Integrations include REST, EST, Microsoft Entra ID, Google SSO, Yocto, CI/CD clients and provisioning-station clients. | The company lists plugins and REST API integrations for GitHub Actions, GitLab, Jenkins, Azure DevOps, and TeamCity. |
| Key protection | Signing keys are generated inside AWS CloudHSM and never exist in plaintext outside the HSM. | Private keys remain in SignPath-managed or customer-managed HSMs; the architecture page states FIPS 140-2 Level 3 compliance. |
LAAVAT PKI and Signing Platform plans
- Custom quotePriced on request
SignPath plans
- Open Source Code SigningFree
- Code GovernancePriced on request
- Software Integrity PlatformPriced on request
Pick LAAVAT PKI and Signing Platform if…
You want what its maker publishes above — check its page for the details.
Pick SignPath if…
SignPath suits development teams that need controls around signing and verifying software releases. Its free option is for qualifying open source projects; deployment choices also include self-hosted and hybrid.