Documenso
Open-source DocuSign alternative for e-signatures, self-hostable with a real audit trail and a signing API, built on a modern TypeScript stack.
The most credible open-source DocuSign alternative in 2026, a clean signing UI on a modern stack with a real audit trail and no document caps when you self-host. The catch: getting legally valid signatures on your own server means wrestling a signing certificate, and the enterprise pieces (SSO, 21 CFR Part 11, white-label embed) live behind a paid Enterprise Edition.
Teams that want e-signatures on their own infrastructure with a timestamped audit trail and full data ownership, plus builders who want a signing API and embedded flows without DocuSign per-signature pricing.
Self-hosting is genuine ops work, the signing certificate is the step that decides whether your PDFs are legally valid, and SSO, passkey and 2FA reauth, and 21 CFR Part 11 compliance are commercial Enterprise Edition.
Alive and shipping weekly with a funded company behind it, so support is real but tilted toward paid plans. Small teams that want zero ops usually land on the hosted plans, free up to 250 dollars a month.
What it does
- Send PDFs for e-signature with drawn, typed, or uploaded signatures, plus fields for text, dates, checkboxes, and initials
- Reusable templates and direct signing links, so recurring contracts go out without rebuilding the document each time
- Multi-recipient workflows with signing order, so a document routes through signers in sequence
- Every completed document gets a timestamped audit trail and a cryptographic signing certificate embedded in the PDF
- REST API, webhooks, and embedded signing to wire signatures into your own product or automation
- Full self-host under AGPL with no document, recipient, or user caps on the free build, so signed contracts stay on your infrastructure
What it can’t do
- Sign anything on self-host until you generate and mount a signing certificate (cert.p12); without it the app runs but signing fails
- Give you SSO, an organisation auth portal, passkey and 2FA reauth, or 21 CFR Part 11 on the free build; those are Enterprise Edition commercial
- Match DocuSign on bulk send, deep template libraries, and complex conditional routing yet
- Accept your pull requests; the team paused external PRs in 2026, so contribution runs through detailed issues and a small invited group
- Hand you polished self-host docs; hands-on setup help largely assumes a paid plan, and the community calls the docs thin
Pros & cons
- Genuinely clean, fast signing UI that people compare favorably to DocuSign, on a modern TypeScript stack
- Self-hosted build is full AGPL with no document, recipient, or user caps, so signed contracts and their data stay on your own servers
- Real audit trail and an embedded signing certificate, the compliance backbone e-signatures need to hold up
- Ships constantly, weekly releases with v2.17 in August 2026, backed by a funded company, so the bus factor is not one maintainer
- REST API, webhooks, templates, and embedded signing make it a signing layer you can build your own product on
- Signing-certificate setup on self-host trips up new users; get it wrong and documents sign without a valid cert
- The features enterprises need, SSO auth portal, passkey and 2FA reauth, 21 CFR Part 11, white-label embed, sit behind the commercial Enterprise Edition
- Self-host documentation is thin and hands-on support largely assumes a paid plan
- External pull requests are paused, so you cannot upstream fixes the usual open-source way
- Bulk send and the deepest template and routing features still trail DocuSign
What the community says
Document signing is one of those workflows that should be simple, fast, and trustworthy but too often it feels locked inside expensive, rigid tools. Documenso feels like a much-needed rethink: open source, clean to use, flexible enough to self-host or use hosted, and built with APIs, templates, direct links, and team workflows in mind.
We use it for all our docs, great tool. The UX is a bit fidgety but looks like it is much better now in 2.0.
Watch out. Documenso, even when you host it on your own, automatically adds two users that cannot be deleted. If you delete them, it breaks. Before using it in production, make sure you replace all mentions of these service-account e-mails, otherwise they will have access to your self-hosted instance.
I tried Documenso, not bad but not amazing. I am looking for an e-signature solution to self-host and would like to hear your recommendations.
For better or worse, DocuSeal and OpenSign are basically the whole self-hosted e-sign field right now. Most options nail PDF plus fields plus audit log, but if Documenso already felt almost there, that is just where the ecosystem is. UX is still catching up to the big hosted tools.
9 sourcesWhere this page’s facts came from. Open the receipts.
- 1GitHub - documenso/documenso repo
- 2GitHub API - repo metadata (stars, language, activity)
- 3Documenso LICENSE (AGPL-3.0)
- 4Documenso Enterprise Edition LICENSE (commercial carve-out)
- 5Documenso Enterprise Edition FEATURES (SSO portal, 21 CFR Part 11, white-label embed)
- 6Documenso pricing (Free, Individual $25, Teams $40, Platform $250)
- 7Reddit r/selfhosted - Documenso self-host cert issues + feedback
- 8Reddit r/selfhosted - self-hosted e-signature options incl Documenso
- 9Product Hunt - Documenso reviews (5.0, 13 reviews)
Watch it work
Real tutorials and reviews from YouTube, not ours.