somery
Joined 5 years ago
Karma
117
Submissions
42
Member since
Dec 16
Recent submissions
Comment · 1 year ago
It's great that such communities exist, but I personally prefer Discord
Comment · 3 years ago
In this highly competetive market we're currently more focused on things that we can do better like on-premises and embedding/API.
DocuSeal doesn't require any significant initial costs to be built - and then it comes only to our ability to build a great product to come over the competitors.
Regarding the compliance we're focused on simple eIDAS signatures for the EU and also we follow the UETA and the ESIGN Act.
Comment · 3 years ago
Hi everyone, Alex here, one of the co-founders of DocuSeal.
We're using Ruby on Rails and Vue to build DocuSeal and it really helps us to stay lean and ship features fast while being bootstrapped.
Here is a short list of what the tool can do:
- Automatic eSignatures
- Multiple submitters
- 10 document form field types
- Emails via SMTP
- AWS S3, GCP, Azure Cloud files storage
- Open large files up to 500MB
I'm happy to answer any questions!
Comment · 3 years ago
When comparing to Iframe our JS-based solution better adopts to the existing page layout due to the fact that it embeds into the existing page DOM (when iframe lives in it's own DOM which brings many limitations). Also it loads much faster than any equivalent iframe solution
Comment · 3 years ago
The solution utilizes a native web elements (aka web components) browser API for easier embedding into websites: https://developer.mozilla.org/en-US/docs/Web/API/Web_compone...
Basically instead of using JS snippet for mounting the UI - we're using a custom web element so it can be embedded just with HTML tag without JS.
Comment · 3 years ago
Hi, it's Alex from DocuSeal.
Recently we released a new embedded JS api for document signing at DocuSeal. Instead of doing it via iframe we decided to provide a JS-based solution.
Here are some benefits over iframe:
- faster load speed
- easy to customize
- optimized on different screen sizes
Also there is a React components library which also works with SSR Next.js https://github.com/docusealco/docuseal-react
Looking for some feedback and would be happy to answer any questions.
Comment · 3 years ago
Thanks! :)
Comment · 3 years ago
Hi everyone, my name is Alex, and I'm the CTO and Founder at DocuSeal – an open-source alternative to DocuSign.
Recently, we launched DocuSeal Cloud, which is available in both the US and EU regions. Our goal is to create a developer-friendly document signing infrastructure, similar to how Stripe has revolutionized the payment infrastructure. The HTML API described in this blog post is the first step of this initiative. You can find more information about the developer tools at DocuSeal here: https://www.docuseal.co/integration.
Looking for some feedback and would be happy to answer any questions.
Comment · 3 years ago
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.
Comment · 3 years ago
Self-hosted Docuseal also sends emails to the signers - you just need to add your SMTP configs to send emails.
Comment · 3 years ago
Currently the documents are signed with PKCS#1 signature, signed documents can be verified at https://demo.docuseal.co/settings/esign (to ensure that they were produced by the tool and not altered/forged by some third party). Additionally I'm planning to add a merkle-based log of documents to ensure that documents were not altered by the party that is self-hosting the tool.
Comment · 3 years ago
Yep, support for SMS verification will be added eventually with ability to bring own Twilio credentials when self-hosting it.
https://www.docuseal.co
https://github.com/docusealco/docuseal
[email protected]