Self-Hosting n8n

Deploy your own n8n instance with Railway - the fastest way to production

What’s the Fastest Way to Deploy n8n to Production?

Railway provides the quickest deployment path - one-click setup with Redis, PostgreSQL, and workers included, getting you production-ready in just 2 minutes.

The fastest way to get n8n running in production is through Railway. It handles all the infrastructure complexity and gets you running in just 2 minutes.

Why Should I Choose Railway for n8n Hosting?

Railway is recommended because it offers one-click deployment, automatic SSL, managed databases, auto-scaling, built-in monitoring, and easy updates - all without configuration.

Railway is the recommended deployment method because it provides:

• One-click deployment - No configuration needed
• Automatic SSL - HTTPS out of the box
• Managed databases - PostgreSQL and Redis included
• Auto-scaling - Handles traffic spikes
• Built-in monitoring - See logs and metrics
• Easy updates - Redeploy with one click

How Do I Set Up n8n on Railway?

You only need a GitHub account to get started. Railway handles the rest automatically through their template system.

Prerequisites

• Sign up for Railway at railway.com
• GitHub account for authentication

Step-by-Step Deployment

1. Click Deploy Button

   • Use the deploy button above
   • Or visit railway.com/new/template/n8n-with-workers

2. Authorize Railway

   • Sign in with GitHub
   • Authorize Railway to create repositories

3. Deploy Template

   • Click “Deploy” on the n8n template
   • Railway automatically provisions:
     • Redis for queues
     • PostgreSQL for data
     • n8n primary instance
     • n8n worker instances

4. Access Your Instance

   • Go to Railway dashboard
   • Click on “Primary” service
   • Navigate to Settings → Network
   • Click “Generate Domain”
   • Access your n8n at the provided URL

5. Set Admin Credentials

   • In Railway dashboard, go to Variables
   • Set these environment variables:
   N8N_BASIC_AUTH_ACTIVE=true
   N8N_BASIC_AUTH_USER=your_username
   N8N_BASIC_AUTH_PASSWORD=your_secure_password
   
   • Redeploy for changes to take effect

What If I Want More Control Over My Deployment?

Docker Compose gives you full control over your n8n deployment with PostgreSQL and Redis, perfect for teams who want to manage their own infrastructure.

If you prefer more control over your deployment, use Docker Compose:

version: '3.8'

services:
  postgres:
    image: postgres:15-alpine
    environment:
      POSTGRES_USER: n8n
      POSTGRES_PASSWORD: n8n
      POSTGRES_DB: n8n
    volumes:
      - postgres_data:/var/lib/postgresql/data

  redis:
    image: redis:7-alpine
    volumes:
      - redis_data:/data

  n8n:
    image: docker.n8n.io/n8nio/n8n
    ports:
      - "5678:5678"
    environment:
      - DB_TYPE=postgresdb
      - DB_POSTGRESDB_HOST=postgres
      - DB_POSTGRESDB_DATABASE=n8n
      - DB_POSTGRESDB_USER=n8n
      - DB_POSTGRESDB_PASSWORD=n8n
      - QUEUE_BULL_REDIS_HOST=redis
      - N8N_BASIC_AUTH_ACTIVE=true
      - N8N_BASIC_AUTH_USER=admin
      - N8N_BASIC_AUTH_PASSWORD=changeme
    volumes:
      - n8n_data:/home/node/.n8n
    depends_on:
      - postgres
      - redis

volumes:
  n8n_data:
  postgres_data:
  redis_data:

Run with:

docker-compose up -d

What Should I Configure After Deployment?

After deployment, configure your webhook URL, enable execution pruning to keep your database clean, and set your timezone for accurate scheduling.

Configure Webhook URL

After deployment, configure your webhook URL:

1. In Railway or your deployment environment
2. Set the WEBHOOK_URL environment variable
3. Use your public domain: https://your-domain.railway.app/

Enable Execution Pruning

Keep your database clean:

N8N_EXECUTIONS_DATA_PRUNE=true
N8N_EXECUTIONS_DATA_MAX_AGE=168

Set Timezone

Configure your timezone:

GENERIC_TIMEZONE=America/New_York

How Do I Monitor My n8n Instance?

Railway provides comprehensive monitoring with real-time logs, resource metrics, deployment tracking, and alerting capabilities built into the platform.

Railway Monitoring

Railway provides built-in monitoring:

• Logs - Real-time application logs
• Metrics - CPU, memory, and network usage
• Deployments - Track deployment history
• Alerts - Set up notifications

Health Checks

Check if your instance is running:

curl https://your-n8n-url.railway.app/healthz

How Can I Scale My n8n Deployment?

Scale your n8n deployment by adding more worker replicas in Railway or optimizing your database connection pooling for better performance.

Adding More Workers

In Railway, scale workers by:

1. Go to your project settings
2. Find the n8n-worker service
3. Increase replica count
4. Railway handles load balancing

Database Optimization

For better performance:

DB_POSTGRESDB_SSL_ENABLED=true
DATABASE_CONNECTION_POOL_MIN=2
DATABASE_CONNECTION_POOL_MAX=10

What Are Common Issues and How Do I Fix Them?

Most issues relate to domain configuration, webhook URLs, memory usage, or authentication settings. Each has specific solutions and prevention strategies.

Common Issues

Issue	Solution
Can’t access n8n	Check if domain is generated in Railway
Webhooks not working	Ensure WEBHOOK_URL is set correctly
High memory usage	Enable execution pruning
Authentication not working	Check N8N_BASIC_AUTH variables

Getting Help

• n8n Community Forum
• Railway Discord
• n8n Documentation

What Should I Do After Setting Up Hosting?

After hosting setup, focus on configuring error handling, implementing retry strategies, and building advanced workflows to maximize your automation capabilities.

• Learn n8n Basics
• Explore Service Integrations
• Discover LLM Workflow Generation

Frequently Asked Questions

How much does it cost to host n8n on Railway?

Railway offers a generous free tier that includes $5 of monthly usage. For production workloads, costs typically range from$10-50/month depending on your resource usage (CPU, memory, bandwidth). The exact cost depends on your workflow complexity and execution frequency.

Can I migrate my data if I want to leave Railway?

Yes, you have full access to your PostgreSQL database and can export all your workflows, credentials, and execution history. n8n data is portable between hosting providers since you control the database.

What happens if Railway has downtime?

Railway has excellent uptime (99.9%+), but for mission-critical applications, consider setting up monitoring and have a backup deployment ready. You can always restore your n8n instance on another provider using your database backups.

How do I backup my n8n data on Railway?

Railway automatically backs up your PostgreSQL database. You can also set up additional backups by exporting workflows via the n8n API or CLI. Consider implementing automated backup workflows within n8n itself.

Can I use my own domain with Railway?

Yes, Railway supports custom domains with automatic SSL certificates. Go to your service settings, add your domain, and update your DNS records as instructed. SSL certificates are managed automatically.

How do I update my n8n version on Railway?

Railway automatically deploys the latest stable n8n version. You can also manually trigger deployments or pin to specific versions if needed. Updates are seamless with zero downtime.

What’s the difference between Railway and Docker Compose hosting?

Railway is fully managed (automatic updates, monitoring, scaling) while Docker Compose requires manual management but gives you complete control. Railway is better for teams wanting simplicity; Docker Compose for those needing customization.

Can I connect Railway n8n to external databases?

Yes, you can configure n8n to use external PostgreSQL, MySQL, or other databases instead of Railway’s managed database. This is useful for compliance or when integrating with existing infrastructure.

How do I scale n8n for high-volume workflows?

On Railway, increase worker replicas and upgrade your database plan. For extreme scale, consider horizontal scaling with multiple n8n instances sharing the same database and Redis queue.

What security features does Railway provide for n8n?

Railway provides automatic HTTPS, private networking between services, environment variable encryption, and infrastructure-level security. Always enable n8n’s built-in authentication and consider additional access controls for production use.