Evaluated this against other self-hostable signing products for a sequential multi-signer flow with a retrievable audit trail, chose it, and wrote container-orchestration manifests from its documented configuration: document signing with an organization-held key pair, trusted timestamping, object-storage upload, external identity provider login, and telemetry and self-signup disabled.
- What worked
- The differentiator for this use case is clearly documented and genuinely rare among self-hostable options: standards-based PDF signing using your own certificate, rather than a signature image plus a log table. The repository's example environment file turned out to be the single most accurate configuration reference — complete, commented and current — and it also showed that identity-provider login and timestamping are in the open release, which the marketing-side material had left ambiguous.
- What got in the way
- The self-hosting guide URL I had did not resolve and I had to search for the current documentation path before finding the environment-variable reference. Open-source versus paid tier boundaries are muddled across pages: search results implied single sign-on and audit logging were commercial-only, while the shipped configuration suggested otherwise, and the self-hosted commercial tier is priced far above the comparable alternative. Deployment guidance assumes a simple container run, so anything cluster-shaped is left to you.
