OpenSign
Open-source e-signature app with templates, audit trails and a document drive
Our verdict
#3 of 3 in Self-hosted e-signature tools · For teams with no integrations to build
Pros
- The official Compose file starts MongoDB alongside the app, and documents sign with a built-in certificate
- User roles are documented for self-hosted installs
- Two-factor login for users, with no plan restriction in the docs
Cons
- The free self-hosted version has no API, and live webhooks need a paid plan
- Automatic reminders and bulk send are paid-plan features
- MongoDB authentication is off by default, so MongoDB's port 27017 must stay closed to the internet
- The README warns that the default MongoDB instance in deployment is cleared on restart
Who should skip:Developers who need an API or webhooks to connect signing to other software.
Rankings and alternatives
Self-hosted e-signature tools scores
Evaluated Nov 7, 2026 Evidence ↓- Self-hosted setup 4
4/5 means: An official Docker Compose setup starts the app and its database, and documents are signed with a certificate the app provides.
The official Docker Compose file starts OpenSign with a MongoDB container, and documents are signed with a built-in certificate by default. The README warns that the default MongoDB instance in deployment is cleared on restart, and the install guide warns that MongoDB authentication is off by default.
- Sending features in the free edition 3
3/5 means: Three of the five features.
Signing in a set sequence, sharing signing links, and documents that expire after a set number of days are in the README; automatic reminders and bulk send are documented as paid-plan features.
- API, webhooks and embedding in the free edition 1
1/5 means: Neither an API nor webhooks in the free self-hosted edition.
An OpenSignLabs collaborator states that APIs are not part of the free self-hosted version, and the documentation says live webhooks need a paid plan.
- Digital signature options 3
3/5 means: You can sign with your own certificate (a .p12 or .pfx file).
A self-hosted install can sign with your own PFX or P12 certificate. The captured documentation doesn't mention a timestamp server or HSM-held keys.
Rests partly on what the sources don't mention, which is a weaker signal than what they say.
- Team and login controls in the free edition 3
3/5 means: Three of the five controls.
User management is documented for self-hosted plans, with OrgAdmin, Editor and User roles, and the docs describe two-factor login with no plan restriction. Teams need the Teams or Enterprise plan, and the captured documentation doesn't mention single sign-on.
Rests partly on what the sources don't mention, which is a weaker signal than what they say.
- Document storage choices 2
2/5 means: Two documented storage options.
A self-hosted install stores files on local storage or in a DigitalOcean Spaces or AWS S3 bucket.
Evidence and sources
Self-hosted e-signature tools scores
Self-hosted setup 5 quotes
-
“The simplest way to install OpenSign on your own server is using official docker images”
github.com/OpenSignLabs/OpenSign · checked -
“The default MongoDB instance used in deployment is not persistant and will be cleared on every restart.”
github.com/OpenSignLabs/OpenSign · checked -
“MAKE SURE THAT PORT 27017 IS NOT EXPOSED TO THE INTERNET, AS THE DEFAULT CONFIGURATION DOES NOT ENABLE MONGODB AUTHENTICATION.”
docs.opensignlabs.com/docs/self-host/docker/run-locally · checked -
“image: mongo:latest”
github.com/OpenSignLabs/OpenSign/blob/main/docker-compose.yml · checked -
“By default, OpenSign uses its built-in signing certificate to digitally sign documents.”
docs.opensignlabs.com/docs/help/User%20Menu/Console/signing_certificate · checked
Sending features in the free edition 5 quotes
-
“invite by sharing signing links & being able to enforce signing in a sequence”
github.com/OpenSignLabs/OpenSign · checked -
“You can set documents to expire after certain number of days after which nobody will be able to sign.”
github.com/OpenSignLabs/OpenSign · checked -
“Once you enable the auto reminder, a text field will appear allowing you to set the reminder for a specific number of days.”
docs.opensignlabs.com/docs/help/New-Document/request-signatures · checked -
“This feature only available for the paid users.”
docs.opensignlabs.com/docs/help/New-Document/request-signatures · checked -
“Bulk Send is available only in paid plans.”
docs.opensignlabs.com/docs/help/Templates/quick-send · checked
API, webhooks and embedding in the free edition 2 quotes
-
“APIs are not a part of the free self-hosted version.”
github.com/OpenSignLabs/OpenSign/issues/1231 · checked -
“To enable Live Webhook support, you must upgrade to a paid plan — either the Professional or Teams plan.”
docs.opensignlabs.com/docs/help/Settings/Webhook · checked
Digital signature options 2 quotes
-
“By default, OpenSign uses its built-in signing certificate to digitally sign documents.”
docs.opensignlabs.com/docs/help/User%20Menu/Console/signing_certificate · checked -
“Base64 encoded PFX or p12 document signing certificate file.”
docs.opensignlabs.com/docs/self-host/guides/env-variables · checked
Team and login controls in the free edition 4 quotes
-
“This functionality is available on Self-Hosted, Teams, and Enterprise plans.”
docs.opensignlabs.com/docs/help/Settings/manage-users · checked -
“OrgAdmin: Full access, including user and team management.”
docs.opensignlabs.com/docs/help/Settings/manage-users · checked -
“Teams must be created beforehand under Settings → Teams (available in Teams & Enterprise plans).”
docs.opensignlabs.com/docs/help/Settings/manage-users · checked -
“If 2FA is enabled, you will be prompted for a verification code every time you log in.”
docs.opensignlabs.com/docs/help/Settings/SecurityManagement · checked
Document storage choices 2 quotes
-
“If this is set to true, local file storage will be used to save files, and DO credentials will be ignored.”
docs.opensignlabs.com/docs/self-host/guides/env-variables · checked -
“Digital ocean space name or AWS S3 bucket name for uploading documents”
docs.opensignlabs.com/docs/self-host/guides/env-variables · checked
Facts
License 2 quotes
-
“OpenSign is licensed under the AGPL-3 License.”
github.com/OpenSignLabs/OpenSign · checked -
“All content that resides under the "apps/OpenSignServer/cloud/customRoute" directory of this repository, if that directory exists, is licensed under the license defined in "apps/OpenSignServer/cloud/customRoute".”
github.com/OpenSignLabs/OpenSign/blob/main/LICENSE · checked
Runs on 2 quotes
-
“The simplest way to install OpenSign on your own server is using official docker images”
github.com/OpenSignLabs/OpenSign · checked -
“Now sign unlimited documents even on the cloud hosted free version of OpenSign.”
github.com/OpenSignLabs/OpenSign · checked
Needs 2 quotes
-
“MAKE SURE THAT PORT 27017 IS NOT EXPOSED TO THE INTERNET, AS THE DEFAULT CONFIGURATION DOES NOT ENABLE MONGODB AUTHENTICATION.”
docs.opensignlabs.com/docs/self-host/docker/run-locally · checked -
“image: mongo:latest”
github.com/OpenSignLabs/OpenSign/blob/main/docker-compose.yml · checked
Other quotes
Not cited by a score or fact 5 quotes
-
“Guest signers can only sign the document after entering a unique code sent to their email address.”
github.com/OpenSignLabs/OpenSign · checked -
“A completion certificate is generated as soon as document is completed which contains all the document related logs for added safety.”
github.com/OpenSignLabs/OpenSign · checked -
“Yes. this is available in pad selfhosted version for that you need to contact to opensign Support.”
docs.opensignlabs.com/docs/help/New-Document/qualified_signature · checked -
“v3.1.0”
github.com/OpenSignLabs/OpenSign/releases · checked -
“It has long been removed from free self-hosted version.”
github.com/OpenSignLabs/OpenSign/issues/1231 · checked