Open source DocuSign alternative. Create, fill, and sign digital documents ✍️
17.5k
Stars
1.7k
Forks
121
Open issues
6
Contributors
AI Analysis
DocuSeal is an open-source platform for creating, filling, and signing PDF documents digitally, positioning itself as a self-hosted alternative to DocuSign. It serves organizations and developers who need e-signature capabilities with full control over data and deployment, benefiting companies seeking privacy-conscious document workflows and developers building document signing into larger applications. It is not a general-purpose document editor but a specialized signing and form-filling pla...
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.
Self-hosted document signing platform targeting businesses that need DocuSign-like features without SaaS lock-in
DocuSeal is an open source, self-hostable platform for creating, filling, and signing PDF documents digitally. It targets SMBs, developers building document workflows into products, and organizations in regulated industries (banking, healthcare, real estate) that need e-signature infrastructure without per-seat SaaS pricing. The project ships a WYSIWYG form builder, multi-party signing flows, API/webhooks, and embeddable signing components. A cloud SaaS tier and Pro features add commercial sustainability. With 17K+ stars and active maintenance as of mid-2026, it is among the more mature open source e-signature tools.
Created in July 2023 by DocuSeal LLC, the project emerged during a wave of open source alternatives to expensive SaaS document tools. It reached meaningful star counts within months, suggesting strong latent demand for self-hosted e-signature infrastructure.
Growth appears driven by developer and DevOps communities seeking self-hosted alternatives to DocuSign and HelloSign, amplified by HackerNews and Product Hunt visibility typical for open-source SaaS alternatives. The steady ~100+ stars/week in mid-2026 suggests sustained organic discovery rather than a single viral spike. Multiple one-click deploy integrations (Heroku, Railway, DigitalOcean, Render) lowered the adoption barrier significantly.
Docker Hub image versioning is publicly visible (badge in README), suggesting real deployment activity. The existence of a live demo, a commercial cloud tier, and industry-specific sales outreach (banking, healthcare, transport) suggests paying customers exist, though exact user counts or deployment volumes are not publicly disclosed. Adoption not independently verified at scale.
Likely a Ruby on Rails monolith based on the Ruby language tag. Appears to use SQLite as default storage with PostgreSQL/MySQL support via DATABASE_URL, and supports S3-compatible object storage for files. Docker-first deployment with Caddy for TLS suggests a well-considered self-hosting story. Embeddable components exist as separate React/Vue/Angular packages, implying an API-first design for the signing UI.
Not documented in README.
Last push was June 22, 2026 — four days before evaluation date — indicating active, ongoing development. The project has been continuously maintained since 2023. The README references 2023-2026 copyright and an evolving Pro feature set, consistent with a commercially backed open source project.
ADOPT IF: you need a self-hosted or embeddable e-signature solution, have Ruby/Docker infrastructure comfort, want to avoid per-signature SaaS costs, and your compliance requirements can be met by AGPL software without third-party certification. AVOID IF: you require SOC 2, eIDAS advanced signatures, or legally certified audit trails out of the box, or if your organization prohibits AGPL-licensed software in products. MONITOR IF: you are evaluating open source e-signature tooling but need to see how Pro features, compliance posture, and community governance evolve over the next 12 months.
Independent dimensions
Mainstream potential
6/10
Technical importance
7/10
Adoption evidence
5/10
- AGPL-3.0 with additional Section 7(b) terms creates legal complexity for SaaS products built on top of DocuSeal — commercial use may require a paid license, which some organizations may not discover until late in evaluation.
- Key features (SSO, embedded signing, bulk send, conditional fields) are locked behind the Pro tier, meaning the open source version may be insufficient for production enterprise use without a commercial agreement.
- Single-company controlled project (DocuSeal LLC) — governance, roadmap, and long-term open source commitment depend entirely on that company's commercial success and priorities.
- E-signature legal compliance (eIDAS, ESIGN Act, UETA) varies by jurisdiction and use case; DocuSeal does not appear to advertise certified compliance, which may limit use in legally sensitive document workflows.
- Ruby on Rails stack may limit the contributor pool compared to TypeScript or Go alternatives, potentially slowing community-driven development if commercial interest wanes.
DocuSeal is likely to consolidate as the leading self-hosted e-signature tool in the Ruby/Docker ecosystem and grow its commercial SaaS tier steadily. It is unlikely to displace commercial incumbents in regulated enterprise markets without third-party compliance certifications.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://www.docuseal.com
- Language
- Ruby
- License
- AGPL-3.0
- Last updated
- 4d ago
- Created
- 37mo 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
Top contributors
Recent releases
Similar repos
documenso/documenso
Documenso is an open-source, self-hostable alternative to DocuSign for digital...
OpenSignLabs/OpenSign
OpenSign is a self-hosted, open-source alternative to DocuSign that enables...
Euro-Office/DocumentServer
Euro-Office DocumentServer is a sovereign, self-hosted office suite component...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
docusealco/docuseal
this
|
17.5k | +127 | Ruby | 8/10 | 4d ago |
|
documenso/documenso
|
13.7k | — | TypeScript | 7/10 | 12h ago |
|
OpenSignLabs/OpenSign
|
6.6k | — | JavaScript | 7/10 | 2d ago |
 papermark/papermark
|
8.8k | — | TypeScript | 7/10 | 2d ago |
|
Euro-Office/DocumentServer
|
1.6k | — | Shell | 6/10 | 2d ago |
 Stirling-Tools/Stirling-PDF
|
86.7k | — | Java | 9/10 | 6 min ago |
TypeScript-based alternative with 13.5K stars, also AGPL-licensed. Documenso has a strong open-source community focus and recently raised funding. DocuSeal has more stars and a longer feature list including embedded components, but Documenso may appeal more to TypeScript-native teams and has growing enterprise backing.
JavaScript-based with 6.5K stars. Appears less mature and less feature-complete than DocuSeal. DocuSeal's broader language support, Pro tier, and more polished deploy story give it a practical edge for production use.
The dominant commercial incumbent. DocuSign offers legally certified workflows, enterprise compliance, and deep integrations. DocuSeal cannot fully match compliance certifications (eIDAS, SOC 2) without significant additional effort, but costs far less for high-volume use cases where self-hosting is acceptable.
Not a direct competitor — focuses on PDF manipulation rather than signing workflows. Users needing both PDF editing and signing may deploy both tools together. Stirling-PDF's 84K stars reflect a different, broader use case.
Commercial SaaS with established compliance certifications and enterprise support. DocuSeal is a viable alternative for teams with technical resources to self-host and where SaaS pricing is prohibitive, but lacks the compliance paperwork trail these services provide.
