Learn how Docuseal and OpenSign differ in their key features, development activity, technology stack and community adoption, so you can decide which of these e-signature platforms is best for you.
Last 30 days
Last commit
23 hours agoRepository age
3 yearsVersion
3.3.8License
AGPL-3.0Self-hosted
YesRepository
docusealco/docuseal
Last 30 days

Both Docuseal and OpenSign have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Docuseal leads in popularity with 19,104 stars vs 7,310 stars for OpenSign. The 161% higher star count indicates stronger community adoption. In terms of developer contributions, Docuseal has 1,964 forks, indicating strong developer engagement.
OpenSign is growing faster, adding 173 stars in the last 30 days (+2.4%) against adding 337 stars for Docuseal (+1.8%). OpenSign is the smaller project of the two, so it is closing the gap rather than extending a lead.
Both projects show recent activity, with Docuseal last updated 23 hours ago and OpenSign 7 days ago.
Both tools share common technology foundations, being built with JavaScript. However, they differ in their additional technology choices: Docuseal uses SCSS, Vue, Ruby while OpenSign leverages CSS, Bash, Typescript, JSX.
Both projects started around the same time, with Docuseal beginning 3 years ago and OpenSign 3 years ago.
Both projects use the AGPL-3.0 license, providing identical terms for usage and distribution.
Both tools serve similar use cases in E-Signature Platforms.
Both Docuseal and OpenSign offer self-hosting capabilities, giving you full control over your data and infrastructure.