Viewing profile — somery

It's great that such communities exist, but I personally prefer Discord

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 …

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 bei…

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 DO…

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... Bas…

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. …

Thanks! :)

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…

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 (…

Self-hosted Docuseal also sends emails to the signers - you just need to add your SMTP configs to send emails.

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…

Yep, support for SMS verification will be added eventually with ability to bring own Twilio credentials when self-hosting it.

That's a good idea! will definitely add this feature to the project

Thanks, please feel free to open an issue with your suggestion to improve the tool at https://github.com/docusealco/docuseal/issues

When self-hosting it it's possible use merkle tree to ensure the documents integrity (similar to how git works with its commit hashes). So to forge one document it will require to …

I think that's a valid point - and actually in their terms of services say that they are not responsible for the signer authenticity. Here is a summary from their TOS: "DocuSign pr…

It's hard to say at this point if something like Let's Encrypt can exist in this space - but I'm for sure going to continue offering a free Cloud SaaS option with a generous set of…

Thanks for the feedback! All your UI suggestions/fixes make sense and will definitely be brought into the the tool soon! Also I like the idea of using some 'fake' legal document fo…

can you please elaborate which use-cases? - maybe that's something that actually can be possible by splitting some parts of the project into MIT licensed dependencies?

It's possible to use local storage or Aws s3, Azure, Google Cloud to store files. When storing locally it makes all the documents 100% owned by you - but in some cases companies mi…

thanks, i think that's an interesting space to explore. there were many comments regarding the 'consistency' of the data/documents so solving this 'trust' issue especially when sel…

>A self-hosted digital signature system isn't worth anything in court; the other parties will simply reject the authenticity of any data held within it and the amount you'd have to…