How to self-host Documenso in 2026: DocuSign alternative

What Documenso is and why people self-host it

Documenso is open-source document signing — the closest thing to DocuSign with the source on GitHub. 12,000+ stars in 2026 and climbing fast (it was under 5K stars in early 2024). PDF document signing, ordered or parallel signing flows, audit trails, digital signature certificates, templates for repeated workflows, embeddable signing into your own product.

Three reasons to self-host instead of using DocuSign or Documenso Cloud.

DocuSign's per-send and per-user math. DocuSign Personal is $10/month for 5 sends. Standard is $25/user/month. Business Pro $40/user/month with API access. A small business signing 20 contracts a month with 3 sales reps lands at $75–120/month minimum.

Self-hosted is unlimited. Free for unlimited senders, unlimited documents, unlimited recipients. Pay only for the server.

Document privacy. Signed contracts often include sensitive terms — acquisition deals, employment agreements, NDAs. Self-hosting means these documents live on your server, not in DocuSign's storage.

Three ways to self-host Documenso

Path A: Docker Compose on your own VPS

Documenso ships a clean docker-compose.yml. Spin up a 2 GB RAM VPS ($10/month), install Docker, drop the Compose file (Documenso server + PostgreSQL), configure environment variables, set up nginx + free SSL setup for SSL.

Realistic time-to-first-deploy: 1–2 hours plus generating the signing certificate.

Path B: Managed Docker host (Coolify, Dokploy)

Both platforms have Documenso as a one-click template. SSL, Postgres, reverse proxy all wired up.

Path C: livemy.app one-click deploy

Pick the Documenso template, point your domain, ship. livemy.app provisions PostgreSQL, sets up persistent storage for uploaded documents, daily backups for both.

From zero to Documenso on livemy.app (about 5 minutes including signing certificate)

Step 1: Sign up at livemy.app, pick Maker

Go to livemy.app, Start free, pick Maker ($20/month). Always-on is important — signing requests time out if recipients try to access the document while the server is asleep.

Step 2: Deploy from the Documenso template

In the dashboard: New project → Template → Documenso. livemy.app pulls the official image and provisions PostgreSQL.

Step 3: Generate a signing certificate

This is the part most other self-host guides skip. For documents to have proper digital signatures (not just an image of a signature, but an actual cryptographically signed PDF), Documenso needs a signing certificate.

Generate a self-signed certificate for testing:

• openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -sha256 -days 365 -nodes

• Combine into a PKCS#12 file: openssl pkcs12 -export -out cert.p12 -inkey key.pem -in cert.pem

• Upload the cert.p12 file to Documenso's configured cert directory

For production-grade legally binding signatures, buy a certificate from a trusted CA (DigiCert, GlobalSign, etc.) instead of self-signing. The technical setup is identical — just the cert provenance differs.

Step 4: Configure environment variables

Under Project Settings → Environment Variables:

• NEXTAUTH_URL — your full public URL with https://

• NEXTAUTH_SECRET — a 32+ character random string

• NEXT_PRIVATE_DATABASE_URL — PostgreSQL connection (auto-populated)

• NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH — path to the cert.p12 you uploaded

• NEXT_PRIVATE_SIGNING_PASSPHRASE — the passphrase you set on the cert

Plus SMTP variables for sending signing request emails (Mailgun, Postmark, Resend).

Step 5: Deploy, create admin, test a signing flow

Typical deploy time: 3–5 minutes. When live, visit the URL, create the owner account. Upload a test PDF, add a recipient (use a personal email of yours), send for signature. Check email, complete the signing flow.

Verify by opening the signed PDF in Adobe Acrobat — it should show a digital signature in the signature panel.

Step 6: Point your domain

Add custom domain, update DNS, wait for SSL. Update NEXTAUTH_URL to the final domain and redeploy. Test one more signing flow to confirm signing request emails contain the right URL.

Five things that quietly break self-hosted Documenso

1. Signing certificate not configured — documents "signed" without real signatures

If you skip the certificate step, Documenso still works — the UI flow completes, the recipient "signs" with a drawn signature image, and you get a PDF back. But the resulting PDF has no cryptographic signature, just an image, and won't pass any audit that checks for real digital signatures.

Fix. Don't skip Step 3. Generate (or buy) a signing certificate before sending any real contracts. Open one signed PDF in Adobe Acrobat to verify the signature panel shows a real digital signature.

2. NEXTAUTH_URL mismatch breaks signing links

Documenso emails signing request links to recipients. The links are built from NEXTAUTH_URL. Mismatch — still pointing at the temporary subdomain after domain change — and every signing link goes to the wrong host.

Fix. Update NEXTAUTH_URL after every domain change. Redeploy. Test one signing flow with a personal email.

3. SMTP misconfigured — signing requests never arrive

Without working SMTP, recipients never get the email with the signing link. The document sits in Documenso forever, recipient confused why they haven't received anything.

Fix. Test SMTP early. Send a test signing request to yourself before sending one to a real contract recipient.

4. PDF size limit on uploads

Default upload size limits on Documenso (and on the nginx layer if you have one) are conservative — large multi-page contracts with embedded images can exceed defaults.

Fix. Bump NEXT_PRIVATE_MAX_DOCUMENT_SIZE on Documenso. On a manual nginx setup, also bump client_max_body_size. livemy.app handles this automatically.

5. Backups must cover signed documents AND database

Documenso stores document metadata, signing audit trail, and user accounts in PostgreSQL; the actual PDF files live on disk. Losing either alone is a partial restore: you have the contracts but no audit trail, or the audit trail but no PDFs.

Fix. Snapshot both daily. livemy.app's $5/month backups add-on covers the whole Documenso project. For manual setups, pg_dump + rsync the document volume to off-server storage.

Cost: DocuSign vs self-hosted Documenso

Real numbers for a small business with 3 sales reps sending 20 contracts per month.

DocuSign Standard: $25/user × 3 = $75/month, but contract send caps may push you to Business Pro.

DocuSign Business Pro: $40/user × 3 = $120/month

Self-hosted on a $10 VPS: $10/month for unlimited users and sends.

Self-hosted on livemy.app: $25/month flat ($20 Maker + $5 backups). Unlimited users and sends.

For a 3-rep team, livemy.app saves $50–95/month. Annual: $600–1,140. Self-hosting pays for itself in the first month and keeps paying.

FAQ

Is self-hosted Documenso legally binding?

Yes — if you set up the signing certificate correctly. Documenso supports both basic e-signatures (a drawn signature image) and qualified electronic signatures backed by a real digital certificate. The latter is what gives the signed PDF cryptographic integrity that passes audit. Self-signed certs work for internal use; for legally critical contracts, buy a certificate from a trusted CA.

Can I migrate from DocuSign?

No direct importer exists — DocuSign doesn't export templates or contracts in a Documenso-compatible format. The practical migration is: download your past signed contracts as PDFs from DocuSign (they're yours, you can keep them), then start new contracts on Documenso going forward. Templates rebuild quickly.

Does Documenso support API access?

Yes — REST API for sending signing requests, retrieving signed documents, managing templates programmatically. DocuSign gates API access behind their Business Pro tier ($40/user/month); Documenso self-hosted includes the API at no cost.

Can multiple people in my team send documents?

Yes — unlimited team members on a single self-hosted instance. Each user has their own login, can send documents, can have templates. The flat self-hosting cost covers any team size.

What about audit trails?

Documenso records every event in the document lifecycle — sent, viewed, signed, with timestamps and IP addresses. The audit trail is embedded in the signed PDF and stored in the database, exportable for compliance.

Will it auto-update?

On livemy.app, opt-in auto-update or pin to a specific version. Documenso ships frequent updates — the project is moving fast in 2025–2026. For document signing, you generally want to stay current for security patches.

Self-host Documenso — unlimited contracts, flat $25/month

If you're paying DocuSign per user or per send, Documenso replaces it at a flat self-hosted cost with unlimited team members and unlimited sends. The cheapest path is a $10 VPS. The fastest path is livemy.app's Documenso template — just budget the 30 minutes to generate the signing certificate.

→ Start free on livemy.app · Documenso template with Postgres provisioned, custom domain, SSL, backups, all on Maker at $20/month flat.

Stuck on the signing certificate setup or migrating templates from DocuSign? Email hello@livemy.app. Replies inside one business day.

Read next

• How to self-host Cal.com in 2026: own your scheduling

• How to self-host Vaultwarden in 2026: Bitwarden alternative

• How to self-host n8n in 2026: the complete guide

• How to self-host Outline wiki in 2026: Notion alternative