Open Source DocuSign Alternatives

DocuSeal handles digital document signing and processing. You build a PDF form once, send it out, and signers fill and sign it in a browser on a phone or a laptop, which retires the print, sign, scan and email cycle entirely.

The form builder is WYSIWYG and mobile-optimized on the signing side. Completed documents receive an automatic PDF eSignature, and signatures can be verified afterwards. Files are stored on disk or in AWS S3, Google Storage or Azure Cloud, and notification emails go out over your own SMTP server.

The open source edition covers the whole signing loop.

• Field types: twelve of them, signature, date, file and checkbox among others, placed visually on the page.
• Submitter flow: several people can be routed through a single document in turn.
• Localisation: seven interface languages, with signing available in fourteen.
• Integrations: an API and webhooks connect it to whatever system creates or consumes the documents.
• User management: accounts for the people who build templates and send them out.

Deployment is a single Docker command backed by SQLite, or PostgreSQL and MySQL through a database URL, and a compose file issues certificates through Caddy for a custom domain. One-click templates exist for Heroku, Railway, DigitalOcean and Render. Paid features add white-labelling, user roles, SSO with SAML, conditional fields, bulk send from spreadsheets and embedded signing components.

Signing a document digitally introduces a third party to every signature: the provider of the signing tool. Documenso exists so that party can be one you host, read and audit yourself, which is the argument behind the whole project.

It is a TypeScript application on React Router v7 with a Hono server, Prisma over Postgres and tRPC for the API. Signatures are produced with libpdf, documents are rendered with pdf.js and manipulated with pdf-lib, and the interface uses Tailwind CSS with shadcn and Radix components.

Around that core sit the pieces you need to actually operate it.

• Deployment choice: Docker, Docker Compose, Railway, Kubernetes or a manual install, with official images on Docker Hub and the GitHub registry.
• One-click deploys: Railway, Render, Koyeb and Elestio buttons for people who would rather not touch infrastructure.
• Local quickstart: one command spins up Postgres and a mail catcher in Docker, another starts the app.
• Internationalisation: Lingui drives translations, with react-email behind the transactional templates.
• Testing: Playwright covers end-to-end runs, with Biome for linting and formatting.

Local development needs Node.js 24 or newer and a Postgres database, with Docker optional but assumed by the quickstart. External pull requests are paused, so the project asks for detailed issues instead, and an enterprise plan is offered to organizations that need more flexibility and control.

Routine paperwork gets expensive when every envelope carries a fee. OpenSign is a document e-signing platform built as an open alternative to DocuSign, PandaDoc, SignNow, Adobe Sign and HelloSign, with the stated goal of making signing accessible to everyone.

Documents are signed in the browser through a signing pad that accepts hand drawn signatures, uploaded images, typed signatures and saved ones. Encryption protects the PDFs, and the app pairs a sign yourself path for your own documents with a request flow for everyone else.

Most of the product sits in the signing workflow.

• Multi-signer support: invites several signers, shares signing links and can enforce a signing order.
• Guest verification: sends a one-time code by email that a guest must enter before signing.
• Expiry and rejection: closes a document after a set number of days and lets a signer decline with a reason returned to the sender.
• Templates: store reusable PDF documents so repeat paperwork is not rebuilt each time.
• Audit trails: log activity with timestamps, IP addresses and email addresses, and produce a completion certificate when a document closes.
• OpenSign Drive: keeps documents in one vault for storing, organizing, sharing and archiving.

Self-hosting runs through official Docker images or a DigitalOcean deploy under the AGPL-3 license; note that the default MongoDB instance is not persistent, so supply your own connection string to keep data across restarts. An API with keys generated in the app, integrations with cloud storage and CRMs, and a Zapier connection tie it into existing systems.

Wraft treats a business document as something with a lifecycle rather than a file, covering drafting, collaboration, approval, signature and long-term storage in one platform. It removes the sprawl where a contract starts in a word processor, gets approved over email and ends up in a folder nobody can search.

Content is authored in open formats, markdown and JSON, so documents stay readable and portable whatever happens to the software that produced them. Generation runs through Pandoc, which converts that markdown into PDF and other formats, and the output is customized with LaTeX or Typst and driven from API endpoints inside an existing workflow.

The platform reaches past authoring into the work that surrounds a contract.

• Contract repository: every contract document is stored and organized centrally instead of per team.
• E-signature: documents are signed through built-in signing and approval workflows.
• Workflow rules: approvals and reminders run on rules a team configures without writing code.
• Structured storage: search and retrieval work on structured documents backed by object storage, not a flat pile of files.
• Integrations: REST APIs, single sign-on and webhooks connect Wraft to the systems a team already runs.

Wraft is self-hostable under AGPLv3 with deployment guides for your own servers, and a hosted cloud account exists for teams that would rather not run one. The product is in private beta and reusable smart blocks are still listed as an upcoming feature, so early adopters should expect the surface to keep moving.