Skip to content
SPECIFICTION
Get listed

Red Hat Trusted Artifact Signer vs SignServer

Red Hat Trusted Artifact Signer

access.redhat.com

SignServer

signserver.org

Side by side

FigureRed Hat Trusted Artifact SignerSignServer
Price from—Free
Free plan—Yes
Free trial—Yes
Open source——
WebYesYes
WindowsYesYes
macOSYesYes
LinuxYesYes
API—Yes
Self-hostedYesYes
Plans published12
Spec score · Code Signing Software7.5 (#18)7.7 (#12)
Founded19932005
IntegrationsRed Hat lists Podman, Quay, Ansible, Red Hat Advanced Cluster Security, StoneSoup/HACBS, and Red Hat Trusted Content among products adopting or integrating Sigstore.The comparison lists integration and secure automatic certificate renewal with CA/EJBCA, and the maker describes integration with third-party applications through standard interfaces.
PurposeRHTAS simplifies cryptographic signing and verification of software artifacts, including container images, binaries, and Git commits.SignServer is a server-side platform for digitally signing code, documents, and timestamps.

Plans

Red Hat Trusted Artifact Signer

  • Red Hat Trusted Artifact SignerPriced on request

Red Hat Trusted Artifact Signer pricing →

SignServer

  • SignServer CommunityFree
  • SignServer Enterprise Cloud trialFree

SignServer pricing →

In their own words

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.

Visit access.redhat.com

SignServer

SignServer is a server-side platform that centrally manages signing keys and digitally signs code, documents, and timestamps. One installation can serve several signing workflows, including containers, firmware, IoT, and DevOps use cases. It can connect to CI/CD pipelines, firmware build processes, document workflow engines, identity platforms, and other applications through standard interfaces. Community is available as a Docker container, Helm chart, source code, or GitHub release, and is also listed on SourceForge. Its interfaces include SOAP, HTTP, REST, and the SignClient command-line interface, though Community REST lacks some endpoints. Community is released under LGPL V2.1 or later and is intended for learning, testing, and prototyping rather than production. The maker says it lacks production capabilities such as audit, compliance, SLA, high availability, and security features. Enterprise adds professional support with an SLA, security updates, and maintenance. The Community plan is free; the Enterprise Cloud trial is free for 30 days through AWS or Azure marketplaces. The maker recommends Hardware Security Modules for signing-key storage.

Visit signserver.org