Open-Source DocuSign Alternatives
What the open-source DocuSign rivals actually ask of you, checked against their repositories and pricing pages in September 2026.
The appeal of an open-source DocuSign alternative is easy to state: no per-seat subscription, no vendor lock-in, and source code you can read before you trust a provider with contracts. The part that gets understated is the operations. Open source removes the license fee, not the server, the TLS certificate, the backups, or the update cadence. This page compares the four projects that come up most, then maps the exit ramp for people who want the free part without the hosting part.
Facts were checked against each project's GitHub repository and pricing page in September 2026. One disclosure up front, because you will notice it anyway: AmiPDF, the site publishing this comparison, is not open source. Its PDF signing tools run client-side in your browser, which is a privacy architecture rather than a license, and the sections below keep the two ideas separate.
What the four projects have in common
All four are licensed under the AGPL family (AGPL-3.0; DocuSeal adds a Section 7 additional-terms file on top). None of them use a permissive MIT-style license, which matters if your plan is to embed signing into a product you ship: AGPL carries source-disclosure obligations for network services in a way MIT does not. Signing your own documents on an instance you run is ordinary use, and the obligations live at the distribution and hosting layers. Read the LICENSE file of any project before you build a business on it; this page compares trade-offs, not legal advice.
What they also share is the real price tag: your operations. A VPS, a domain, TLS, an SMTP relay for signature emails, a database, backups, and updates that someone has to apply. For a tinkerer that is a fair Saturday afternoon. For a two-person studio it is a second job that repeats monthly.
Open-source DocuSign alternatives, compared
| Project | License | Self-hosting needs | Hosted option |
|---|---|---|---|
| Documenso | AGPL-3.0 | Node.js 24+, PostgreSQL | Free 5 documents / month; paid from $25 / month |
| OpenSign | AGPL-3.0 | Docker, MongoDB | Free cloud plan, promoted as unlimited signatures |
| DocuSeal | AGPL-3.0 + additional terms | Docker, SQLite by default | Free 10 request emails / month; Pro $20 / user / month |
| LibreSign | AGPL-3.0 | Runs inside Nextcloud | No first-party cloud; via Nextcloud hosts |
Documenso is the most DocuSign-shaped of the four: full send-for-signature workflows, and a hosted free tier of 5 documents a month with up to 10 recipients if you want their code without your server. OpenSign self-hosts through Docker with MongoDB, and its README warns that the default database setup does not persist between restarts: bring your own MongoDB or lose your documents on the next reboot. DocuSeal leans on form building alongside signing, ships with SQLite so a first install is genuinely small, and its hosted Pro tier is $20 per user per month. LibreSign is a Nextcloud app, which is either a feature or a prerequisite: teams already running Nextcloud get signing inside their existing files and accounts; everyone else stands up a Nextcloud first.
If you arrived here by searching for a GitHub-hosted DocuSign alternative, those four repositories are the active ones the search results are built from.
The self-hosting checklist nobody puts on the landing page
Instance: a small VPS handles light signing volume for any of the four. Add a domain, a TLS certificate, and an SMTP relay, because signature requests are email-driven and deliverability is part of the product.
Persistence and backups: OpenSign's default MongoDB clears on restart unless you point it at a durable instance; Documenso expects PostgreSQL; DocuSeal defaults to SQLite and moves to PostgreSQL or MySQL through one environment variable. Whichever you pick, the signed documents and their audit trails are the data you must back up, because that evidence is the product.
Updates: AGPL projects ship fixes like any other software, and an e-signature server that falls behind on security updates is a liability wearing a badge that says free.
Free without a server: the other honest route
Not everyone who searches for open source wants the source. Plenty want the properties they associate with it: no subscription surprise, no document hoarding, no account wall. Those are obtainable without hosting anything.
AmiPDF's Sign PDF tool places your own signature on any page, and it runs entirely in your browser: no account, no upload, the file never leaves your device. That is an observable property, not a promise; the browser's network tab shows nothing leaving while you sign. The eSign service covers the send-for-signature direction, free for a one-time allowance of 3 documents with up to 2 signers each, with one-time $5 packs instead of a subscription when you need more, which sits next to the hosted tiers above without imitating them.
To be plain about the difference one more time: the open-source projects above give you inspectable code running on hardware you rent. AmiPDF gives you uninspectable-but-local code running on hardware you already own, for the signing half of the job. People with compliance mandates should pick the code. People who sign five documents a month should pick whichever of those two sounds like less work, and for most of them it is not the server.
Related pages: the full pricing comparison puts every hosted tier side by side, and free DocuSign alternatives covers the free tiers of the closed-source rivals.
Open-source questions
Is AmiPDF open source?
No, and this page would be a strange place to imply otherwise. AmiPDF's client-side tools are closed-source JavaScript that runs locally in your browser; you cannot read the source, but you can observe that signing uploads nothing. If reading the code is your requirement, use Documenso, OpenSign, DocuSeal, or LibreSign.
Does AGPL affect documents I sign on my own instance?
No. Using the software to sign your own documents is ordinary use and does not trigger source-disclosure obligations. AGPL obligations engage when you distribute the software or offer it as a network service to others. This page is a comparison, not legal advice; read the LICENSE of the project you choose.
Can I run one of these on a $5 VPS?
For light signing volume, yes: DocuSeal with SQLite is the smallest footprint, and the others run comfortably on a gigabyte-class instance. Budget for a domain and backups alongside the VPS, and expect an hour or two of maintenance per update rather than zero.
Which one is closest to DocuSign?
Documenso and OpenSign aim at the full send-for-signature workflow with audit trails and certificates, which is the core of what DocuSign sells. DocuSeal adds document form building on top. LibreSign is the natural pick only if you already run Nextcloud.