← Directory

SignServer CE

SignServer CE is an open-source, PKI-based signing solution for digitally signing code, documents, timestamps, and artifacts.

  • Security
  • Tools & Utilities
SignServer CE is an open-source, PKI-based signing solution for digitally signing code, documents, timestamps, and artifacts. It provides self-hosted signing infrastructure for development and non-production use, offering a free alternative to commercial signing platforms.

Platform availability

Available on 2 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

67/100 Good

Maintained
86last commit 50 days ago
Popular
53436 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 4 days ago

GitHub stars
436
Open issues
8
Last commit
2026-08-26
Latest release
v7.7.1
License
LGPL-2.1
Activity
stale

Checked 6 days ago - source: GitHub (Keyfactor/signserver-ce)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start WildFly before running SignServer Unzip the WildFly download, go into its folder, and run ./bin/standalone.sh so the Java app server is running. SignServer needs this server to start and handle its requests. source
  • Add a token and worker before signing Create a crypto token (a container for signing keys) and a worker (the service that does signing) using the sample properties files, then reload SignServer. Without them, you have no key or service ready to sign documents. source
  • Allow port 8080 for the API if needed The examples use http://localhost:8080 to sign or validate data, so open port 8080 if another device or app must call SignServer. If it is blocked, remote calls cannot reach the service. source

Fetched 9 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I configure a trusted CA certificate for SignServer in Docker?

Save the certificate in the current directory as TrustedCA.pem or replace the path with the file path to your certificate. The server certificate is generated automatically and self-signed, with its fingerprint shown in the log output.

What license applies to SignServer CE?

SignServer CE is LGPL-licensed.

Which product does SignServer CE form a subset of?

It is an open-source subset of SignServer Enterprise.

Answers sourced from github.com, www.reddit.com

Community

Collected 11 days ago - public community threads