
N8N+Worker+Pgbouncer+Postgres+Valkey : 1$
Enterprise n8n Workflow Automation Stack
pgbouncer
antisofisme/railway
Just deployed
valkey
antisofisme/railway
Just deployed
/data
n8n-worker
antisofisme/railway
Just deployed
n8n-main
antisofisme/railway
Just deployed
postgres
antisofisme/railway
Just deployed
/var/lib/postgresql/data
Enterprise n8n Workflow Automation Stack
What You Get
A complete production-ready n8n deployment with distributed architecture, optimized databases, and high-performance caching - all pre-configured for maximum performance and reliability.
Components:
- n8n Main: Primary workflow editor and API service
- n8n Worker: Dedicated execution engine for intensive workflows
- PostgreSQL: Enterprise-grade database with optimized settings
- PgBouncer: Advanced connection pooling for better database performance
- Valkey: High-performance Redis-compatible caching layer
Key Features
- ✅ Distributed Architecture: Separate worker processes for handling high-volume executions
- ✅ High Concurrency: Optimized for 500+ simultaneous workflow executions
- ✅ Enterprise-Ready: Full redundancy with separated services
- ✅ Performance Tuned: Memory allocation and database parameters pre-optimized
- ✅ Secure: SSL/TLS enabled by default with proper authentication
- ✅ IPv6 Compatible: Full support for Railway's advanced networking
Usage Instructions
- Deploy Template: One-click deployment sets up the complete stack
- Important: Configure the n8n-main service to expose port 5678 in Railway settings
- Access n8n: Use the public URL to access your workflow editor
- Create Workflows: Build your automations with confidence in the infrastructure
Environment Variables
- n8n Editor URL:
https://${{n8n-main.RAILWAY_PUBLIC_DOMAIN}}
- Database configuration: Pre-connected via internal service discovery
- Worker scaling: Adjustable through environment variables
Technical Specifications
- n8n Main & Worker nodes with optimized memory allocation (port 5678)
- PostgreSQL with connection pooling via PgBouncer
- Valkey (Redis-compatible) for queue management and caching
- Pre-configured for high-throughput AI agent workloads
- Advanced logging configuration with minimal noise
Important Note
If you cannot access the n8n interface after deployment, ensure that the n8n-main service has its port explicitly set to 5678 in the Railway service settings.
Important: Configuring Public Access
After deploying the template, you MUST configure the port for n8n-main service:
- In your Railway project, select the n8n-main service
- Navigate to the Settings tab
- Under Public Networking, click to expand
- You will see a dropdown for port selection - choose 5678
- Click Update to save your port configuration
Without this port configuration, the n8n interface will not be accessible from the public URL.
Your n8n instance will then be accessible at the URL shown in the Public Networking section.
Support me if you think this is good, one dollar is also very valuable to me, I'm really broke man. https://linktr.ee/givemesomehope
Template Content
pgbouncer
antisofisme/railwayvalkey
antisofisme/railwayn8n-worker
antisofisme/railwayn8n-main
antisofisme/railwaypostgres
antisofisme/railway