DocuSeal vs Documenso: customer-cloud evaluation
Test your actual signing ceremony, template import, identity checks, PDF fidelity, evidence export and SMTP delivery. Validate paid SSO rights and database/attachment restoration separately.
FormKiQ publishes this directory. This comparison records reviewed evidence, not a feature score or support certification.
| Field | DocuSeal Self-Hosted | Documenso Self-Hosted |
|---|---|---|
| Documented clouds | AWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock, Azure, Google Cloud, Railway, Heroku, Render | Railway |
| Deployment model | Customer-operated | Customer-operated |
| Infrastructure | Servers / containersInfrastructure scopeWeb application containers and document-processing jobs with durable database and attachment storage on Cloudron or managed application platforms. Cloud Run container hosting does not establish event-driven function deployment support. | Servers / containersInfrastructure scopeThe Railway deployment runs a long-lived application service and PostgreSQL database, with SMTP and persistent document data. |
| Install | Vendor Azure, Google Cloud, DigitalOcean, Railway, Heroku and Render deployment paths, or a Cloudron package on a customer VM. | Official Railway template or manual Railway deployment from the upstream repository |
| License | AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms. | AGPL-3.0 Community Edition; Enterprise Edition uses a commercial license. |
| Operations | Read requirements and scopeCustomer manages administrator access, signing workflows, HTTPS, secrets, database networking, mail, durable attachment storage, database/file/key recovery and image upgrades. Platform providers operate the underlying managed services. For 3.3.8 security remediation, restart every Ruby web and background process after deployment. | Read requirements and scopeCustomer manages the Railway project, application secrets, PostgreSQL recovery, SMTP, signing certificates, domains, access controls, data retention and upgrades; Railway operates the platform. |
| Notes | Read requirements and scopeReviewed core 3.3.7 includes security hardening, bug fixes, and performance improvements. The separately reviewed Cloudron package snapshot is 1.21.3 with core 3.3.6; pin a current image and confirm package lag before upgrading. Back up the database and attachments, and preserve SECRET_KEY_BASE. Native deployment examples need production configuration: restrict database access and configure durable storage; Heroku/Render app filesystems are ephemeral, and the free Render database expires. Paid features require appropriate entitlements; Pro uses a license/usage connection to DocuSeal. Qualified electronic signatures are not available in the on-premises edition. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations. DocuSeal 3.3.8 fixes GHSA-78g6-f52x-q3jx, a High-severity unauthenticated denial of service in Ruby versions used by earlier DocuSeal builds. Versions before 3.3.8 are affected and no workaround is documented. Upgrade, restart every Ruby web and background process, and verify all workers use the updated runtime. | Read requirements and scopeThe official Railway page labels its instructions as a community contribution that may become outdated. Confirm the current upstream image or source revision and template before deployment. Production signing requires correctly protected encryption keys, SMTP and signing-certificate configuration. This entry covers signing workflow automation, not full contract lifecycle management. |
| Marketplace delivery | AvailableEvidence and scope for Marketplace deliveryAWS delivery uses Cloudron’s platform AMI and a separate application package. Cloudron publishes the platform offer; application versions, licensing and support are separate. Cloudron platform plus separate application package · Source ↗ · Cloudron application package ↗ · Offer prodview-aep3gt5elubci ↗ — Cloudron UG; Platform AMI; external Cloudron license; package Cloudron 10.0.5 (platform, not application) · Reviewed 2026-11-14 Documented · Editor reviewed. | Not researched Supply a public source. |
| Single sign-on | Edition-dependentEvidence and scope for Single sign-onSAML SSO appears in the self-hosted Pro feature list. It is not established here for the free edition. Self-hosted Pro · Source ↗ · Reviewed 2026-11-14 Edition-dependent · Editor reviewed. | Edition-dependentEvidence and scope for Single sign-onOrganisation SSO supports OIDC identity providers and is explicitly Enterprise-only. An organisation admin/manager configures the redirect, scopes, issuer, client credentials, allowed domains and default role; the self-hosting guide confirms enterprise features require a licence key. Self-hosted Enterprise organisation user SSO; distinct from individual social sign-in and signer authentication · Source ↗ · Self-hosted Enterprise activation ↗ · Reviewed 2026-11-20 Edition-dependent · Editor reviewed. |
| Security controls | DocumentedEvidence and scope for Security controlsGHSA-78g6-f52x-q3jx affects DocuSeal before 3.3.8. A single unauthenticated request can crash a Ruby application worker before routing or authentication. No workaround is documented; update and restart every web and background process. DocuSeal versions earlier than 3.3.8 · Source ↗ · 3.3.8 security release ↗ · Reviewed 2026-11-19 Documented · Editor reviewed. | Not researched Supply a public source. |
| Deployment artifact / IaC | DocumentedEvidence and scope for Deployment artifact / IaCThe upstream Compose example defines DocuSeal, PostgreSQL and Caddy with persistent storage. It uses moving application/proxy images and example database credentials; pin compatible versions and replace credentials before deployment. Upstream Compose example; not a hardened production baseline · Deployment artifact ↗ (master (moving branch)) · Reviewed 2026-11-14 Documented · Editor reviewed. | DocumentedEvidence and scope for Deployment artifact / IaCThe Railway guide supplies a one-click application/PostgreSQL template and manual setup. It is explicitly a community contribution that may be outdated. SMTP credentials are required for signing-request email; validate the deployed version and configuration. Documenso Railway community-contributed deployment guide · Source ↗ · Reviewed 2026-11-16 Documented · Editor reviewed. |
| Minimum footprint / sizing | DocumentedEvidence and scope for Minimum footprint / sizingThe vendor sizes examples for 10,000 signed documents. For one-off templates with one signer and 500-KB average files it lists 1 vCPU, 1 GB RAM and 12 GB disk; larger files, reused templates and multiple signers have different storage needs. PostgreSQL is recommended for heavy production/API use. Approximate document-based examples, not a 1-TB or HA installation baseline · Source ↗ · Reviewed 2026-11-20 Documented · Editor reviewed. | DocumentedEvidence and scope for Minimum footprint / sizingThe current requirements distinguish testing/development (1 core, 1 GB RAM, 10 GB storage) from recommended production (2+ cores, 2+ GB RAM, 20+ GB storage). PostgreSQL, email delivery, a signing certificate and HTTPS are required; document storage and optional conversion services need separate planning. Current general self-hosting guidance, not a backdated v2.22.0 specification or an HA/1-TB capacity guarantee · Source ↗ · Reviewed 2026-11-20 Documented · Editor reviewed. |
| License pricing | DocumentedEvidence and scope for License pricingThe 3.3.8 core is AGPLv3. The on-premises page offers free self-hosting and separately prices Pro at $240 per user/year plus $0.20 per document signed through API or embedding. Confirm billable user/document definitions, currency and current terms before quoting. Self-hosted core versus paid Pro; advertised amounts are not a 100-user total or infrastructure cost · Source ↗ · Versioned core licence ↗ · Reviewed 2026-11-20 Documented · Editor reviewed. | DocumentedEvidence and scope for License pricingCommunity Edition is AGPL-3.0, with the v2.22.0 licence available in the repository. Enterprise Edition uses commercial terms and a licence key for enterprise features. Obtain a self-hosted entitlement and price for the selected features rather than applying hosted subscription prices. Community versus commercial enterprise licensing; software fees exclude hosting, signing certificates and operations · Source ↗ · Versioned licence ↗ · Reviewed 2026-11-20 Documented · Editor reviewed. |
| Release snapshot / cadence | DocumentedEvidence and scope for Release snapshot / cadenceDocuSeal 3.3.8 was published November 19, 2026. It updates Ruby to address GHSA-78g6-f52x-q3jx; all web and background processes must be restarted so the fixed runtime is active. Upstream DocuSeal core release; separately packaged provider images may lag · Source ↗ · Prior reviewed release context ↗ · Security advisory ↗ · Reviewed 2026-11-19 Documented · Editor reviewed. | Not researched Supply a public source. |