libresign
docuseal
| libresign | docuseal | |
|---|---|---|
| 2 | 13 | |
| 428 | 5,210 | |
| 4.4% | 4.2% | |
| 9.9 | 9.9 | |
| 2 days ago | 7 days ago | |
| JavaScript | Ruby | |
| GNU Affero General Public License v3.0 | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
libresign
-
Sign contract tool
Nextcloud app LibreSign
docuseal
- Docusign just admitted that they use customer data to train AI
-
Docusign updates terms of service, training proprietary AI using user data
Unknown 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
- DocuSeal – Open-source Document Signing
-
Niche request
Docuseal might also do the same and it's open-source
- Selfhosted DocuSign alternative
-
Server-Side Rendering Is a Thiel Truth (2020)
I 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.
- DocuSeal: Open-Source Document Signing
-
eSignature for Google Docs and Google Drive (Beta)
There are alternatives: https://github.com/docusealco/docuseal
I would like esignatures to be backed by strong electronic authentication, like EIDAS
- Docuseal: Open-source DocuSign alternative. Create, fill, sign digital documents
What are some alternatives?
documenso - The Open Source DocuSign Alternative.
forms - 📝 Simple form & survey app for Nextcloud
ifme - Free, open source mental health communication web app to share experiences with loved ones
text - 📑 Collaborative document editing using Markdown
quickstart-rails-tailwind - Start building rapidly with quickstart-rails-tailwind.
photos - 📸 Your memories under your control
mapzy - Simple, open-source and self-hostable store finder.
viewer - 🖼 Simple file viewer with slideshow for media
react-on-rails - Integration of React + Webpack + Rails + rails/webpacker including server-side rendering of React, enabling a better developer experience and faster client performance.
turbo - The speed of a single-page web application without having to write any JavaScript
sso-wall-of-shame - A list of vendors that treat single sign-on as a luxury feature, not a core security requirement.