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 commit
Repository age
Version
License
Self-hosted
Repository

Last 30 days
Last commit
Repository age
Version
License
Self-hosted
Repository

Both OpenSign and Wraft 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.
OpenSign significantly outpaces Wraft in community adoption with 7,081 stars compared to 167 stars on GitHub. This 42.4x difference suggests OpenSign has a much larger and more active community. In terms of developer contributions, OpenSign has 839 forks, indicating moderate developer engagement.
OpenSign and Wraft are moving at much the same rate, adding 101 stars and adding 2 stars respectively over the last 30 days (+1.4% vs +1.2%). Neither is pulling away from the other on momentum alone.
Wraft shows more recent development activity with its last commit 8 days ago, while OpenSign was last updated 2 months ago. This suggests Wraft is being more actively maintained.
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.