JKjkahrs595·Jul 27, 2026
Any benefits over DocuSeal?
https://github.com/docusealco/docuseal
In Show HN: Let's Seal – Let's Encrypt for document signing, free and self-hosteddocusealco
docuseal
Ruby2023–2026
docusealco / docuseal
docuseal
Open source DocuSign alternative. Create, fill, and sign digital documents ✍️
5Distinct people
6Mentions
0Explicit recommenders
19KGitHub stars
What to know before exploring
What it is
Open source DocuSign alternative. Create, fill, and sign digital documents ✍️
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year6 dated mentions
Observed mentions: 2023-07-20 10:04:44 UTC to 2026-07-27 20:41:11 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
6 sourcesUnknown if it's better or worse but https://support.google.com/docs/answer/12315692?hl=en ("Send signature requests & sign documents with eSignature")
and there have also been a bunch of alleged competitors submitted:
https://github.com/docusealco/docuseal#readme https://news.ycombinator.com/item?id=36798593
https://github.com/OpenSignLabs/OpenSign#readme https://news.ycombinator.com/item?id=38052344
https://github.com/documenso/documenso#readme https://news.ycombinator.com/item?id=38404129
but they're all AGPLv3 and the network effect is very real
In Docusign updates terms of service, training proprietary AI using user dataI mostly agree with the author. After working a couple of years with React client render and API a pure server render seems to be a way more productive. For my recent OSS project (https://github.com/docusealco/docuseal) I use server render everywhere except of the 2 most complex/dynamic UI parts (drag&drop form builder and the signing form). I think just figuring out which approach fits best for which part of the software is the most important thing, doing both SSR and CSR in a single project is completely fine when done right.
In Server-side rendering is a better choice for many applications (2020)There are alternatives: https://github.com/docusealco/docuseal
I would like esignatures to be backed by strong electronic authentication, like EIDAS
In eSignature Beta for Google Docs and Google DriveThanks, please feel free to open an issue with your suggestion to improve the tool at https://github.com/docusealco/docuseal/issues
In Docuseal: Open-source DocuSign alternativeDocuseal: Open-source DocuSign alternative
671 points · Open discussion