
Commercial e-signature tools made it easy to send a contract, collect a signature, and keep a record. They also made the bill easy to predict in the wrong direction: a charge for every sender, a cap on envelopes, and every agreement sitting on a vendor’s servers. For a lot of ordinary business documents, that is more product than you need, and less control than you want.
Open-source e-signature platforms take the same basic loop — upload a PDF, place fields, send a link, store a signed copy and an audit trail — and let you run it on infrastructure you control. Some of these tools are now mature enough to replace a commercial product for everyday agreements. Others are better thought of as signing infrastructure: libraries and servers that apply cryptographic seals, rather than a full “send this contract” product.
The newest entry in the first group arrived on November 16, 2026, when Kevin Rose wrote that DocuSign wanted $8,100 a year for a 15-person team, so he built SignuDoc: an MIT-licensed app you deploy to your own Vercel account, with no per-seat fee. That number is Rose’s, based on DocuSign’s published U.S. plan prices as of November 2026, and those prices change. The more useful part of the announcement is the model: the documents stay in accounts you own, the signed PDF carries a tamper-evident seal, and the cost does not rise when you add another person who sometimes sends a contract.
This article explains what that model is worth, which open-source tools exist today, where they fit in high-value workflows, what U.S. and EU signature law actually requires, and how to put one of these systems into production. It is not legal advice. Whether a particular signature is valid depends on the document, the parties, and the law that applies.
What you actually gain
The commercial tools are good. The case for an open-source alternative is not that they are bad. It is that a large share of signing work does not need a per-seat license, a shared multi-tenant cloud, or a 1,000-integration marketplace.
Cost that does not track headcount
Most commercial plans charge by sender and then cap how many envelopes each sender can use. Open-source tools have no license of that kind. You pay for compute, storage, a database, and outbound email. SignuDoc’s project documentation says the free tiers of Vercel, Neon, and Resend will carry about 250 documents a month at no charge. Self-hosted Documenso, DocuSeal, and OpenSign similarly have no per-envelope license in their community editions. You can still spend money on a hosted plan, a Pro or Enterprise license, SMS identity checks, or a qualified-signature provider. You just stop paying a seat tax for people who send a contract twice a month.
Data that stays where you put it
A signed share-purchase agreement, a loan package, or a patient consent form is not a good candidate for “wherever the vendor’s region happens to be.” Self-hosting, or a deploy into your own cloud account, lets you choose the region, keep documents on a private network, and set retention yourself. That is the practical meaning of data sovereignty here: you know which country the files are in, who can read the database, and how long a finished PDF is kept.
Evidence you can inspect
A useful e-signature system does more than capture a squiggle. It should record that the signer agreed to transact electronically, bind the signature to a specific document, and produce a record you can keep and reproduce. The better open-source tools go further: they seal the finished PDF so a standard reader can detect later changes (often with a PAdES signature), keep a hash-chained or otherwise append-only audit trail, and, in SignuDoc’s case, offer a public Verify page that checks a file’s fingerprint without uploading the file. Because the code is public, you can also read how that evidence is produced.
Customization, APIs, and no lock-in
If signing is a step inside your own product — a domain transfer form, a loan origination system, an HR portal — you want an API, webhooks, and the option to embed the signing page. Documenso, DocuSeal, OpenSign, and LibreSign all expose APIs. SignuDoc, as of its public launch, does not; its README is explicit that an API is “not yet” available. On the flip side, SignuDoc is MIT-licensed, which is easier to embed in proprietary software than the AGPL licenses used by most of the others. AGPL is fine for internal use. It becomes a serious question if you modify the software and offer it to customers over a network, because you may have to share those modifications.
The current open-source platforms
These are the maintained projects that matter if you are looking for a “DocuSign killer,” plus two widely used signing-infrastructure projects that are not products in that sense. Hosted options are noted where the same team also runs a cloud service. A public demo instance is not the same thing.
SignuDoc
SignuDoc is the project Kevin Rose announced in November 2026. It is published by Nyllon Software under the MIT license. You deploy it onto your own Vercel account; PDFs go into a private Vercel Blob store, everything else into a Neon Postgres database, and email goes out through Resend, in a region you choose. There is no separate vendor-hosted SignuDoc cloud. The product covers the everyday loop well: a PDF, up to ten signers in order, field types including signature, initials, date, text, checkbox, dropdown and radio, templates, deadlines, reminders, access codes or emailed one-time codes, white-label branding on your domain, a PAdES seal (self-signed by default, or your own certificate, with optional long-term validation), and a hash-chained audit trail.
It is also new, and its own documentation is frank about the gaps. It signs one PDF per envelope, in sequence only, with signing pages in English. There is no API, no SSO, and no bulk send. Advanced and qualified signatures under eIDAS are possible only if you connect a provider such as eID Easy or a CSC remote-signing service, and the project says that flow has been tested against stand-ins, not yet against the live services. For FDA 21 CFR Part 11 records, an administrator can turn on a Part 11 mode; validating the install and writing the procedures remains your job. Treat it as a serious, early tool for your own organization, not as a drop-in enterprise platform.
Documenso
Documenso is the best-known full product in this category: a modern signing workflow with recipients, fields, templates, teams, and an API, licensed under AGPL-3.0. The code is on GitHub. You can self-host it with Docker or Kubernetes, or use Documenso’s own cloud. Self-hosting requires a signing certificate; without a .p12 file, the app starts but document signing fails. Every completed document is digitally signed with that X.509 certificate. SSO, white-label embedding, and some other features sit in paid or Enterprise editions. On its compliance page, Documenso states that it is compliant with the U.S. ESIGN Act, UETA, eIDAS simple electronic signatures, 21 CFR Part 11, SOC 2, and HIPAA, and that eIDAS advanced and qualified signatures are planned for the second half of 2026. Those claims are the company’s, and they apply to its product — especially the hosted service, where a Business Associate Agreement and a SOC 2 report can actually be issued. A self-hosted copy still has to be configured, operated, and, if you need Part 11 or HIPAA, validated by you.
DocuSeal
DocuSeal is built around reusable, fillable PDF forms. A drag-and-drop builder offers field types such as signature, date, checkbox, image, and cells; documents can go to multiple submitters; storage can sit on disk or in S3, Google Cloud, or Azure; and there is an API with webhooks. The code is on GitHub, under AGPL-3.0 with additional terms published by DocuSeal. You can self-host the open-source edition for free, or use DocuSeal’s cloud. White-label branding, user roles, SMS identity checks, SSO/SAML, bulk send, and embedded builders are Pro features. If your workload is the same form, sent again and again, this is usually the most natural fit.
OpenSign
OpenSign aims at a broad, DocuSign-like feature set in the free software: sequential multi-signer workflows, templates, bulk send, reminders, expiry, rejection, email one-time-code checks for guest signers, a completion certificate and audit trail, a document vault called OpenSign Drive, and a REST API. It is AGPL-3.0, with the code on GitHub. You can self-host it with Docker or use OpenSign Cloud, which has a free tier and paid plans. It is a strong option when you want many workflow features without buying an enterprise edition first.
LibreSign
LibreSign is an AGPL-3.0-or-later Nextcloud app, with the code on GitHub and documentation at docs.libresign.coop. Signing happens next to the files, users, and sharing model you already have. It supports signing order, internal and external signers, reminders, document validation, an API, and hybrid signatures that can use a personal certificate or a system-generated one. There is no separate LibreSign SaaS in the usual sense; you self-host Nextcloud, and the team offers optional professional deployment and support. Choose it if you already run Nextcloud and want signing to live there, not if you want a standalone envelope product.
Signature PDF
Signature PDF, from 24ème, is a lightweight AGPL-3.0 PHP application for signing a PDF alone or with others, and for organizing, compressing, and editing PDF metadata. The code is on GitHub, it deploys with Docker or a conventional PHP host, and a list of public instances is published in the repository. Optional multi-signer mode stores files on the server. Optional digital signatures use NSS certificates and poppler. It is a useful, well-maintained signing utility. It is not a template, reminder, and API platform.
SignServer and DSS, if you need the cryptography rather than the workflow
Two other open-source projects show up in every serious conversation about digital signatures, and they are easy to mis-label as DocuSign replacements. They are not.
SignServer Community, sponsored by Keyfactor and licensed under LGPL-2.1 or later, is a server that applies digital signatures and timestamps to documents, code, and other artifacts, with keys held in one place. The code is on GitHub. There is a commercial Enterprise edition as well.
The European Commission’s Digital Signature Service (DSS) is an LGPL-2.1 Java library for creating and validating CAdES, XAdES, JAdES, and PAdES signatures in line with eIDAS and ETSI standards. The code is on GitHub. If you need to build or verify advanced or qualified signatures, this is the reference implementation many other systems sit on. It has no signer-facing envelope product of its own.
One historical note, so it does not get confused with the current list: Open eSignForms, from Yozons, was an early AGPL web-contracting platform. The project itself says only versions through 19.3.23 are AGPL, and that more current versions are commercial. It is not a current open-source alternative.
How they compare
| Project | License | How you run it | Hosted option | API | Best fit |
|---|---|---|---|---|---|
| SignuDoc | MIT | Your own Vercel, Neon, and Blob accounts | No vendor cloud; you host it | Not yet | Small and mid-size teams that want everyday PDF signing they own |
| Documenso | AGPL-3.0 | Docker, Kubernetes, or similar; needs a .p12 certificate | Yes, Documenso Cloud | Yes | A polished, general-purpose replacement, self-hosted or managed |
| DocuSeal | AGPL-3.0 with additional terms | Docker; disk or S3-compatible storage | Yes, DocuSeal Cloud | Yes, plus webhooks | Reusable templates and fillable PDF forms |
| OpenSign | AGPL-3.0 | Docker, on your cloud or servers | Yes, OpenSign Cloud | Yes | A broad free feature set, including bulk send and OTP checks |
| LibreSign | AGPL-3.0-or-later | A Nextcloud app | No SaaS; optional paid deployment help | Yes | Organizations already running Nextcloud |
| Signature PDF | AGPL-3.0 | Docker or PHP hosting | Public demo instances only | No full workflow API | Simple PDF signing and file tools, not envelope workflows |
| SignServer Community | LGPL-2.1-or-later | Self-hosted signing server | Enterprise edition is commercial | Server APIs, not an envelope UI | Central, certificate-based signing of documents and code |
| DSS | LGPL-2.1 | Java library | n/a | Library APIs | Creating and validating PAdES and other AdES signatures |
High-value workflows
The legal weight of a signature and the operational need to control the file often rise together. These are the places where a self-hosted or self-accounted system is most often worth the work.
Mergers, acquisitions, and other corporate closings
NDAs, term sheets, disclosure letters, and many ancillary closing documents are routinely signed electronically. The files are sensitive, the signer list is short, and the audit trail matters if a term is later disputed. A system you host — with a sealed PDF, a recorded consent to transact electronically, and a retention rule you set — is a good fit for that work. Some closing deliverables, board consents, or filings may still call for a wet-ink signature or a higher eIDAS level. Treat the platform as the workflow, and let counsel decide the level of signature each document needs.
Real estate
Purchase contracts, disclosures, and leasing paperwork are widely signed electronically in the United States. Recordable instruments are a different problem. In many states, a deed, mortgage, or other document that has to be recorded still requires a wet-ink signature, a specific electronic-notarization process, or both. An open-source platform can handle the contract package and the audit trail. It does not, by itself, satisfy county recording rules or remote-online-notarization statutes. Check the state and the recorder before you assume a closing can be entirely paperless.
Domain name sales and escrow transfers
A premium domain sale is a high-value contract with a short paper trail: a purchase agreement, sometimes an assignment, and then an escrow or registrar transfer. The transfer itself happens at the registry and the registrar. The contract still needs a clean, auditable signature, and neither party is eager to park that agreement in a shared vendor tenant they do not control. This is a natural place for a self-hosted signing step, then a handoff to escrow. Teams that already transact in names — including buyers and sellers using a marketplace such as premium.lonestardomains.com — often need exactly that: a serious agreement, a verifiable record, and no per-envelope surprise when a deal finally closes.
Lending and other financial documents
Consumer and commercial loan documents are, as a rule, allowed to be electronic under the ESIGN Act and UETA, provided the usual conditions of intent, consent, and record retention are met. Investors, warehouse lenders, and secondary-market buyers sometimes impose their own packaging rules, and some promissory notes still have special original-note requirements. A platform with a strong audit trail and document integrity seals is useful here; so is the ability to keep files in a chosen region. It is not a substitute for the investor’s or regulator’s checklist.
Healthcare consents
Intake forms, treatment consents, and related acknowledgements often contain protected health information. The signature law is usually the straightforward U.S. kind: a simple electronic signature can be valid. The harder constraint is HIPAA. If a vendor hosts the documents for you, you generally need a Business Associate Agreement, plus encryption, access control, and audit logs. If you self-host, you are not buying HIPAA compliance by installing the software; you are taking those safeguards on yourself, which is sometimes the point. Several vendors state that their cloud products can support HIPAA. Read the actual BAA, and do not treat a marketing page as the compliance program.
HR and internal agreements
Offer letters, policy acknowledgements, contractor agreements, and invention assignments are the volume use case that makes per-seat pricing sting. They are also a good first workload for an open-source tool: the documents are repetitive, the legal bar is usually a simple electronic signature, and you already have the employee’s or contractor’s email. Some employment and immigration forms have their own electronic-signature rules. Keep those off the generic workflow until you have checked them.
Government and public-sector files
Public bodies often care less about the envelope UI and more about where the file lives, whether the signature can be validated years later, and whether the law requires an advanced or qualified signature. In the EU, some official filings and high-stakes acts require a qualified electronic signature. An open-source workflow tool can still be the front end, but the signature itself has to come from a qualified certificate and a qualified signature-creation device, usually through a qualified trust service provider. LibreSign’s Nextcloud model, SignServer, and DSS are the parts of this list that tend to show up in those designs.
What the law actually requires
Software does not make a signature legal. The statute, the document type, and the evidence you keep do. Open-source tools can give you a solid record for many everyday contracts. They cannot, on their own, reach every legal standard, and some documents are simply outside electronic-signature statutes.
United States: ESIGN and UETA
The Electronic Signatures in Global and National Commerce Act (15 U.S.C. § 7001) and the Uniform Electronic Transactions Act, adopted in some form by 49 states and the District of Columbia (New York uses its own Electronic Signatures and Records Act), are the foundation. In outline, an electronic signature is not denied legal effect solely because it is electronic, if the signer intended to sign, consented to do business electronically, the signature is logically associated with the record, and the record can be retained and accurately reproduced. Most typed, drawn, or click-to-sign flows in the tools above can support those elements, provided the product actually captures consent, binds the signature to a hash of the document, and lets you keep the result.
The statutes also have exceptions. Wills and certain family-law documents, some Uniform Commercial Code transactions, and a short list of other records are carved out or left to other law. State recording statutes can impose their own formalities on real-property instruments. ESIGN and UETA are why a consulting agreement or an offer letter can be signed in a browser. They are not a blanket rule that every document in the business may be.
European Union: eIDAS, in three levels
Regulation (EU) No 910/2014, known as eIDAS, and its 2024 update, Regulation (EU) 2024/1183, define three kinds of electronic signature:
- Simple electronic signature (SES). The basic form: a typed name, a drawn signature, a click that is logically associated with the document. It is admissible as evidence, but it offers the least assurance about identity. Most open-source envelope tools produce something in this category by default.
- Advanced electronic signature (AES or AdES). The signature must be uniquely linked to the signer, capable of identifying the signer, created with data the signer can use under their sole control, and tied to the document so that a later change is detectable. That usually means a certificate in the signer’s name and a PAdES, CAdES, or XAdES structure — not merely a platform certificate that seals the file after the fact. A system seal is still useful evidence of integrity. It is not, by itself, an advanced signature by the signer.
- Qualified electronic signature (QES). An advanced signature created by a qualified signature-creation device and based on a qualified certificate from a qualified trust service provider. In the EU, a QES has the equivalent legal effect of a handwritten signature. Open-source software cannot mint that status. You have to integrate a qualified provider. SignuDoc documents an optional connection to eID Easy or a CSC-compliant service for this purpose, with the caveat that it has not yet been tested against the live services. Documenso lists AES and QES support as planned for the second half of 2026. DSS is the library commonly used to create and validate the underlying signature formats.
PAdES, the ETSI standard for PDF advanced electronic signatures, is the technical format that lets a PDF reader check a seal years later, including with long-term validation data. Several of the tools above apply a PAdES or similar PDF signature. That is necessary for a durable, checkable file. It is not sufficient for QES unless the certificate and the signing device also meet the qualified tests.
HIPAA, 21 CFR Part 11, SOC 2, and GDPR
These regimes are often lumped in with “e-signature compliance.” They are mostly about how records are kept, not about whether a signature counts as a signature.
- HIPAA. Applies when the workflow includes protected health information. A hosted vendor typically must sign a Business Associate Agreement and implement the usual safeguards. A self-hosted tool can keep PHI on your network, which helps, but you still have to encrypt, restrict access, log activity, and handle incidents. Installing OpenSign or Documenso does not make a clinic “HIPAA compliant.”
- 21 CFR Part 11. The FDA’s rules for electronic records and electronic signatures in regulated life-science environments. They call for unique user identities, operational checks, audit trails, and, for signatures, a meaning attached to the signing act. SignuDoc has a dedicated Part 11 mode and a validation-pack of starting documents; the project is clear that you still have to validate the install and write your own procedures. Documenso states Part 11 compliance on its compliance page. In both cases, the regulated organization remains responsible for validation.
- SOC 2 and similar attestations. These are reports about a service organization’s controls. They can matter when you use a vendor’s cloud. They do not travel with the source code onto your server. If you self-host, your own controls — and, if a customer asks, your own audit — are what you have.
- GDPR and data residency. Running the software in the EU, or in a region you choose, makes it easier to know where personal data sits. You are still the controller for your signers’ data: legal basis, retention, access, and deletion. SignuDoc includes export and erasure tools for signer requests; other platforms vary. A region picker is not a GDPR program, but it is one of the better reasons to self-host.
How to put one into production
Self-hosting
The common path for Documenso, DocuSeal, OpenSign, and Signature PDF is a Docker image or a Docker Compose file, plus a database (Postgres for Documenso; Postgres, MySQL, or SQLite depending on the tool), object storage, and an SMTP server. Documenso also publishes Kubernetes and Helm options, and one-click deploys on some PaaS providers. LibreSign is installed as a Nextcloud app on a compatible Nextcloud site. SignuDoc is the odd one out: a one-click deploy to your Vercel account, with Neon and Resend provisioned for you, and no servers of your own to patch.
Before you send a real document, set up TLS at the edge, restrict outbound network access from the app (a self-hosted signer can often reach internal addresses if you let it), put the database and object store on private networks, and turn on backups you have actually restored once. Store the signing certificate and any SMTP or SMS credentials in a secret manager, not in the Compose file you commit to git.
Certificates, seals, and timestamps
Plan the certificate story at the start, not after the first failed envelope. Documenso will not sign documents without a .p12 certificate. SignuDoc seals with a self-signed certificate by default and can use yours; long-term validation (PAdES B-LTA) needs a timestamp server. Signature PDF’s optional digital signature uses an NSS certificate store. A self-signed platform certificate will prove that a file has not changed since your system sealed it. It will not automatically be trusted by Adobe’s trust list, and it will not turn a guest signer’s drawn name into a qualified signature. If you need a seal that PDF readers trust out of the box, you will be looking at a certificate from a publicly trusted CA, and, for QES, a qualified provider.
Managed cloud
Documenso, DocuSeal, and OpenSign all offer a hosted service if you want the product without running Docker. That is the right choice when your staff should not be patching containers, and when you need a vendor to sign a BAA or produce a SOC 2 report. You give up some of the sovereignty argument, so read where the data is stored and whether you can pin a region.
Embedding, SSO, storage, and backups
If signing is a step in your own application, use the API and webhooks: create the envelope when a deal reaches a certain stage, and close the workflow when the signed PDF comes back. SSO, usually SAML or OIDC, is often in a paid edition — DocuSeal lists it as a Pro feature; Documenso treats it as an Enterprise-style capability. SignuDoc currently uses email and password. Decide that before you roll it out to a firm that already lives in Okta or Microsoft Entra.
Put finished PDFs in storage you already know how to back up. Disk is fine for a small install; S3-compatible storage, Google Cloud, Azure, or Vercel Blob are the usual options. Back up the database on the same schedule as the files, because an audit trail without the PDF, or a PDF without the trail, is a weak record. Test a restore. Set a retention period that matches your contracts and your privacy policy, and do not invent a seven-year rule you cannot actually keep.
Limits, and how to choose
Open source does not remove the hard parts. It moves them.
- If you self-host, you own uptime, upgrades, bot protection, and the security of the box. A missed patch on a signing server is a missed patch on a store of contracts.
- Qualified signatures, and some advanced signatures, require a trust-service provider. The workflow tool can call that provider. It cannot replace one.
- Commercial platforms still win on breadth: Salesforce and Microsoft integrations, in-person signing, payments, identity-document checks, many languages, Word files, and simultaneous signing. SignuDoc’s own comparison is a fair guide to those gaps, and the larger projects have their own.
- AGPL is a poor surprise to discover after you have embedded a signing service in a commercial product. MIT (SignuDoc) and LGPL (DSS, SignServer) are easier in that situation. Read the license, including any additional terms, before you fork or white-label anything.
- A compliance logo on a vendor’s website is a claim about their service, not a certificate that travels with a Docker image.
A simple way to choose: if you already run Nextcloud, start with LibreSign. If the work is repetitive forms, start with DocuSeal. If you want a general-purpose product with a hosted option and an API, start with Documenso or OpenSign. If you want a small team’s PDF signing to live entirely in accounts you already have, and you can live without an API for now, look at SignuDoc — and review it as new software. If the real problem is cryptographic signing and validation rather than sending envelopes, look at SignServer and DSS.
Then pick one document type, send it through a staging install, download the signed PDF, and check the seal in a PDF reader. If you cannot explain the audit trail to a lawyer — or restore the file from backup — you are not ready for a closing binder, a loan file, or a patient record. You are ready for a second test.
This article is about software and publicly available legal frameworks. It is not legal advice, and it is not an assessment of whether any particular signature, document, or installation would be valid or enforceable.
Sources
https://x.com/kevinrose/status/2122394902168473975
https://github.com/NYLLON-SOFTWARE/SignuDoc
https://documenso.com
https://documenso.com/compliance
https://documenso.com/self-hosted
https://docs.documenso.com/docs/self-hosting
https://github.com/documenso/documenso
https://www.docuseal.com
https://www.docuseal.com/on-premises
https://github.com/docusealco/docuseal
https://www.opensignlabs.com
https://www.opensignlabs.com/self-hosted-esignature
https://github.com/OpenSignLabs/OpenSign
https://libresign.coop
https://docs.libresign.coop/
https://github.com/LibreSign/libresign
https://pdf.24eme.fr/
https://github.com/24eme/signaturepdf
https://www.signserver.org/
https://www.signserver.org/license/
https://github.com/Keyfactor/signserver-ce
https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467109107/Digital+Signature+Service+-+DSS
https://github.com/esig/dss
https://github.com/OpenESignForms/openesignforms
https://www.govinfo.gov/content/pkg/USCODE-2024-title15/html/USCODE-2024-title15-chap96-subchapI-sec7001.htm
https://www.uniformlaws.org/shared/docs/electronic%20transactions/ueta_final_99.pdf
https://eur-lex.europa.eu/eli/reg/2014/910/oj
https://eur-lex.europa.eu/eli/reg/2024/1183/oj
https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.03.01_60/en_31914201v010301p.pdf
https://www.ecfr.gov/current/title-21/chapter-I/subchapter-A/part-11
https://www.hhs.gov/hipaa/for-professionals/privacy/index.html
