🔥 The free & Open Source DocuSign alternative
6.6k
Stars
759
Forks
134
Open issues
30
Contributors
AI Analysis
OpenSign is a self-hosted, open-source alternative to DocuSign that enables secure PDF e-signing with multi-signer support, document annotation, and template management. It serves organizations and individuals seeking to avoid vendor lock-in and licensing costs for document signing workflows. Best suited for enterprises, legal teams, and compliance-conscious users who can self-host; not a good fit for users needing managed SaaS simplicity or extensive third-party integrations out of the box.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
OpenSign brings self-hostable e-signature workflows to teams that can't or won't pay DocuSign prices
OpenSign is an open source electronic document signing platform targeting businesses, legal teams, and developers who want DocuSign-grade features — multi-signer workflows, audit trails, OTP verification, templates, API access — without per-envelope pricing. It can be self-hosted for full data sovereignty or used via a free cloud tier. Its audience spans privacy-conscious SMEs, regulated industries requiring on-premise deployments, and developers embedding signing into existing applications. With 6,560 stars roughly 2.5 years after creation and an active Discord community, it occupies a credible position in a crowded open source e-signature space.
Launched in October 2023, OpenSign entered a market already being shaped by Documenso and DocuSeal. It appears to have been built by OpenSignLabs as a commercial open source play — free self-hosted tier plus likely paid cloud plans.
Growth appears driven by sustained organic interest in avoiding DocuSign's per-signature pricing model, amplified by Reddit and Hacker News discussions common to self-hosted alternatives. 34 stars in the last 7 days suggests modest but steady traction rather than viral momentum. The project has not had a single breakout spike but maintains consistent community engagement.
A free cloud-hosted version exists at opensignlabs.com, implying real user traffic, but independent production usage metrics (user counts, document volumes) are not publicly disclosed. Docker Hub pull counts and third-party deployment mentions are not cited in the README. Adoption appears real but scale is not independently verifiable.
Likely a React/JavaScript frontend paired with a Parse Server backend based on README references to cloud hosting and API key generation patterns. Appears to use Parse Platform for data modeling, which simplifies self-hosting but introduces a non-standard backend dependency. PDF manipulation likely handled server-side with PDF-lib or similar.
not documented in README
Last push was June 22, 2026 — 3 days before the evaluation date — indicating active development. Weekly commit activity badge in README suggests consistent cadence. Issue resolution badge present, implying the team monitors and closes issues. Maintenance signals are strong for a project of this age and star count.
ADOPT IF: you need a self-hosted, cost-controlled e-signature solution for an SME or internal tooling context, are comfortable managing Parse Server infrastructure, and don't require formal eIDAS/ESIGN legal certification out of the box. AVOID IF: you need certified legal compliance across multiple jurisdictions, enterprise SLA guarantees, or a fully TypeScript/modern-stack codebase that integrates cleanly with Next.js/Vercel deployments. MONITOR IF: you're evaluating open source e-signature options and want to see whether OpenSign's API and integration ecosystem matures to the point of replacing a paid SaaS subscription in the next 12 months.
Independent dimensions
Mainstream potential
5/10
Technical importance
6/10
Adoption evidence
4/10
- Parse Platform as backend introduces a relatively niche dependency — self-hosters unfamiliar with it may face a steeper operational learning curve than competitors using more conventional stacks.
- Legal enforceability of collected signatures varies by jurisdiction; the README does not document compliance certifications (eIDAS, ESIGN, UETA), which may disqualify it for regulated industries without additional legal review.
- Three direct open source competitors (Documenso, DocuSeal, and others) are better funded or more starred, meaning OpenSign may struggle to retain contributors pulled toward more visible projects.
- The project's JavaScript codebase (vs TypeScript in leading competitors) may increase friction for contributors and long-term maintainability, though this cannot be confirmed without source inspection.
- Commercial sustainability is unclear — if OpenSignLabs cannot convert free users to paid cloud plans, maintenance investment may decline over time.
OpenSign will likely remain a viable, actively maintained option in the open source e-signature niche but is unlikely to displace DocuSeal or Documenso as the community default without a significant differentiation event such as a compliance certification or a major enterprise contributor.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://www.opensignlabs.com
- Language
- JavaScript
- License
- NOASSERTION
- Last updated
- 2d ago
- Created
- 34mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
> ### Feature Title
> ### Feature Title
[Bug]: request for signature is "sent" even if email verification isn't completed
getsignedurl cloud function returns master-key-signed file URL for any user-supplied URL without authentication, bypassing the file access middleware
[Bug]: the "Are you sure you want to send" dialog just sends anyway
Top contributors
Similar repos
documenso/documenso
Documenso is an open-source, self-hostable alternative to DocuSign for digital...
Open-Source-Legal/OpenContracts
OpenContracts is a self-hosted document intelligence platform that transforms...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
OpenSignLabs/OpenSign
this
|
6.6k | +32 | JavaScript | 7/10 | 2d ago |
|
documenso/documenso
|
13.7k | — | TypeScript | 7/10 | 13h ago |
 docusealco/docuseal
|
17.5k | — | Ruby | 8/10 | 4d ago |
|
Open-Source-Legal/OpenContracts
|
1.4k | — | Python | 7/10 | 9h ago |
 papermark/papermark
|
8.8k | — | TypeScript | 7/10 | 2d ago |
 ONLYOFFICE/DocumentServer
|
6.7k | — | Shell | 7/10 | 3w ago |
Documenso (13.5k stars, TypeScript) has roughly 2x the GitHub visibility and a stronger developer-first brand. It integrates tightly with Next.js ecosystems. OpenSign may have feature parity on signing workflows but Documenso has more community momentum and enterprise traction signals.
DocuSeal (17.3k stars, Ruby) leads the open source e-signature segment by star count and has a more established deployment story. It targets a similar SME audience. OpenSign competes directly but currently trails on community size.
Papermark (8.6k stars) solves document sharing and tracking rather than legally binding e-signatures. Overlaps only in document workflow tooling; not a direct competitor for signature use cases.
OpenContracts (1.4k stars) focuses on contract analysis and annotation (NLP-heavy), not signing workflows. Different problem space despite superficial overlap in the 'legal documents' category.
DocuSign remains the reference implementation for enterprise compliance (21 CFR Part 11, eIDAS). OpenSign cannot match its legal certification breadth, Salesforce integrations, or enterprise SLA guarantees, but it eliminates per-envelope costs and gives data ownership — the core trade-off.
