somery

5 ms·

1.
by somery 2y ago
It's great that such communities exist, but I personally prefer Discord
2.
by somery 3y 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
3.
by somery 3y 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
4.
Why we bootstrap(docuseal.co)
2 points by somery 3y ago|3 comments
5.
by somery 3y 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 fa
6.
by somery 3y 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
7.
by somery 3y 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
8.
Show HN: Embeddable DocuSign alternative via native Web Components(docuseal.co)
6 points by somery 3y ago|5 comments
9.
by somery 3y ago
Thanks! :)
10.
by somery 3y 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-f
11.
Show HN: Creating Fillable PDF Document Forms with HTML(docuseal.co)
8 points by somery 3y ago|4 comments
12.
by somery 3y 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
13.
by somery 3y ago
Self-hosted Docuseal also sends emails to the signers - you just need to add your SMTP configs to send emails.
14.
by somery 3y 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 t
15.
by somery 3y ago
Yep, support for SMS verification will be added eventually with ability to bring own Twilio credentials when self-hosting it.
16.
by somery 3y ago
That's a good idea! will definitely add this feature to the project
17.
by somery 3y ago
Thanks, please feel free to open an issue with your suggestion to improve the tool at https://github.com/docusealco/docuseal/issues
18.
by somery 3y ago
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 change all document hashes after the disputed document
19.
by somery 3y ago
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 provides tools and features that help to establish t
20.
by somery 3y ago
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 features for document signing. I'd love
21.
by somery 3y ago
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 for the demo. Regarding the iframe - i've
22.
by somery 3y ago
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?
23.
by somery 3y ago
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 might want to bring a third party files storages to ensur
24.
by somery 3y ago
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 selfhosting it is really importan
25.
by somery 3y ago
>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 spend to get that data into evidence would pro
26.
by somery 3y ago
When self-hosting it - it's up for the company that is using the tool hosted on-premises to ensure that all their specific requirements are met - i think DocuSeal provides enough features to make this happen. AWS S3 to store documents
27.
by somery 3y ago
That's interesting that you ended up developing an in-house document e-signing feature for your product. I'm curious, would it be possible for you to choose a self-hosted and open-source solution like Docuseal, integrated with you
28.
by somery 3y ago
When selfhosting it - it's possible to connect AWS S3 to store the documents - AWS with S3 logs could be used as a source of trust to ensure the documents are not altered.
29.
by somery 3y ago
The emails are automatically sent to the recipients after you submit the modal window to add them (there should be 'SENT' status displayed next to their emails) Regarding the form issue - it looks like some js client side bug - i&
30.
by somery 3y ago
can you please elaborate what exactly from docsend you'd love to see available in docuseal?

More ›