Deploy Sign Documents Without DocuSign Fees — Self-Host DocuSeal on Railway
Self-host DocuSeal: legal e-signatures. No DocuSign per-envelope fees.
Just deployed
/var/lib/postgresql/data
Docuseal
Just deployed
Deploy and Host DocuSeal on Railway
DocuSeal is the open-source e-signature platform with 17k+ GitHub stars — build PDF signing forms with a visual drag-and-drop editor, manage multiple signers, send automatic email reminders, generate audit trails, and embed signing workflows directly into your application via REST API. ESIGN Act, UETA, and eIDAS compliant for legally binding signatures in the US and EU.
DocuSign's median annual contract is $17,250. A 50-person team paying DocuSign per-seat pricing spends $39,000/year. DocuSeal on Railway costs ~$2–5/month — under $60/year. Unlimited documents. Unlimited signatures. No per-envelope fees. Ever.
What This Template Deploys
| Service | Purpose |
|---|---|
| DocuSeal v3.0.2 | The e-signature platform — PDF form builder, signer management, document templates, email notifications, audit trail, API, and embedding on port 3000 |
| PostgreSQL 17 (SSL) | Primary database — documents, templates, signers, submissions, audit logs, and user accounts with persistent volume at /var/lib/postgresql/data |
Single-app architecture. One required environment variable at deploy time. DocuSeal handles all document processing, PDF rendering, email delivery, and storage internally.
About Hosting DocuSeal
Running DocuSeal in production requires a persistent PostgreSQL database for documents and audit logs, a public HTTPS endpoint for signer access links (signers don't need an account — they access documents via a unique URL), and email configuration for signature request notifications. Without a managed host, you're configuring Docker, SSL, volume mounts, and email relay manually.
Railway handles all of it. This template deploys DocuSeal pre-connected to Railway-managed PostgreSQL 17 SSL over private networking, with a public HTTPS domain provisioned automatically — signer links work immediately after deploy.
Typical cost: ~$2–5/month on Railway's Hobby plan. DocuSign starts at $15/user/month for basic features, $45+/user/month for API access. PandaDoc starts at $19/user/month. DocuSeal on Railway gives you unlimited documents, unlimited signers, and full API access at flat compute cost — no per-signature fees, no per-envelope caps, no user seat limits.
Deploy in Under 3 Minutes
- Click Deploy on Railway — DocuSeal and PostgreSQL build automatically (~2–3 minutes)
SECRET_KEY_BASEis auto-generated — the only required variable- Open your Railway-assigned URL — the DocuSeal admin setup wizard loads immediately
- Create your admin account and upload your first PDF to start building a signing workflow
No SSH. No Docker configuration. No database setup.
Common Use Cases
- Replace DocuSign without $17,250/year contracts — self-host legally binding e-signatures on your own Railway instance; no per-envelope fees, no user seat billing, no vendor lock-in on your signed document archive
- GDPR-compliant document signing for EU businesses — signed documents, signer data, and audit trails stay in your Railway PostgreSQL instance within your chosen region; no customer signature data sent to DocuSign's US servers
- Embedded signing for SaaS products — embed DocuSeal's signing widget directly into your application via JavaScript embed or iFrame; signers never leave your product's UI
- Contract automation via REST API — create documents, add signers, and trigger signature requests programmatically from any backend; webhook events notify your system when documents are signed, declined, or expired
- HR onboarding document workflows — build offer letters, NDAs, and employment contracts as reusable templates; assign multiple signers with sequential or parallel signing order and automatic email reminders
- Law firm and legal team document management — generate audit-trail PDFs with digital certificates, timestamp verification, and signer IP logging for each completed document; fully eIDAS compliant for EU legal enforceability
Configuration
| Variable | Required | Description |
|---|---|---|
SECRET_KEY_BASE | ✅ Auto-generated | Rails encryption key — auto-generated at deploy via Railway's ${{secret()}} function |
DATABASE_URL | ✅ Auto-injected | PostgreSQL connection string via Railway reference variable |
DOCUSEAL_BASE_URL | Recommended | Your Railway public domain — required for correct signer link generation |
SMTP_ADDRESS | Recommended | SMTP host for signature request and reminder emails |
SMTP_PORT | Recommended | SMTP port — 587 (TLS) or 465 (SSL) |
SMTP_USERNAME | Recommended | SMTP username from your email provider |
SMTP_PASSWORD | Recommended | SMTP password |
SMTP_FROM | Recommended | Sender address for all DocuSeal emails |
DOCUSEAL_PREMIUM | Optional | Set to true if you have a DocuSeal Pro license key |
PORT | Auto-set | Railway injects the port automatically |
SMTP is strongly recommended. Without email configured, DocuSeal cannot send signing request links to external signers. Use Resend or Brevo for Railway Hobby plan (raw SMTP is blocked; both have free tiers and work via HTTPS-based relay).
DocuSeal vs. Managed E-Signature Platforms
| DocuSeal (Railway) | DocuSign | PandaDoc | HelloSign | |
|---|---|---|---|---|
| Monthly cost | ~$2–5 flat | $15–45+/user | $19–49/user | $15–25/user |
| 50-person team/year | ~$60 | $9,000–$27,000 | $11,400–$29,400 | $9,000–$15,000 |
| Per-envelope fees | ✅ None | ❌ Yes | ❌ Yes (some plans) | ❌ Yes |
| Data ownership | ✅ Your instance | ❌ DocuSign servers | ❌ PandaDoc servers | ❌ Dropbox servers |
| ESIGN / UETA compliant | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes |
| eIDAS compliant | ✅ Yes | ✅ Yes | ✅ Yes | ⚠️ Limited |
| API access | ✅ Included | ❌ Paid plan required | ✅ Paid plans | ✅ Paid plans |
| Embedded signing | ✅ JS/iFrame | ✅ Paid plan | ✅ Paid plan | ✅ Paid plan |
| Open source | ✅ AGPL-3.0 | ❌ No | ❌ No | ❌ No |
| Self-hostable | ✅ Yes | ❌ No | ❌ No | ❌ No |
Dependencies for DocuSeal Hosting
- Railway account — Hobby plan (~$2–5/month) for DocuSeal and PostgreSQL
- SMTP provider for signature request emails — Resend or Brevo recommended (both have free tiers; raw SMTP is blocked on Railway Hobby)
Deployment Dependencies
- DocuSeal GitHub Repository — source and releases
- DocuSeal Documentation — API and configuration reference
- DocuSeal REST API Reference — full API documentation
- Resend — recommended SMTP (3,000 free emails/month)
Implementation Details
DocuSeal v3.0.2 deploys alongside Railway-managed PostgreSQL 17 SSL over private networking.
SECRET_KEY_BASE is auto-generated — the only manual variable at deploy time. All documents,
templates, signer data, and audit logs persist in PostgreSQL independently of the container.
Set DOCUSEAL_BASE_URL to your Railway domain immediately after deploy — without it,
signing URLs sent to external signers will point to localhost and fail to load.
Frequently Asked Questions
How much does DocuSeal cost compared to DocuSign? DocuSeal on Railway runs at ~$2–5/month. Vendr's 2026 benchmark puts the median DocuSign annual contract at $17,250 — a 50-person team can save $39,000/year. DocuSign's retail plans start at $15/user/month for basic features; API access requires the $45+/user plan. DocuSeal gives you the full API, embedded signing, and unlimited documents at flat compute cost.
Are DocuSeal signatures legally binding? Yes. DocuSeal is compliant with the US ESIGN Act, UETA, and EU eIDAS regulations for legally binding electronic signatures. Each completed document includes an audit trail PDF with signer timestamps, IP addresses, and digital certificate verification.
Do signers need a DocuSeal account? No. Signers receive a unique URL by email and complete the signing process directly in their browser without creating an account. Only document senders need a DocuSeal account.
Is my document data private? Yes. All documents, signed PDFs, signer data, and audit trails are stored in your Railway PostgreSQL instance. DocuSeal does not send document content to any external service. This makes DocuSeal suitable for GDPR-regulated customer contracts and HIPAA-eligible healthcare documents on self-hosted infrastructure.
Can I embed DocuSeal signing into my application? Yes. DocuSeal supports JavaScript embed and iFrame embedding for inline signing within your application. The API allows you to create signing sessions programmatically and receive webhook events when signers complete, decline, or expire. Full API documentation is at docuseal.com/docs/api.
How do I update DocuSeal to a newer version?
Update the image tag in Railway service settings to the latest release (e.g.
docusealco/docuseal:3.0.2) and redeploy. Your PostgreSQL data — documents, templates,
and audit logs — is unaffected by version updates.
Why Deploy and Host DocuSeal on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying DocuSeal on Railway, you get a legally binding, ESIGN/UETA/eIDAS-compliant e-signature platform — unlimited documents, full API access, embedded signing, and audit trails — at ~$2–5/month with no per-envelope fees and full ownership of every signed document your business creates.
Template Content