Documenso v2 Document Signing

Documenso is an open-source document signing platform: upload a PDF or Word file, place fields, send it to signers and receive a digitally sealed PDF with an audit trail. This template runs Documenso v2.20.0 with Postgres, a Redis job queue, DOCX conversion and its own signing certificate.

What you get

  • Documenso v2.20.0 with migrations run as a pre-deploy step
  • Postgres 18 and Redis 8.2 (BullMQ queue for e-mails, sealing, reminders and webhooks)
  • Gotenberg 8 with LibreOffice so .docx uploads convert to PDF
  • A Railway Bucket for uploaded and signed documents
  • A self-signed signing certificate created on a volume at first boot, and a first admin account with a generated password

Good for

  • Sending contracts, NDAs and offer letters for signature without per-envelope fees
  • Internal approvals and policy acknowledgements with an audit log
  • Embedding signing flows in your own product through the API and webhooks
  • Keeping signed documents and signer data in infrastructure you control

Cost

The template notes idle figures measured locally on 2026-10-11, not on Railway: about 0.7 GB RAM in total across Documenso (380 to 470 MB), Postgres, Redis and Gotenberg, and about 0.03 vCPU. RAM is the main driver of usage-based cost.

Services in this template

  • Redis · image redis:8.2
  • Gotenberg · image gotenberg/gotenberg:8.37.0-libreoffice
  • Documenso · from baranberkay96/documenso-railway
  • Postgres · image ghcr.io/railwayapp-templates/postgres-ssl:18

Questions people ask

How do I log in?

Enter your e-mail in DOCUMENSO_ADMIN_EMAIL when deploying. After first boot, sign in at https://{your-domain} with that address and the generated DOCUMENSO_ADMIN_PASSWORD from the Documenso service variables, then change the password in your profile.

Does it send e-mail?

Set NEXT_PRIVATE_RESEND_API_KEY and NEXT_PRIVATE_SMTP_FROM_ADDRESS (an address on a Resend-verified domain) and redeploy; Resend works on every Railway plan, while SMTP works only on Pro. Without e-mail you can copy each recipient's signing link.

What kind of signing certificate is used?

A unique self-signed certificate, kept on the volume and protected by NEXT_PRIVATE_SIGNING_PASSPHRASE, which you must not change afterwards. To use a CA-issued certificate, provide a base64 .p12 in NEXT_PRIVATE_SIGNING_LOCAL_FILE_CONTENTS. Whether a self-signed certificate meets your legal needs is a question for your own counsel.

What is the licence?

Documenso is AGPL-3.0 per the NOTICE file; enterprise features need a separate Documenso licence key, which this template does not use.

How do I upgrade or scale?

Change DOCUMENSO_VERSION in services/documenso/Dockerfile and redeploy; a failed migration leaves the running version untouched. Documenso has a volume for the certificate, so run one replica and scale vertically.

Full template README

Deploy and Host Documenso with Railway

Documenso is an open-source document signing platform: upload a PDF or Word file, place fields, send it to signers, and receive a digitally sealed PDF with a full audit trail. This community template runs Documenso v2 on Railway with Postgres, a Redis job queue, DOCX conversion and its own signing certificate.

About Hosting Documenso

Documenso is a single Node.js web app that needs Postgres, a background job system for e-mails, sealing and webhooks, file storage for documents, and an X.509 certificate to seal completed PDFs. The certificate is the step most self-hosters get stuck on. This template creates a unique self-signed certificate on a volume at first boot, runs migrations as a pre-deploy step, uses BullMQ on Redis for jobs, stores documents in a Railway Bucket, adds Gotenberg so .docx uploads work, and creates your first admin account so you can sign in before any e-mail provider is set up.

Common Use Cases

  • Sending contracts, NDAs and offer letters for signature without per-envelope fees
  • Internal approvals and policy acknowledgements with a tamper-evident audit log
  • Embedding signing flows into your own product through Documenso's API and webhooks
  • Keeping signed documents and signer data in infrastructure you control

Dependencies for Documenso Hosting

  • Documenso (documenso/documenso:v2.20.0 plus a thin Railway layer)
  • PostgreSQL (Railway Postgres 18)
  • Redis (BullMQ job queue)
  • Gotenberg 8 with LibreOffice (DOCX to PDF)
  • S3-compatible storage (Railway Bucket)
  • Optional: a Resend account (or SMTP on Railway Pro) for e-mails

Deployment Dependencies

Implementation Details

Service Image / source Role
Documenso services/documenso (from documenso/documenso:v2.20.0) Web app and API; pre-deploy migrations; signing certificate on a volume; first-admin bootstrap
Postgres ghcr.io/railwayapp-templates/postgres-ssl:18 Database (volume)
Redis redis:8.2 BullMQ queue for e-mails, sealing, reminders and webhooks (noeviction)
Gotenberg gotenberg/gotenberg:8.37.0-libreoffice Converts uploaded .docx files to PDF (private, basic auth)
Bucket Railway Bucket Uploaded and signed documents

First login: enter your e-mail in DOCUMENSO_ADMIN_EMAIL when deploying. After the first boot, sign in at https://{your-domain} with that address and the generated DOCUMENSO_ADMIN_PASSWORD from the Documenso service variables, then change the password in your profile. The account is verified and has admin rights.

E-mail: set NEXT_PRIVATE_RESEND_API_KEY and NEXT_PRIVATE_SMTP_FROM_ADDRESS (an address on a domain verified in Resend) and redeploy; the template switches to Resend automatically. Resend is an HTTP API and works on every Railway plan; SMTP works only on Railway Pro. Without e-mail you can still send by copying each recipient's signing link.

Certificate: the self-signed certificate is created once and kept on the volume, protected by NEXT_PRIVATE_SIGNING_PASSPHRASE. Do not change the passphrase afterwards. To use a CA-issued certificate, provide it as a base64 .p12 in NEXT_PRIVATE_SIGNING_LOCAL_FILE_CONTENTS with its passphrase.

Scaling: scale the Documenso service vertically; Redis-backed jobs keep work durable across restarts. Gotenberg can be given more memory for large Word files.

Versions: change DOCUMENSO_VERSION in services/documenso/Dockerfile and redeploy; migrations run in the pre-deploy step, and a failed migration leaves the running version untouched.

Why Deploy Documenso on Railway?

Railway runs the app, database, queue, converter and storage as one project on a private network, with managed volumes and usage-based billing. You get a complete, production-shaped e-signature service, including a working signing certificate, without running servers or hand-building PKCS#12 files.

Guides for this template

View Documenso v2 Document Signing on railway.com

Similar templates

TemplateCategoryDeploymentsDeploys
Chatwoot
A customer communication platform
Other5,871
Ubuntu-Linux
Ubuntu terminal accessible via web browser
Other4,926
Ubuntu SSH + Claude
ARA TM —SSH server with root access + Claude Code pre-installed.
Other4,682
Debian-Linux
Debian terminal accessible via web browser.
Other2,883
Code Server
VS Code in the browser
Other2,787
Kali Linux (Web Terminal)
Instant Kali Linux browser terminal powered by ttyd
Other2,632