Documenso Self-Hosted
Self-hosted electronic-signature and document workflow application with a Railway deployment path.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Official Railway template or manual Railway deployment from the upstream repository
Runs in
Documented customer environment
Application service with PostgreSQL, SMTP, signing configuration and persistent document data
- Railway: Customer platform workspace
- Railway
Servers / containers
Operated by
Your team
Customer manages the Railway project, application secrets, PostgreSQL recovery, SMTP, signing certificates, domains, access controls, data retention and upgrades; Railway operates the platform.
Deployment boundaries by provider
- Railway: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Documenso deployment in a Railway project ↗ · Source checked 2026-11-15
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Official Railway template or manual Railway deployment from the upstream repository |
|---|---|
| Infrastructure | Servers / containers The Railway deployment runs a long-lived application service and PostgreSQL database, with SMTP and persistent document data. |
| Licensing model | Open Source / Open Core Documenso Community Edition is AGPL-3.0. Enterprise Edition uses a separate commercial license; confirm the selected edition and AGPL obligations for modifications and network use. |
| License | AGPL-3.0 Community Edition; Enterprise Edition uses a commercial license. |
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.
4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
Organisation 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.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The 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 / sizing
The 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 pricing
Community 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.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- 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.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
The 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.
Community & maintenance
Documenso release v2.22.0 was published on November 13, 2026, and its public contributor history shows continuing upstream participation. This evidence applies to the open-source project, not to paid Enterprise support or the longevity of the Railway template.
Category fit
- Workflow automation
- Automates document preparation, signing requests, recipient completion and status-driven electronic-signature workflows through a self-hosted application.
Compare within Workflow automation
- Activepieces Self-HostedSelf-hosted workflow automation platform with integrations, triggers, actions and worker execution.
- AWS
- Google Cloud
- Railway
- Apryse FluentCustomer-hosted document-template management and rendering software for automated business output.
- AWS
- Azure
- Camunda 8 Self-ManagedCommercial self-managed process orchestration and workflow automation platform.
- AWS
- Azure
- Google Cloud
- CloudBolt Cloud Management PlatformSelf-hosted cloud-management and infrastructure-automation platform deployed as a customer-operated appliance.
- AWS
- Azure
- CortezaLow-code platform for business records, workflows and configurable CRM applications.
- Hostinger
- Decisions Self-HostedCommercial rules and workflow platform with provider-specific container deployments.
- AWS
- Azure
- Google Cloud
- DocuSeal Self-HostedSelf-hosted document forms and electronic-signature workflows with API and webhook integration.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Railway
- Render
- Heroku
- Linode
- Vultr
- Hostinger
- LumaDock
- DocuWare On-PremiseCustomer-operated document repository, email capture and document-workflow platform on Azure VMs.
- Azure
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
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Documenso Railway deployment ↗docs.documenso.com
- Documenso deployment options ↗docs.documenso.com
- Community and Enterprise licenses ↗docs.documenso.com
- Reviewed release v2.22.0 ↗github.com
- Upstream contributor history ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Documenso deployment in a Railway project ↗ · Railway
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
Documenso's official documentation provides an official Railway template and a manual project workflow that provisions the application service and managed PostgreSQL, configures secrets and networking and exposes the customer's deployment URL. The page identifies the guide as a community contribution that may become outdated. This is community-contributed deployment guidance published in the upstream documentation, not a verified vendor support commitment.
- Documenso deployment in a Railway project ↗ · Railway
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Reviewed release v2.22.0 ↗github.com
- Upstream contributor history ↗github.com