Learn how OpenSign and Wraft 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 30 days
Last commit
28 days agoRepository age
2 yearsVersion
v0.6.7License
AGPL-3.0Self-hosted
YesRepository
wraft/wraft
OpenSign appears to have several advantages over Wraft, particularly in popularity and growth. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
OpenSign significantly outpaces Wraft in community adoption with 7,201 stars compared to 167 stars on GitHub. This 43.1x difference suggests OpenSign has a much larger and more active community. In terms of developer contributions, OpenSign has 851 forks, indicating moderate developer engagement.
OpenSign is growing faster, adding 155 stars in the last 30 days (+2.2%) against adding 1 stars for Wraft (+0.6%). OpenSign is both larger and pulling further ahead.
Both projects show recent activity, with OpenSign last updated 13 hours ago and Wraft 28 days ago.
Both tools share common technology foundations, being built with JavaScript, CSS, Bash. However, they differ in their additional technology choices: OpenSign uses Typescript, JSX while Wraft leverages Rust, Lua, Elixir.
Both projects started around the same time, with OpenSign beginning 3 years ago and Wraft 2 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. However, they also have distinct specializations: Wraft extends into Document Management Systems.
Both OpenSign and Wraft offer self-hosting capabilities, giving you full control over your data and infrastructure.