DocuSeal Self-Hosted

Self-hosted document forms and electronic-signature workflows with API and webhook integration.

  • AWS
  • Azure
  • Google Cloud
  • DigitalOcean
  • Railway
  • Render
  • Heroku
  • Linode
  • Vultr
  • Hostinger
  • LumaDock
Customer-operated Servers / containers Open Source / Open Core

41 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

DocuSeal 3.3.8 unauthenticated denial-of-service fix

GHSA-78g6-f52x-q3jx allows one unauthenticated request to crash a Ruby application worker before routing or authentication.

Scope: DocuSeal versions earlier than 3.3.8.

Every web and background process still using the affected Ruby runtime remains exposed; the advisory documents no workaround.

Action: Upgrade to 3.3.8 or later, restart every Ruby process and verify the active runtime.

Primary source · 3.3.8 security release · Reviewed 2026-11-19

What lands where

  1. Supplied by

    Vendor or project

    Vendor Azure, Google Cloud, DigitalOcean, Railway, Heroku and Render deployment paths, or a Cloudron package on a customer VM.

  2. Operated by

    Your team

    Customer 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.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodVendor Azure, Google Cloud, DigitalOcean, Railway, Heroku and Render deployment paths, or a Cloudron package on a customer VM.
InfrastructureServers / containers
Web 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.
Licensing modelOpen Source / Open Core
AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms. Cloudron packaging and platform plans have separate terms; the application license does not grant a free platform subscription.
LicenseAGPL-3.0 core; Pro features and the private Pro image use separate commercial terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

7 of 12 fields researched (58%) · 7 documented · 0 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
AvailableEvidence and scope for Marketplace delivery

AWS 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.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

SAML 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.

Security controls
DocumentedEvidence and scope for Security controls

GHSA-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.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The 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.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The 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.

License pricing
DocumentedEvidence and scope for License pricing

The 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.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

DocuSeal 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.

Show all fields (5 not researched)
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

Reviewed 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.

Community & maintenance

The current core has sustained work by two principal maintainers, external code contributions and continuing security releases. Public contributor and release histories establish ongoing maintenance; they do not independently validate every paid feature or customer deployment.

Category fit

Workflow automation
Automates document form filling, signature collection and completion workflows through a self-hosted application, API and webhooks. This does not establish full contract lifecycle management or regulated-record compliance.

Compare within Workflow automation

  • Activepieces Self-HostedSelf-hosted workflow automation platform with integrations, triggers, actions and worker execution.
    • AWS
    • Google Cloud
    • Railway
    Customer-operated · Open Source / Open Core
  • Apryse FluentCustomer-hosted document-template management and rendering software for automated business output.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • Camunda 8 Self-ManagedCommercial self-managed process orchestration and workflow automation platform.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • CloudBolt Cloud Management PlatformSelf-hosted cloud-management and infrastructure-automation platform deployed as a customer-operated appliance.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • CortezaLow-code platform for business records, workflows and configurable CRM applications.
    • Hostinger
    Customer-operated · Open Source / Open Core
  • Decisions Self-HostedCommercial rules and workflow platform with provider-specific container deployments.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Documenso Self-HostedSelf-hosted electronic-signature and document workflow application with a Railway deployment path.
    • Railway
    Customer-operated · Open Source / Open Core
  • DocuWare On-PremiseCustomer-operated document repository, email capture and document-workflow platform on Azure VMs.
    • Azure
    Customer-operated · Commercial Only

Showing 8 of 25 other listings in Workflow automation. These products address related workflows; read their category-fit notes before comparing scope. See all of Workflow automation →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Cloudron EC2 AMI and application installation ↗ · AWS

      Marketplace offer · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.

    • Cloudron customer Droplet deployment ↗ · DigitalOcean

      Marketplace offer · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.

    • Cloudron customer Linode deployment ↗ · Linode

      Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.

    • Cloudron named-provider installation and Marketplace availability ↗ · Vultr

      Package platform documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established. Cloudron currently names the Vultr Marketplace offer; use current Cloudron OS requirements, not the historical Ubuntu 20.04 tutorial.

    • Hostinger customer VPS Cloudron template ↗ · Hostinger

      Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.

    • LumaDock customer VPS Cloudron template ↗ · LumaDock

      Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.

    • Vendor Azure Web Apps deployment ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      Installs the actual application container in a customer Azure resource group with PostgreSQL and Blob Storage. Configure secrets, storage and production database network restrictions rather than retaining permissive example firewall rules.

    • Vendor Google Cloud Run deployment ↗ · Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      Installs the actual application container in a customer project with Cloud SQL and Google Cloud Storage. Configure keys, bucket access and production database network restrictions. This is application hosting, not a storage-only integration.

    • Vendor DigitalOcean application specification ↗ · DigitalOcean

      Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      Creates the vendor application container and PostgreSQL in a customer App Platform account. Database persistence does not preserve attachments: configure durable object storage and back up both. Pin the application image and configure real mail.

    • Vendor-linked Railway application template ↗ · Railway

      Community template · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      Installs the vendor application and PostgreSQL in a customer Railway project. The database volume alone does not preserve attachments: configure an application volume at the image data path or durable object storage. Review secrets, SMTP and backups.

    • Vendor Heroku application specification ↗ · Heroku

      Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      Creates a container application and PostgreSQL add-on in a customer Heroku account. Dyno filesystems are ephemeral: configure durable object storage for documents, retain encryption keys and back up the database.

    • Vendor Render application blueprint ↗ · Render

      Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      Creates the application and PostgreSQL in a customer Render account. The example selects free services; Render does not recommend those for production and the free database expires after 30 days. Use suitable paid compute/database, durable attachment storage, secrets and working outbound mail.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory