TiloBox
Back to directory
OpenSign project preview

OpenSign

Open-source, self-hosted electronic document signing platform alternative to DocuSign.

LicenseAGPL-3.0
GitHub stars6.9k
Last commit1 weeks ago
Tags6 topics
CompliancePdfSelf HostedLegalE SignatureDocument Signing
Overview

Why consider OpenSign?

OpenSign is an open-source e-signature platform. It sends documents for digital signature collection, tracks signing progress, and stores completed agreements securely.

Guided learning

Learn OpenSign by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

3 min read 10 sections
In this guide10 sections

What is OpenSign?

OpenSign is an open-source, self-hosted electronic document signing (e-signature) platform developed with Node.js, React, and MongoDB. It operates as a private, data-sovereign alternative to expensive commercial e-signature platforms like DocuSign, HelloSign (Dropbox Sign), and PandaDoc.

OpenSign enables businesses to send PDF contracts, NDAs, employment agreements, and legal documents to recipients for legally binding electronic signature collection. Signers complete the process from any device without downloading software, while senders track signing progress in real time and receive completed documents stored securely.

Who Is It For?

  • Legal & Compliance Teams: Executing contracts, NDAs, and compliance attestations with full audit trails.
  • HR Departments: Collecting employee offer letter signatures, policy acknowledgments, and onboarding agreements.
  • SaaS Businesses: Embedding automated contract signing workflows into customer onboarding and subscription upgrade processes.

Key Features

  • Drag-and-drop signature field placement: Assign signature, initials, date, and text fields to specific PDF page locations.
  • Multi-party signing workflows: Route documents through sequential or parallel signing chains.
  • Detailed audit trail: Capture timestamped signer emails, IP addresses, device fingerprints, and signature events.
  • Automated email notifications: Remind unsigned recipients and deliver completed documents upon final signature.
  • API-first design: Integrate document sending and signing status checks directly into internal business applications.

Deploying OpenSign with Docker Compose

yaml
1version: '3.7'
2
3services:
4 mongo:
5 image: mongo:6-jammy
6 container_name: opensign_mongo
7 restart: unless-stopped
8 volumes:
9 - ./mongo_data:/data/db
10
11 opensign:
12 image: opensignlabs/opensign:latest
13 container_name: opensign_app
14 restart: unless-stopped
15 ports:
16 - "3000:3000"
17 environment:
18 - DATABASE_URL=mongodb://mongo:27017/opensigndb
19 - NODE_ENV=production
20 - JWT_SECRET=generate_a_secure_random_jwt_secret
21 - APP_URL=http://localhost:3000
22 depends_on:
23 - mongo

Start the instance:

bash
1docker compose up -d

Open http://localhost:3000 in your browser to register your OpenSign administrator account.

Practical Use Cases

1. Automated Client Contract Execution

A law firm uploads an NDA PDF, places signature fields for two parties, sends the document, and receives a completed, countersigned agreement automatically.

2. HR Onboarding Agreement Collection

An HR team creates offer letter templates; when candidates accept, OpenSign automatically routes acceptance letters and policy acknowledgments for digital signature.

3. API-Driven Subscription Upgrade Agreements

A SaaS company integrates OpenSign API into its upgrade flow, automatically sending enterprise license agreements to customers who upgrade their subscription tier.

Troubleshooting and Limitations

  • PDF Rendering Quality: OpenSign processes PDFs client-side; ensure uploaded PDFs are not password-protected, as encrypted documents prevent field positioning from rendering correctly.
  • Email Delivery for Signing Invites: Configure SMTP settings in the OpenSign environment variables to ensure signing invitation emails reach recipients reliably.

Official Resources

Related tools

More options with a similar category or technology profile.

OpenSign FAQs

OpenSign is listed as a Productivity tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository and official website for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

OpenSign is listed under the AGPL-3.0 license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

OpenSign is listed as an alternative to HelloSign. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.