Self-Host Docuseal: Open Source Document Signing 2026

TL;DR

Docuseal (AGPL 3.0, ~6K GitHub stars, Ruby) is a self-hosted document signing platform. Upload a PDF, drag-and-drop signature fields onto it, send to signers, and collect legally binding signatures — all from your own server. DocuSign charges $10-$25/month per user; HelloSign charges $15/month. Docuseal gives you unlimited signatures, unlimited templates, and unlimited users for free.

Key Takeaways

• Docuseal: AGPL 3.0, ~6K stars, Ruby — full document signing with template builder
• Template builder: Drag-and-drop field placement — signature, date, text, checkbox
• Multiple signers: Routing order, sequential or parallel signing
• REST API: Programmatic document generation and signing from any app
• Mobile friendly: Signers can sign on any device — no app install required
• Audit trail: Complete signing history with timestamps and IP addresses

---

Docuseal vs DocuSign vs Documenso

Feature	Docuseal	DocuSign	Documenso
Price	Free (self-host)	$10-25/user/mo	Free (self-host)
Template builder	Drag-and-drop	Drag-and-drop	Basic
Multi-signer	Yes (ordered)	Yes	Yes
API	REST	REST	REST
Branding	Customizable	Limited (paid)	Customizable
Audit trail	Yes	Yes	Yes
Self-hosted	Yes	No	Yes
Stars	~6K	N/A	~8K

---

Part 1: Docker Setup

# docker-compose.yml
services:
  docuseal:
    image: docuseal/docuseal:latest
    container_name: docuseal
    restart: unless-stopped
    ports:
      - "3000:3000"
    volumes:
      - docuseal_data:/data
    environment:
      DATABASE_URL: "sqlite3:///data/docuseal.db"
      # Or use PostgreSQL:
      # DATABASE_URL: "postgresql://docuseal:password@db:5432/docuseal"
      SECRET_KEY_BASE: "${SECRET_KEY}"   # openssl rand -hex 64

volumes:
  docuseal_data:

echo "SECRET_KEY=$(openssl rand -hex 64)" >> .env
docker compose up -d

Visit http://your-server:3000 → create your admin account.

---

Part 2: HTTPS with Caddy

sign.yourdomain.com {
    reverse_proxy localhost:3000
}

---

Part 3: Creating Templates

Upload a document

1. Templates → + New Template
2. Upload PDF (contract, NDA, agreement, offer letter, etc.)
3. The PDF pages appear in the editor

Add signature fields

Drag fields onto the PDF:

Field Type	Description
Signature	Drawn or typed signature
Initials	Short initials field
Date	Auto-filled signing date
Text	Free text input (name, address, etc.)
Checkbox	Agreement checkboxes
Select	Dropdown menu
Image	Upload an image (ID, photo)
Stamp	Company stamp/seal

Multi-signer templates

1. Add signers: Client, Company Representative, Witness
2. Assign fields to specific signers (color-coded)
3. Set signing order: sequential (client first → company second) or parallel

Template variables

Use {{variables}} in templates that get filled programmatically:

Client Name: {{client_name}}
Date: {{contract_date}}
Amount: {{total_amount}}

---

Part 4: Sending Documents for Signing

Via web UI

1. Templates → Select template → Create submission
2. Enter signer details:
   • Name: John Smith
   • Email: john@example.com
3. Send → signer receives email with signing link
4. Signer opens link → reviews document → signs → done

Signing experience

Signers see:

1. Document preview with highlighted fields
2. Click each field to fill it
3. Draw signature (mouse, touch, or type)
4. Submit → PDF sealed with signatures
5. All parties receive signed copy via email

---

Part 5: REST API

Create and send via API

TOKEN="your-api-token"  # Settings → API
BASE="https://sign.yourdomain.com"

# List templates:
curl "$BASE/api/templates" \
  -H "X-Auth-Token: $TOKEN" | jq '.[].name'

# Create a submission (send for signing):
curl -X POST "$BASE/api/submissions" \
  -H "X-Auth-Token: $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "template_id": 1,
    "send_email": true,
    "submitters": [
      {
        "role": "Client",
        "email": "client@example.com",
        "name": "John Smith",
        "fields": [
          {"name": "client_name", "default_value": "John Smith"},
          {"name": "contract_date", "default_value": "2026-03-09"}
        ]
      },
      {
        "role": "Company",
        "email": "ceo@company.com",
        "name": "Jane Doe"
      }
    ]
  }'

# Check submission status:
curl "$BASE/api/submissions/1" \
  -H "X-Auth-Token: $TOKEN" | jq '{status: .status, signers: [.submitters[].status]}'

# Download signed PDF:
curl "$BASE/api/submissions/1/documents/1" \
  -H "X-Auth-Token: $TOKEN" \
  -o signed-contract.pdf

Webhook notifications

# Configure webhook to get notified when documents are signed:
# Settings → Webhooks → Add
# URL: https://yourapp.com/webhook/docuseal
# Events: submission.completed, submission.created

# Webhook payload:
{
  "event_type": "submission.completed",
  "data": {
    "id": 1,
    "template_id": 1,
    "status": "completed",
    "submitters": [
      {"email": "client@example.com", "status": "completed", "signed_at": "2026-03-09T15:30:00Z"}
    ]
  }
}

---

Part 6: Branding and Customization

Company branding

Settings → Branding:
  - Logo: upload your company logo
  - Company name: appears on signing pages
  - Primary color: match your brand
  - Email templates: customize notification emails

Custom signing page

The signing page shows:

• Your logo and company name
• The document
• A clean, distraction-free interface
• No Docuseal branding (on self-hosted)

---

Part 7: Use Cases

Employment contracts

1. Create template from your standard employment agreement
2. Add fields: employee name, position, salary, start date, signature
3. API integration: HR system auto-sends when new hire is confirmed

NDAs

1. Upload NDA PDF
2. Fields: company name, individual name, date, signature
3. Send via API before sharing confidential docs

Invoices and Purchase Orders

1. Create invoice template
2. Fields: line items (via variables), total, approval signature
3. Integration with accounting system

Client proposals

1. Upload proposal PDF
2. Fields: scope, timeline, budget, acceptance signature
3. Track acceptance status via API

---

Part 8: Audit Trail

Every document signing includes a complete audit trail:

• Created: timestamp, created by
• Sent: email sent to each signer
• Viewed: when each signer opened the document
• Signed: timestamp, IP address, user agent for each signature
• Completed: final document sealed

Access via:

Submissions → Select submission → Audit Log

Or via API:

curl "$BASE/api/submissions/1" \
  -H "X-Auth-Token: $TOKEN" | jq '.audit_log'

---

Maintenance

# Update:
docker compose pull
docker compose up -d

# Backup:
tar -czf docuseal-backup-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect docuseal_docuseal_data --format '{{.Mountpoint}}')

# Logs:
docker compose logs -f docuseal

Why Self-Host Docuseal?

The case for self-hosting Docuseal comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Docuseal means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Docuseal, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Docuseal headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Docuseal data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Docuseal without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Docuseal's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Docuseal backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Docuseal's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Docuseal's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Docuseal's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Docuseal's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f docuseal

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Docuseal's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

1. Confirm the container is running: docker compose ps
2. Test locally on the server: curl -I http://localhost:PORT
3. If local access works but external doesn't, check your firewall: ufw status
4. If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats docuseal. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Docuseal Updated

Docuseal follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Docuseal is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

---

See all open source business tools at OSSAlt.com/categories/business.