Deploy and Host n8n Queue Stack with Workers on Railway

n8n queue execution with Postgres, private Redis and a separate worker.

About Hosting n8n Queue Stack with Workers

This deployment fork provisions Primary, Worker, Redis, Postgres. Application domains and any authored TCP endpoints are generated for each new deployment. Database and queue services are private by default.

Why Deploy n8n Queue Stack with Workers on Railway

New setup and maintenance documentation with attribution to the original template.
Public container sources are locked by image digest and public Git repositories by commit SHA.
Database and queue services use private networking; external database access is an explicit deployer choice.
Explicit persistent encryption key, current webhook/proxy settings and bounded execution retention.

Common Use Cases

Execute integration workflows outside the editor process.
Handle webhook-driven automation.
Run scheduled and manual workflow jobs on a worker.

Dependencies for n8n Queue Stack with Workers

A Railway account with capacity for 4 service definitions and the authored storage.
Your own external accounts and credentials when an integration or model provider is needed. No paid provider subscription is included.
Local passwords and service secrets are generated or referenced at deployment; external integrations are configured by the deployer.

First Launch

Wait for PostgreSQL, Redis, Primary and Worker. Open the Primary domain and create the owner account immediately. Connect your integrations. Keep Worker running for queued jobs.

Included Services and Storage

Service	Persistent paths
Primary	No attached volume
Worker	No attached volume
Redis	`/data`
Postgres	`/var/lib/postgresql/data`

Operations

Primary and Worker reference one encryption key and the same database/queue. Back up PostgreSQL and retain that key. Scale workers only after reviewing n8n queue and binary-data requirements.

Railway bills the deployer for actual services, storage and network use. Back up persistent data before source/version changes. This publication was checked against Railway's configuration schema and upstream source/registry availability; a full runtime deployment test has not been performed.

Attribution and Source

Based on N8N (w/ workers) by Jack. It appeared at position 3 in Railway's backend Popular/browse results captured on 2026-10-18, with 81,258 deployments reported for the original. That count belongs to the original, not this new fork.

The original software and repositories remain owned by their upstream authors and retain their licenses. This is a deployment configuration fork with new documentation, not a claim of software authorship or official vendor affiliation.

For template wiring issues, use this template's discussion link and share redacted logs. Never post passwords, API keys or login tokens.

Deploy this recipe

Review the required inputs and hosting resource costs before deploying.

Related deployment recipes

ntfy Private Notifications with Persistent Data — Private push notifications with generated admin and persistent storage.
n8n with PostgreSQL & Durable Storage — Workflow automation with private Postgres, durable files and webhook URLs.
Uptime Kuma with Persistent Storage — Uptime checks, alerts and status pages with persistent monitor data.

These are separate deployments; no preconfigured integration between the applications is implied.

Disclosure: this template is maintained independently. Its maintainer may earn Railway usage kickbacks when other people deploy it. Railway bills hosting separately; no paid software subscription or provider credits are included.