ComSignTrust Secure Code Signing Platform (ASCS) vs SignPath
ComSignTrust Secure Code Signing Platform (ASCS)
comsigntrust.com
SignPath
signpath.ioSide by side
| Figure | ComSignTrust Secure Code Signing Platform (ASCS) | SignPath |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 4 |
| Spec score · Code Signing Software | 7.5 (#17) | 8.4 (#4) |
| Access controls | Access control can be configured by organizational policy using passcodes, OTP, biometric authentication, certificates and other methods. | Role-based access controls define who can sign which artifacts, when, and with which certificate. |
| Founded | 2009 | 2017 |
| Headquarters | Tel Aviv, Israel | Vienna, Austria |
| Purpose | ASCS signs code files to authenticate their origin and integrity and the identity of the developing organization. | SignPath provides code signing and software integrity tools that enforce policies across software builds and releases. |
| Support | ComSignTrust offers remote administration, configuration and installation guidance, onsite installation and organization-specific feature development. | SignPath provides a support portal and lists [email protected] as a contact address. |
Plans
ComSignTrust Secure Code Signing Platform (ASCS)
- Access Secured Code Signing (ASCS)Priced on request
SignPath
- Open Source Code SigningFree
- Open Source Code SigningFree
- Code GovernancePriced on request
- Software Integrity PlatformPriced on request
In their own words
ComSignTrust Secure Code Signing Platform (ASCS)
ComSignTrust Secure Code Signing Platform (ASCS) has no write-up on Specifiction yet; its figures are above.
SignPath
SignPath provides code signing and software integrity controls for builds and releases. Its format-aware signing covers executables, packages, installers, containers, scripts, manifests, SBOMs, and configuration files. Before trusting a release, it can verify source repositories, branches, build systems, approvals, and CI/CD context. SignPath can produce signed, machine-readable attestations, including SLSA provenance, validation summaries, and signed SBOMs. Listed integrations include plugins and REST API connections for GitHub Actions, GitLab, Jenkins, Azure DevOps, and TeamCity. SignPath says private keys remain in FIPS-compliant hardware security modules and are never exposed or shared. Role-based controls determine who can sign which artifacts and with which certificate. Signing records include the user, file, certificate, policy, and result; reports can be exported, with optional WORM-style log archiving. Deployment options are SaaS, self-hosted, or hybrid. The free Open Source Code Signing plan has eligibility conditions: projects must be actively maintained and released, use an OSI-approved open source license, and have no proprietary components.