DocuSeal

Last reviewed Aug 26, 2026 · 749 words

Signatures collected with a self-hosted DocuSeal are as valid as DocuSign's in most jurisdictions, because e-signature law (ESIGN in the US, the basic tier of eIDAS in the EU) cares about intent, consent and an audit trail, not about which company hosted the form. DocuSeal gives you the trail: each completed PDF carries a log with timestamps, IP addresses and email verification, and the file is signed with a PDF certificate, DocuSeal's own by default. What it does not give you is DocuSign's brand recognition when a counterparty's lawyer asks what this is. So the honest framing is: right for leases, contractor agreements, NDAs, consent forms and everything internal; think twice before it carries a deal you expect to litigate.

One container, and Postgres if you plan to keep it

services:
  docuseal:
    image: docuseal/docuseal
    ports:
      - "3000:3000"
    environment:
      - DATABASE_URL=postgresql://docuseal:change-me@db/docuseal
      - SECRET_KEY_BASE=a-64-char-random-hex-string
    volumes:
      - ./data:/data
    restart: unless-stopped
  db:
    image: postgres:16
    environment:
      - POSTGRES_USER=docuseal
      - POSTGRES_PASSWORD=change-me
      - POSTGRES_DB=docuseal
    volumes:
      - ./pgdata:/var/lib/postgresql/data

Leave DATABASE_URL out and DocuSeal falls back to SQLite in /data, which is fine for a household and wrong for a business, since uploaded PDFs, signed output and the audit trail all live in that volume. The first visit to port 3000 creates the admin account. Two settings are not optional: a public HTTPS URL behind a reverse proxy, because signing links go out by email and must resolve from a stranger's phone, and SMTP, configured in the app settings, because a signing platform that cannot send email is a PDF viewer. The 1 GB RAM figure is realistic for a Rails app that renders PDFs; it will not be happy on less.

Templates are the product

Upload a PDF (or a DOCX, which it converts), drag fields onto it: signature, initials, date, text, checkbox, select, file upload and a few more, each assigned to a named party. Save that as a template and every future send is "pick template, enter two email addresses, send". Signers get a link, sign in the browser (draw, type or upload an image), and everyone receives the completed PDF plus the audit log. Multi-party sequencing works: party one must sign before party two is emailed. The signing page is nicer than the incumbents', which matters because your signers are people who never asked to use your software. For structured workflows, the API (token in the settings) creates submissions from a template with pre-filled fields, and webhooks fire on view, start and completion, so an n8n flow or your own code can file the result into Paperless-ngx the moment it lands.

Community versus Pro, honestly

The AGPL community edition has no cap on documents, templates or signers. Pro, a paid licence, adds roughly this at last check: your logo and colours on emails and the signing page, the embeddable builder and signing form for putting the whole flow inside your own app, conditional fields, SMS verification and a few workflow extras; the current split is on the pricing page. For a small business sending contracts by email, community is complete. If you are embedding signing into a product you sell, budget for Pro, and remember the AGPL means a modified DocuSeal offered as a service must publish its source; the licence primer explains why that matters more in this category than most.

Against Documenso and OpenSign

Documenso is the same idea in TypeScript, with a lot of attention on the signing-certificate story and eIDAS-grade signatures; OpenSign is the more feature-crowded of the three. DocuSeal wins on time-to-first-signature and on an API that is usable on day one; Documenso wins if you care about bringing your own certificate. Any of the three replaces DocuSign for a small business; the differences are ergonomics, and DocuSeal's are the best I have used.

What I'd do

DocuSeal on Postgres behind a real domain with TLS, SMTP through whatever relay already sends your other mail, community edition, nightly backup of both the volume and the database, because the signed PDFs are the legal record and losing them is losing the contract. Build one template per recurring agreement, wire the completion webhook into Paperless-ngx, and stop paying per envelope. Move to Pro only when you need signing inside your own product.