Trusted Signatures + Documenso Integration

Overview

Documenso is a free, open-source DocuSign alternative that supports eSigning, templates, and document workflows. For organizations that are (or considering) self-hosting documenso to manage their own workflow, Trusted Signatures maintains a fork that integrates seamlessly with Publisher - our PDF sealing service to provide Adobe-trusted signatures. Below are details and instructions for this integration. Note: by default, documents sealed with our Publisher service complay with EU Advanced certification requirements

Coming Soon

Target Audience

This guide is for developers and system administrators with experience deploying web applications using Docker or manual installation methods. You should be comfortable with:

• Docker containerization and deployment
• Environment variable configuration
• Database setup and management
• Basic command-line operations
• Web application deployment concepts

Trusted Signatures Fork

We maintain an enhanced fork of Documenso with built-in Trusted Signatures integration:

• GitHub Repository: trusted-signatures/documenso
• Docker Image: [trustedsignatures/documenso]
• Release Cycle: Each Documenso release is matched with a corresponding release tagged with a -ts.1 suffix (e.g., v1.13.2-ts.1 corresponds to Documenso v1.13.2)

This fork includes pre-configured integration with Trusted Signatures, eliminating the need for custom modifications.

Deployment Options

Option 1: Docker Deployment (Recommended)

Use our pre-built Docker image for the fastest deployment:

1
2
3

docker pull trustedsignatures/documenso:latest
# Or use a specific version
docker pull trustedsignatures/documenso:v1.13.2-ts.1

Refer to the Documenso Documentation for specifics. The only thing you need to change is the image name (use trustedsignatures/documenso), and configure the environment variables below.

Option 2: Manual Deployment

Clone and build from our GitHub fork:

1
2

git clone https://github.com/trusted-signatures/documenso.git
cd documenso

From there the standard Documenso Manual Deployment Procedures apply.

Prerequisites

• Active Trusted Signatures account
• Valid API key from your Trusted Signatures dashboard
• Basic Documenso deployment knowledge

Configuration

Add these environment variables to your deployment configuration:

You can use a test API key to try it out for free. The documents will be sealed but the test certificate will not produce a green check in Adobe Acrobat.

To get the green check, subscribe to our Publisher and create a new API key using the production signing key. Configure Documenso to use the new API Key and API Key ID. Then documents will get the green check in adobe acrobat and will show that they’ve been signed with the Trusted Signatures certificate.

To get the green check sealed with your own certificate, subscribe to our Publisher Identity product. When your certificate is issued you can create an API Key using that certificate (which we host for you in our secure environment).

Testing Your Integration

1. Send a test document through your Documenso instance
2. Verify the signature:
   • With test API keys: Document will be signed but certificate won’t be recognized
   • With production AATL/eIDAS keys: Document should display a green check with a message indicating all signatures are valid.

Expected Results:

• Test keys: Document sealed but no trust indicator
• Production keys: Green checkmark with “All signatures are valid” message in Adobe Acrobat
• Identity keys: Green checkmark showing your organization name as the signer

Troubleshooting

Common Issues:

• “Signing failed”: Verify API key format (hexadecimal) and key ID are correct
• No seal applied: Check NEXT_PRIVATE_SIGNING_TRANSPORT=trusted-signatures is set
• Database errors: Ensure Documenso’s standard database requirements are met

Support

For deployment issues or integration questions, contact our support team. Include:

• Documenso version and deployment method
• Environment variable configuration (redact actual API keys)
• Error messages or logs