Freedom251 › Code Signing Software
Red Hat Trusted Artifact Signer
What Red Hat Trusted Artifact Signer is
Red Hat Trusted Artifact Signer (RHTAS) helps organizations create and verify cryptographic signatures for software artifacts, including container images, binaries and Git commits. Red Hat describes it as an enterprise deployment of the Sigstore project. Its client tools include cosign, gitsign and rekor-cli. Signing can use OpenID Connect identities or existing self-managed keys held in a third-party key management system. A certificate transparency log records signing events in a permanent, immutable ledger that Red Hat says is inaccessible to the public. Red Hat lists integrations or adoption involving Podman, Quay, Ansible, Red Hat Advanced Cluster Security, StoneSoup/HACBS and Red Hat Trusted Content. 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.
Who it suits
RHTAS suits organizations that need to sign and verify software artifacts as part of their software supply-chain processes. The OpenShift deployment path requires OpenShift Container Platform 4.16 or later and an OIDC provider.
What it does well
- Client tools include cosign, gitsign and rekor-cli.
- Supports identity-based signing through OpenID Connect.
- Signing events enter a permanent, immutable ledger.
- A 60-day trial is listed.
What to know first
- Pricing is on request.
- OpenShift deployment requires version 4.16 or later.
- AI/ML model CLI signing is Technology Preview.
- Technology Preview features are not covered by production SLAs.
Limits
The product has no free plan, and pricing is available on request. CLI signing and verification of AI/ML models is marked Technology Preview and is not covered by production SLAs.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Red Hat Trusted Artifact Signer | Pricing not stated on the product pages opened; contact Red Hat for sales information | On request |
As access.redhat.com lists them, read 30 Sept 2026. The maker's own page has the final word.
Getting started
- Review the RHTAS product page and request pricing or the 60-day trial.
- Choose an environment covered by the deployment guidance: OpenShift Container Platform or Red Hat Enterprise Linux.
- For OpenShift, prepare version 4.16 or later, cluster-admin access, an OIDC provider, and the oc command-line tool.
- Configure an OIDC provider such as Red Hat SSO, Google, Amazon STS, GitHub, Red Hat build of Keycloak, or Microsoft Entra ID.
- Install a CLI binary for Windows, macOS, or Linux and use the Sigstore clients to sign or verify artifacts.
Verdict
RHTAS provides signing and verification tools for software artifacts, with identity-based options and a transparency log. Buyers should review deployment prerequisites and note that AI/ML model signing through the CLI is a Technology Preview, not covered by production SLAs.
Questions
How much does Red Hat Trusted Artifact Signer cost?
Pricing is available on request. A 60-day trial is listed.
Is there a free plan?
No. RHTAS is listed as paid and has no free plan.
Which platforms are supported?
The listed platforms include Linux, macOS, self-hosted, web, and Windows. Deployment guidance covers OpenShift Container Platform and Red Hat Enterprise Linux; Amazon EKS is a development preview for RHTAS 1.4.
What can RHTAS sign?
Supported targets include container images, binaries, documents, source-code commits, software bills of materials, build artifacts, and AI/ML models.
Which identity providers can be configured?
The deployment guide describes Red Hat SSO, Google, Amazon STS, GitHub, Red Hat build of Keycloak, and Microsoft Entra ID as OIDC providers.
Who makes RHTAS?
Red Hat makes RHTAS. The company says it was founded in 1993 and lists its address in Raleigh, North Carolina.
Facts from Red Hat Trusted Artifact Signer's own pages
- Deployment platforms
- The deployment guide covers Red Hat OpenShift Container Platform and Red Hat Enterprise Linux; supported-platform information also lists Amazon EKS as a development preview for RHTAS 1.4. · access.redhat.com, 30 Sept 2026
- Deployment prerequisite
- The OpenShift deployment guide requires OpenShift Container Platform 4.16 or later, cluster-admin access, an OIDC provider, and the oc command-line tool. · docs.redhat.com, 30 Sept 2026
- Downloads
- Red Hat's download page lists CLI binaries for Windows, macOS, and Linux. · developers.redhat.com, 30 Sept 2026
- Founded
- 1993 · access.redhat.com, 28 Sept 2026
- Headquarters
- Raleigh, North Carolina, USA · access.redhat.com, 28 Sept 2026
- Identity and keys
- RHTAS supports identity-based signing through OpenID Connect and can use existing self-managed keys maintained in a third-party key management system. · developers.redhat.com, 30 Sept 2026
- Integrations
- Red Hat lists Podman, Quay, Ansible, Red Hat Advanced Cluster Security, StoneSoup/HACBS, and Red Hat Trusted Content among products adopting or integrating Sigstore. · developers.redhat.com, 30 Sept 2026
- Lifecycle
- Red Hat describes full support and maintenance support phases and says a release reaches end of life after its maintenance phase. · access.redhat.com, 30 Sept 2026
- Maker
- Red Hat says it was founded in 1993 and lists its address at 100 E. Davie Street, Raleigh, NC 27601. · redhat.com, 30 Sept 2026
- OIDC providers
- The deployment guide describes configuring Red Hat SSO, Google, Amazon STS, GitHub, Red Hat build of Keycloak, and Microsoft Entra ID as OIDC providers. · docs.redhat.com, 30 Sept 2026
- Production support
- Red Hat states that support for RHTAS is subject to its Production Scope of Coverage, Service Level Agreement, and product life cycle, and includes help with setup, administration, deployment, and configuration. · access.redhat.com, 30 Sept 2026
- Purpose
- RHTAS simplifies cryptographic signing and verification of software artifacts, including container images, binaries, and Git commits. · access.redhat.com, 30 Sept 2026
- Signing clients
- Its Sigstore client tools include cosign, gitsign, and rekor-cli for generating and verifying signatures. · developers.redhat.com, 30 Sept 2026
- Sigstore
- Red Hat describes Trusted Artifact Signer as a production-ready enterprise deployment of the Sigstore project. · developers.redhat.com, 30 Sept 2026
- SLSA
- Red Hat says RHTAS can help enterprises meet signing-related criteria for Supply-chain Levels for Software Artifacts (SLSA) compliance. · developers.redhat.com, 30 Sept 2026
- Technology preview limitation
- The administration guide marks signing and verifying AI/ML models with the CLI as Technology Preview and says Technology Preview features are not supported by production SLAs. · docs.redhat.com, 30 Sept 2026
- Transparency log
- The certificate transparency log records signing events in a permanent, immutable ledger that the page says is inaccessible to the public. · developers.redhat.com, 30 Sept 2026
Where Red Hat Trusted Artifact Signer stands on Freedom251
- Code Signing Software#21 of 28