E-signatures on Railway: DocuSeal or Documenso
Short answer: to add document e-signing without DocuSign, self-host an open-source signing platform. On Railway, Tracklayer’s DocuSeal template runs DocuSeal 3.3.6 with Postgres and a document volume. The Documenso template runs Documenso v2.20.0 with Postgres, Redis, a document bucket and a signing certificate. Both let you upload a PDF, place fields, send a link and keep signed files in your own project, with no per-envelope fee.
Deploy DocuSeal on RailwayWhen this makes sense
Both templates list the same core uses:
- sending contracts, NDAs and offer letters for signature without per-envelope fees,
- keeping signed documents and audit logs on infrastructure you control,
- embedding signing links in your own product and receiving results by webhook or API.
DocuSeal adds reusable PDF templates with signature, date, text and checkbox fields. Documenso adds internal approvals and policy acknowledgements with a tamper-evident audit log, and accepts Word files as well as PDFs. On DocuSeal, signers open the link and need no account.
Self-hosting means you run the service and are responsible for backups, updates and legal fit. A hosted vendor handles those for you.
DocuSeal or Documenso
| DocuSeal template | Documenso template | |
|---|---|---|
| Version | DocuSeal 3.3.6 | Documenso v2.20.0 |
| Services | DocuSeal (web, jobs and an embedded Redis in one container), Postgres 18 | Documenso, Postgres 18, Redis 8.2, Gotenberg 8 (Word to PDF), Railway Bucket |
| Document storage | Railway volume | Railway Bucket |
| SMTP only (Pro plans on Railway) | Resend API on any plan; SMTP on Pro | |
| Word uploads | Not mentioned in the template | Yes, converted with Gotenberg |
| Sealing certificate | Created during first-start setup | Self-signed, created at first boot, or your own .p12 |
| Licence | AGPL-3.0 plus attribution term | AGPL-3.0 |
Pick DocuSeal if you want the smaller stack. Pick Documenso if you need Word uploads or e-mail on a non-Pro plan.
Deploy DocuSeal, step by step
These steps use Tracklayer’s DocuSeal template.
- Deploy and wait. The first start takes a little longer because the admin account is created before the public port opens. A fresh DocuSeal normally lets the first visitor create the admin; the template does that on a private port instead.
- Sign in. Use
DOCUSEAL_ADMIN_EMAILandDOCUSEAL_ADMIN_PASSWORDfrom the Variables tab. Change the e-mail under Profile and turn on two-factor authentication. - Send a document. Go to Templates, Upload a PDF, place fields, then Send or copy the share link.
- Set the app URL. If you add a custom domain in Railway, change the app URL under Settings, Account so signing links use it.
- Turn on backups. Enable Railway volume backups for both the DocuSeal and Postgres volumes. Signed files sit on the DocuSeal volume and their records in Postgres.
If you lose the admin password, set DOCUSEAL_ADMIN_PASSWORD and DOCUSEAL_RESET_ADMIN_PASSWORD=true, redeploy, sign in, then set the flag back to false.
Deploy Documenso, step by step
These steps use Tracklayer’s Documenso template.
- Enter your e-mail in
DOCUMENSO_ADMIN_EMAILwhen deploying. - Sign in after first boot with that address and the generated
DOCUMENSO_ADMIN_PASSWORD, then change the password in your profile. - Add e-mail. Set
NEXT_PRIVATE_RESEND_API_KEYandNEXT_PRIVATE_SMTP_FROM_ADDRESS(an address on a domain verified in Resend) and redeploy. Without e-mail you can still copy each recipient’s signing link. - Leave the passphrase alone. The certificate is kept on a volume and protected by
NEXT_PRIVATE_SIGNING_PASSPHRASE; do not change it afterwards. To use a CA-issued certificate, provide a base64 .p12 inNEXT_PRIVATE_SIGNING_LOCAL_FILE_CONTENTS.
What it costs
Railway bills by usage, and both templates are small.
- DocuSeal, measured on Railway: DocuSeal about 180 to 200 MiB of RAM at idle and Postgres about 80 to 110 MiB, with near-zero CPU. That is roughly $3 to $4 per month idle plus volume storage. It also started with a 0.5 GB limit, but very large PDFs or many simultaneous signers need more memory.
- Documenso, measured locally, not on Railway: about 0.7 GB of RAM in total across its four services at idle. The template’s own estimate is about $8 per month idle and about $16 per month for a team sending a few hundred documents a month. These are estimates. The template lists Hobby as the minimum plan.
Limits to know
- Both run as a single replica. Scale by giving the service more memory.
- DocuSeal e-mail needs SMTP, which on Railway means a Pro plan.
- A self-signed certificate is not the same as a certificate from a certificate authority. Check with counsel what your documents need.
- If you modify either project and offer it to others over a network, the AGPL has source-sharing obligations. Read the licence or ask a lawyer.
Other options
Signing links in your own product need somewhere to store accounts and data; see the backend options for vibe-coded apps. To add logins to the rest of your app, see Keycloak on Railway. All guides are listed at /guides/.
FAQ
How do I log in to each one?
DocuSeal: sign in with DOCUSEAL_ADMIN_EMAIL (default admin@example.com) and the generated DOCUSEAL_ADMIN_PASSWORD from the service's Variables tab. There is no shared default password. Documenso: enter your e-mail in DOCUMENSO_ADMIN_EMAIL when deploying, then sign in with the generated DOCUMENSO_ADMIN_PASSWORD from the Documenso service variables.
Can they send signature requests by e-mail on every plan?
Documenso can, through Resend, an HTTP API that works on every Railway plan. DocuSeal sends mail by SMTP only, and Railway allows outbound SMTP only on Pro plans. On other plans with DocuSeal, copy the signing link and send it yourself.
Is a self-signed certificate legally enough?
The Documenso template seals documents with a unique self-signed certificate it creates at first boot. You can supply a CA-issued .p12 instead. Whether either option meets the legal requirements for your contracts and country is a question for your own counsel.
What are the licences?
DocuSeal is AGPL-3.0 with an additional term that keeps the DocuSeal attribution in the user interface; Pro features such as white-label, user roles and SMS verification are not in the open-source edition. Documenso is AGPL-3.0; its enterprise features need a separate Documenso licence key, which the template does not use. Both templates run the upstream images unmodified.
How do I upgrade?
Both versions are pinned. For DocuSeal, change the FROM line (tag and digest) in services/docuseal/Dockerfile, back up, and redeploy. For Documenso, change DOCUMENSO_VERSION in services/documenso/Dockerfile and redeploy; migrations run as a pre-deploy step and a failed migration leaves the running version untouched.