OpenSign

Key features

• Unlimited free-plan signatures The free plan includes unlimited e-signatures, so sending and signing volume stops being a budgeting exercise.[1]

• Multi-party signing workflow Several people can be invited into one signing process, which fits approvals and deals that need more than one signature.[1]

• Completion certificates with access logs Every signed document comes with a detailed completion certificate featuring access logs at no extra cost.[1]

• Built-in document vault Signed files are stored and organized in a built-in document vault instead of scattering across inboxes.[1]

• Self-hosting with Docker and one-click installers Teams can deploy OpenSign themselves with Docker guides and one-click installers, keeping documents and audit trails inside their own perimeter.[1]

• Managed cloud option A hosted cloud app runs the same product for teams that prefer not to operate infrastructure.[1]

• Versioned REST API Versioned REST API documentation covers users, contacts, documents, templates, webhooks, and folders for embedding signing into other products.[1]

• Reusable templates Template endpoints standardize repeat agreements such as offers, NDAs, and intake forms so repeat paperwork can be generated programmatically.[1]

Who will love it

• High-volume senders on tight budgets Teams sending hundreds of routine forms gain the most, because the free plan removes the envelope counter that per-envelope pricing imposes.[1]

• Privacy-minded teams that self-host Teams that must keep signed documents on their own infrastructure fit well, since the AGPL-3.0 codebase ships with Docker and one-click deployment paths.[1][2]

• Developers embedding signatures Developers adding signing to onboarding, contracts, or approvals fit well, since versioned endpoints plus templates let signing become a background workflow step.[1]

Who should avoid it

• Buyers requiring documented SSO or an SLA Neither SSO nor an enterprise SLA is stated on the inspected official pages, so procurement that requires them cannot proceed on OpenSign alone.[1][2]

• Mobile-first signing teams Native mobile apps are not documented and the product is presented as a web service, so field teams should confirm the mobile web experience first.[1]

• Regulated teams needing certified compliance claims Certifications beyond completion certificates and access logs are not evidenced, so teams facing a named-standard audit should avoid OpenSign until such claims are documented.[1]

What the reports suggest