OpenSign

Is OpenSign actively maintained?

Development is ongoing. The repository recorded 81 commits over the same window, and the last three months alone account for 28 of them.

Activity is accelerating: the last quarter carried 100% more commits than the one before it.

The most recent tagged release, v2.41.3, shipped within the last month — a current, installable version exists today.

Note that OpenSign depends on a third-party service to work fully. It is self-hosted, but not self-contained: if that external service changes its terms or disappears, your instance is affected.

OpenSign ranks #9 of 18 in Document Management, placing it mid-table for maintenance activity.

What OpenSign actually does

OpenSign is a self-hosted document signing application designed to handle electronic signatures and workflow management. It provides a viable open-source alternative to commercial services like DocuSign, running via containerised environments. The software allows you to upload agreements, route them for signatures, and track completion status.

Best fit: Teams requiring an internal digital signing workflow who need to retain strict control over their contract data and documentation. It suits organisations seeking to replace proprietary SaaS signing platforms with an on-premise solution.

Worth knowing: Adopting the AGPL-3.0 licence means any modifications you make and host publicly or as a service must also be open source, which requires legal review for commercial deployments. It also lacks the extensive third-party integration ecosystem of larger proprietary competitors.

Deployment notes

Deployment typically relies on Docker containers running a Node.js stack, which will usually require a persistent volume for storing uploaded documents and completed files. You will also need to configure a reverse proxy to handle TLS termination and domain routing.

Links

• Official website
• Source code