DigiCert Software Trust Manager vs Red Hat Trusted Artifact Signer
DigiCert Software Trust Manager
digicert.comRed Hat Trusted Artifact Signer
access.redhat.comSide by side
| Figure | DigiCert Software Trust Manager | Red Hat Trusted Artifact Signer |
|---|---|---|
| Price from | — | — |
| 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 | 1 | 1 |
| Spec score · Code Signing Software | 8.3 (#5) | 7.5 (#18) |
| Founded | 2003 | 1993 |
| Headquarters | Lehi, Utah, USA | Raleigh, North Carolina, USA |
| Integrations | Listed integrations include Azure DevOps, CircleCI, GitLab, Gradle, Jenkins, GitHub, and ReversingLabs. | Red Hat lists Podman, Quay, Ansible, Red Hat Advanced Cluster Security, StoneSoup/HACBS, and Red Hat Trusted Content among products adopting or integrating Sigstore. |
| Purpose | Software Trust Manager protects software supply chain integrity through code signing, policy enforcement, and controls over key usage and access. | RHTAS simplifies cryptographic signing and verification of software artifacts, including container images, binaries, and Git commits. |
Plans
DigiCert Software Trust Manager
- Software Trust ManagerPriced on request
Red Hat Trusted Artifact Signer
- Red Hat Trusted Artifact SignerPriced on request
In their own words
DigiCert Software Trust Manager
DigiCert Software Trust Manager governs and automates software signing across artifacts, tools, and teams. Signing workflows can run after security checks and cover containers, binaries, and other artifacts, including Windows packages, Java archives, Android APK/AAB files, and macOS application and installer formats. Teams can use Signing Manager Controller, command-line tools, or the Click-to-sign graphical application, and connect workflows through native connectors, GitHub Actions, CLI tools, and APIs. Role- and team-based access, policy templates, workflows, and approvals govern high-risk signing actions. Logs link signed items to an actor and time for audits and incident response. Keys can be stored in FIPS 140-2 Level 3 or Common Criteria EAL4+ HSMs, with regional storage options. Threat detection includes software composition analysis, static binary analysis, Apple notarization scans, and DAST. Use requires a DigiCert ONE host environment, API key, client authentication certificate, and certificate password; two-factor authentication is required for all users. Pricing is on request, and a 30-day trial is listed.
Red Hat Trusted Artifact Signer
Red Hat Trusted Artifact Signer (RHTAS) helps organizations sign and verify software artifacts, including container images, binaries, documents, source-code commits, software bills of materials, build artifacts, and AI/ML models. Red Hat describes it as an enterprise deployment of Sigstore. Its client tools include cosign, gitsign, and rekor-cli. Signing can use OpenID Connect identities or self-managed keys held in a third-party key management system. A certificate transparency log records signing events in an immutable ledger that Red Hat says is inaccessible to the public. Deployment guidance covers Red Hat OpenShift Container Platform and Red Hat Enterprise Linux; Amazon EKS is listed as a development preview for RHTAS 1.4. The OpenShift guide requires version 4.16 or later, cluster-admin access, an OIDC provider, and the oc command-line tool. CLI binaries are listed for Windows, macOS, and Linux. Pricing is on request, and a 60-day trial is listed. Signing and verifying AI/ML models with the CLI is marked Technology Preview and is not covered by production SLAs.