Documenso on Railway
Open-source document signing with audit trails and sealed PDFs, running Documenso v2.20.0 on Railway.
Documenso is an open-source document signing platform. You upload a PDF or Word file, place signature fields, send the document to signers and receive a digitally sealed PDF with an audit trail. It is commonly positioned as a self-hosted alternative to DocuSign, with an API and webhooks for embedding signing in your own product.
Businesses use it for contracts, NDAs, offer letters and internal approvals, and developers use it to keep signed documents and signer data in infrastructure they control.
Documenso is licensed under AGPL-3.0. Enterprise features need a separate Documenso licence key.
What Documenso can do
- Upload PDF or DOCX, place fields and send to signers
- Digitally sealed PDFs with an audit trail
- API and webhooks for embedding signing flows
- E-mail delivery of signing requests and reminders
- Background job queue for e-mails, sealing and webhooks
- Storage of documents in an S3-style bucket
What people use it for
- Sending contracts, NDAs and offer letters without per-envelope fees
- Internal approvals and policy acknowledgements with an audit log
- Embedding signing in your own product through the API
- Keeping signed documents and signer data in your own infrastructure
Videos
Running Documenso on Railway
The Railway template runs Documenso v2.20.0 with Postgres 18, Redis 8.2 for the BullMQ job queue, Gotenberg 8 with LibreOffice so .docx uploads convert to PDF, and a Railway Bucket for uploaded and signed documents. A self-signed signing certificate is created on a volume at first boot, and a first admin account is created with a generated password. The template notes measure about 0.7 GB RAM idle across all services, measured locally rather than on Railway, and RAM is the main driver of cost.
Documenso templates on Railway
Tracklayer templates are listed first. Other Documenso templates follow, ordered by total deployments on Railway. How this works.
Deployment numbers as of 2026-11-20.
Questions about Documenso
How do I log in?
Enter your e-mail in DOCUMENSO_ADMIN_EMAIL when deploying. After first boot, sign in 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 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. You can supply a CA-issued .p12 instead. Whether a self-signed certificate meets your legal needs is a question for your own counsel.
What is the licence?
AGPL-3.0 for the open-source code. Enterprise features need a separate Documenso licence key, which the 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. Because the certificate lives on a volume, run one replica and scale vertically.
Guides
Similar apps
Tracklayer maintains the templates marked as such; Documenso is a trademark of its owners and this site is not affiliated with them.