How to Self-Host n8n Workflow Automation on Ubuntu VPS with Docker (Free Zapier Alternative)

Why Switch from Proprietary Automation to Self-Hosted n8n?

Modern online businesses and development agencies rely heavily on workflow automation to synchronize CRM leads, automate e-commerce fulfillment, process webhooks, trigger server maintenance scripts, and orchestrate AI LLM agent pipelines. However, SaaS automation platforms like Zapier or Make charge steep tiered pricing per task execution—often running hundreds of dollars monthly when executing high-volume loops.

n8n is the premier fair-code workflow automation platform. Featuring over 400+ native integrations (including OpenAI, Anthropic, Slack, GitHub, WordPress, Stripe, and PostgreSQL), self-hosting n8n on a Linux Cloud VPS gives you unlimited workflow executions, zero task count throttling, complete privacy for sensitive API keys, and native support for custom JavaScript / Python code execution nodes.

In this technical deployment guide, we will configure n8n on Ubuntu 24.04/22.04 LTS backed by persistent PostgreSQL, orchestrate execution via Docker Compose V2, and configure an Nginx reverse proxy with WebSockets and Let’s Encrypt SSL.

Step 1: Installing Docker Engine and Project Directory Setup

Ensure your Ubuntu VPS has Docker CE and Compose V2 installed:

# Install Docker and prerequisite utilities
sudo apt update && sudo apt install -y curl git nginx certbot python3-certbot-nginx

curl -fsSL https://get.docker.com | sudo sh
sudo systemctl enable --now docker

# Create dedicated directory for n8n stack
sudo mkdir -p /var/www/n8n-stack
sudo chown -R $USER:$USER /var/www/n8n-stack
cd /var/www/n8n-stack

Step 2: Writing Production Docker Compose Manifest with PostgreSQL

While n8n supports SQLite by default, high-concurrency production deployments should always use PostgreSQL to ensure reliable multi-threading and prevent database file locking:

Create /var/www/n8n-stack/docker-compose.yml:

services:
  postgres:
    image: postgres:16-alpine
    container_name: n8n_postgres
    restart: always
    environment:
      POSTGRES_USER: n8n_user
      POSTGRES_PASSWORD: StrongN8nDbPassword2026!
      POSTGRES_DB: n8n_db
    volumes:
      - postgres_data:/var/lib/postgresql/data
    deploy:
      resources:
        limits:
          memory: 512M

  n8n:
    image: docker.n8n.io/n8nio/n8n:latest
    container_name: n8n_app
    restart: always
    environment:
      - DB_TYPE=postgresdb
      - DB_POSTGRESDB_HOST=postgres
      - DB_POSTGRESDB_PORT=5432
      - DB_POSTGRESDB_DATABASE=n8n_db
      - DB_POSTGRESDB_USER=n8n_user
      - DB_POSTGRESDB_PASSWORD=StrongN8nDbPassword2026!
      - N8N_HOST=automation.example.com
      - N8N_PORT=5678
      - N8N_PROTOCOL=https
      - NODE_ENV=production
      - WEBHOOK_URL=https://automation.example.com/
      - GENERIC_TIMEZONE=UTC
      - EXECUTIONS_DATA_PRUNE=true
      - EXECUTIONS_DATA_MAX_AGE=168
    ports:
      - "127.0.0.1:5678:5678"
    volumes:
      - n8n_data:/home/node/.n8n
    depends_on:
      - postgres
    deploy:
      resources:
        limits:
          memory: 1024M

volumes:
  postgres_data:
  n8n_data:

Step 3: Launching the n8n Container Fleet

# Start n8n and PostgreSQL services in detached mode
docker compose up -d

# Verify containers are running and healthy
docker compose ps

Step 4: Configuring Nginx Reverse Proxy with WebSocket Support

n8n’s visual workflow canvas requires persistent WebSocket connections for live execution telemetry. Create /etc/nginx/sites-available/automation.example.com:

server {
    listen 80;
    server_name automation.example.com;

    client_max_body_size 50M;

    location / {
        proxy_pass http://127.0.0.1:5678;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_buffering off;
        proxy_cache off;
    }
}

Enable the configuration and issue an SSL certificate:

sudo ln -s /etc/nginx/sites-available/automation.example.com /etc/nginx/sites-enabled/
sudo nginx -t && sudo systemctl reload nginx
sudo certbot --nginx -d automation.example.com

n8n Self-Hosted vs Zapier Commercial Comparison

Deploying AI Agent Nodes & LangChain in n8n

n8n includes native support for autonomous AI Agents, vector memory stores, and LLM integrations. You can build advanced AI workflows (such as automated customer support ticket triage, AI blog generation, or code reviewer bots) by connecting the OpenAI, Anthropic, or local Ollama nodes directly to Webhook triggers and PostgreSQL memory:

# Example n8n environment configuration for AI execution
N8N_AI_ENABLED=true
N8N_METRICS_ENABLED=true
EXECUTIONS_DATA_SAVE_ON_ERROR=all
EXECUTions_DATA_SAVE_ON_SUCCESS=none

Scaling n8n with Redis Queue Mode (Worker Fleet)

For enterprise installations running thousands of simultaneous workflows, n8n supports horizontal scaling via Redis Queue mode. In this architecture, the main n8n web instance accepts webhook triggers and offloads heavy script executions to an elastic pool of background worker containers:

# Add Redis service to docker-compose.yml
redis:
  image: redis:7-alpine
  restart: always

# Configure n8n in queue execution mode
environment:
  - EXECUTIONS_MODE=queue
  - QUEUE_BULL_REDIS_HOST=redis
  - QUEUE_BULL_REDIS_PORT=6379

Routine n8n Maintenance & Pruning

Prevent database bloat by scheduling weekly execution pruning in your docker-compose.yml via EXECUTIONS_DATA_PRUNE=true and EXECUTIONS_DATA_MAX_AGE=168 (7 days).

Securing Webhook Triggers with Cryptographic HMAC Signatures

When creating public webhook endpoints in n8n (such as receiving automated Stripe payment events, Shopify order notifications, or GitHub push payloads), exposing unauthenticated webhook URLs allows bad actors to trigger spoofed workflows. Always enforce cryptographic HMAC-SHA256 signature verification within your n8n workflows before processing incoming webhook data:

// JavaScript Code Node for HMAC-SHA256 Header Validation in n8n
const crypto = require('crypto');
const signature = $request.headers['x-hub-signature-256'];
const secret = $env.WEBHOOK_SIGNING_SECRET;
const payload = JSON.stringify($json.body);

const hmac = crypto.createHmac('sha256', secret);
const digest = 'sha256=' + hmac.update(payload).digest('hex');

if (signature !== digest) {
    throw new Error('Unauthorized: Cryptographic HMAC signature validation failed!');
}
return { status: 'verified', data: $json.body };

Installing Custom Community Nodes in Dockerized n8n

To extend n8n with community nodes from NPM without rebuilding the base Docker container, configure the N8N_COMMUNITY_PACKAGES_ENABLED flag in your environment:

# Enable community node installation from web UI
N8N_COMMUNITY_PACKAGES_ENABLED=true
N8N_CUSTOM_EXTENSIONS=/home/node/.n8n/custom