Aujas Automated Code Signing Platform vs Cosign

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.

Cosign is a free tool for signing and verifying OCI container images and other software artifacts. It can store container signatures in an OCI registry and publish generic artifacts through OCI. Supported targets include blobs, binaries, scripts, configuration files, SBOMs, WASM modules, Tekton bundles, eBPF modules, and in-toto attestations whose payloads use DSSE. Its default keyless workflow uses temporary keys held in memory, short-lived certificates from Sigstore’s Fulcio certificate authority, and entries in the Rekor transparency log. Other signing options include hardware and KMS-backed keys, encrypted keypairs generated by Cosign, and user-provided PKI. Cosign supports CI/CD signing, with guidance for GitHub Actions and GitLab CI/CD. Offline verification is possible when the image and signature materials are available locally and a trusted root is supplied. The project describes Cosign as a legacy signing system and recommends Sigstore-go for verification integrations. Its CLI-focused design has no API stability guarantees, and the documentation does not recommend it for application integration.