Deploy and Host Documenso (Background jobs supported) on Railway

Documenso is the open-source DocuSign alternative for digital document signing. This template runs Documenso with background jobs supported — pairing the app with PostgreSQL and a Redis-backed BullMQ queue so signing-request emails and document processing run asynchronously. Built from the official Docker image, it deploys a complete, production-ready stack in ~2–3 minutes.

📖 Full deployment guide: Documenso on Railway — step-by-step

About Hosting Documenso (Background jobs supported)

Documenso is a Remix web application backed by PostgreSQL (via Prisma) that handles document uploads, signing workflows, audit trails, and transactional email. Self-hosting it normally means provisioning a database, wiring a job queue for reliable email delivery, generating encryption keys, running migrations, and supplying a signing certificate. This template does that wiring for you: it provisions Postgres and Redis with persistent volumes, generates the encryption and session secrets, runs database migrations automatically on startup, and connects every service over Railway's private network. Documents are stored in PostgreSQL by default — no object storage to configure. The only thing you supply is an SMTP provider so Documenso can email signing links to recipients.

Common Use Cases

Contract and agreement signing — send documents to clients and vendors for legally-binding e-signatures
Internal approvals — route NDAs, HR forms, and policy acknowledgments through a self-hosted workflow
White-label e-signatures — run Documenso on your own domain with your own branding and full data ownership

Dependencies for Documenso (Background jobs supported) Hosting

PostgreSQL 14+ — primary database and default document storage (provisioned by this template)
Redis — backs the BullMQ queue for background email and document processing (provisioned by this template)
SMTP provider — required to send signing-request emails (Resend, SendGrid, AWS SES, Postmark, or any SMTP relay)
Signing certificate — a self-signed certificate is auto-generated for testing; supply your own .p12 for production

Deployment Dependencies

Implementation Details

Most variables are configured automatically — encryption secrets are generated, and the database and Redis URLs are wired across services using Railway's reference syntax:

NEXT_PRIVATE_DATABASE_URL = ${{Postgres.DATABASE_PRIVATE_URL}}
NEXT_PRIVATE_REDIS_URL    = redis://default:${{Redis.REDIS_PASSWORD}}@${{Redis.RAILWAY_PRIVATE_DOMAIN}}:6379
NEXT_PUBLIC_WEBAPP_URL    = https://${{Documenso.RAILWAY_PUBLIC_DOMAIN}}
NEXT_PRIVATE_JOBS_PROVIDER = bullmq

The only values you provide at deploy time are your SMTP credentials: NEXT_PRIVATE_SMTP_HOST, NEXT_PRIVATE_SMTP_USERNAME, NEXT_PRIVATE_SMTP_PASSWORD, and NEXT_PRIVATE_SMTP_FROM_ADDRESS. The Postgres and Redis services come fully pre-configured. After deploy, generate a public domain (the app URL updates automatically), then create your account.

Why Deploy Documenso (Background jobs supported) 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 Documenso (Background jobs supported) on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.