Aujas Automated Code Signing Platform vs SignPath
Aujas Automated Code Signing Platform
aujas.com
SignPath
signpath.ioSide by side
| Figure | Aujas Automated Code Signing Platform | SignPath |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 4 |
| Spec score · Code Signing Software | 8.6 (#2) | 8.4 (#4) |
| Deployment | The datasheet lists on-premises deployment in a customer data center, public cloud, and managed cloud hosting. | SignPath describes its deployment options as SaaS, self-hosted, or hybrid. |
| Integrations | The datasheet describes integration with corporate directories, SAML identity providers, command-line interfaces, and HSM key stores. | The company lists plugins and REST API integrations for GitHub Actions, GitLab, Jenkins, Azure DevOps, and TeamCity. |
| Key protection | Signing keys are managed in an HSM or secure keystore, and access is allowed through CodeSign for approved requests from authorized users and machines. | Private keys remain in SignPath-managed or customer-managed HSMs; the architecture page states FIPS 140-2 Level 3 compliance. |
| Malware scanning | The leaflet describes an enterprise-grade malware scanner that inspects files before signing. | Artifacts can be scanned for malware before signing, with signing blocked when policy checks fail. |
| Purpose | CodeSign is a secure, automated, DevOps-ready solution for ensuring software application integrity, protecting signing keys, and helping combat malware. | SignPath provides code signing and software integrity tools that enforce policies across software builds and releases. |
Plans
Aujas Automated Code Signing Platform
- Pay-as-use signing-based licensesPriced on request
SignPath
- Open Source Code SigningFree
- Open Source Code SigningFree
- Code GovernancePriced on request
- Software Integrity PlatformPriced on request
In their own words
Aujas Automated Code Signing Platform
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.
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.