The Complete n8n Self-Hosted Setup Guide (2024)

What if you could automate almost any business process without writing a single line of code? That's exactly what n8n self-hosted setup gives you. n8n is an open-source workflow automation tool that connects your apps, moves your data, and runs complex logic on a schedule or trigger. It's like having a silent operator working 24/7 in the background.

Most teams default to cloud-hosted automation platforms and pay the price, literally. Subscription costs balloon as usage grows. Your data sits on someone else's servers. And you're stuck with whatever limits the vendor decides to impose. Self-hosting n8n flips that equation. You own the server. You own the data. You control the costs.

Why Self-Host n8n? Understanding the Core Benefits

Before you spin up a server, it's worth asking: why bother?

Here's why we think self-hosting n8n is the right call for most serious teams.

Data Privacy and Security

When you run n8n on your own server, your workflow data never leaves your infrastructure. No third-party cloud stores your API keys, customer records, or business logic. For teams handling sensitive data, that's not a nice-to-have. It's a requirement.

Regulations like GDPR and HIPAA make data residency a real concern. Self-hosting means you decide where your data lives and who can access it.

Cost Efficiency at Scale

Cloud automation platforms charge per task, per workflow, or per seat. That's fine when you're running a handful of workflows. But as your automation grows, so does your bill.

With self-hosting, your main costs are:

• A VPS or cloud instance (often $5 to $20/month for small setups)
• Your time for initial setup and occasional maintenance

Compare that to $50, $100, or $500/month for a cloud plan with usage limits. The math gets obvious fast.

Full Customization and Control

Self-hosting gives you the keys to the whole environment. You can:

• Install custom n8n nodes
• Connect to internal systems that aren't exposed to the public internet
• Control memory, CPU, and storage allocation
• Run multiple n8n instances if needed

Cloud plans don't give you that flexibility. You work within their sandbox.

Better Performance for High-Volume Workflows

Shared cloud instances can throttle performance during peak times. When you own the server, you choose the specs. If a workflow needs to process thousands of records per hour, you scale the server, not your plan.

Yes, There's a Learning Curve

We won't sugarcoat it. Setting up n8n yourself takes more effort than clicking "sign up" on a cloud platform. You'll deal with command-line tools, Docker, and server configuration.

But it's a one-time investment. Once it's running, maintaining it is straightforward. And the control you gain is worth every minute of setup time.

Choosing Your Self-Hosting Method: Docker vs. Manual Installation

There are two main ways to self-host n8n. Let's break them down so you can pick the right one.

Option 1: Docker (Our Recommendation)

Docker is a containerization platform. It packages n8n, all its dependencies, and its runtime environment into a single portable unit called a container. You run that container on your server, and it works the same way every time, regardless of what else is installed on the machine.

Why Docker works so well for n8n:

• Quick setup. A single docker-compose up command and you're live.
• No dependency conflicts. Everything n8n needs is inside the container.
• Easy updates. Pull the latest image and restart.
• Isolated from your host system. If something breaks, it stays contained.
• Docker Compose lets you run n8n alongside a database in one config file.

For most users, Docker is the right choice. It's predictable, well-documented, and the n8n team officially supports it.

Option 2: Manual Installation

Manual installation means installing n8n directly on your server's operating system using npm (Node Package Manager). You run npm install -g n8n and configure everything yourself.

When manual installation makes sense:

• You have a specific Node.js version requirement
• You're integrating n8n into a larger existing system
• You need granular control over every dependency

The downsides:

• More complex setup and ongoing maintenance
• Dependency conflicts are common, especially with Node.js version mismatches
• Updates require more manual steps
• Not ideal for production environments without extra tooling like PM2 for process management

Our Verdict

Use Docker. Unless you have a specific technical reason to go manual, Docker gives you a cleaner, more reliable setup with far less headache. The rest of this guide focuses on the Docker path.

Step-by-Step: Setting Up n8n with Docker (The Recommended Way)

Let's get n8n running. Follow these steps in order.

Prerequisites

Before you start, make sure you have:

• A server (a VPS from DigitalOcean, Hetzner, Linode, or even your local machine)
• Docker installed (official install guide)
• Docker Compose installed (official install guide)
• Basic comfort with a terminal and command-line commands, -

Step 1: Create a Directory for n8n

Organize your files from the start.

mkdir n8n && cd n8n

This creates a folder called n8n and moves you into it. All your config files will live here., -

Step 2: Create Your docker-compose.yml File

This file defines your entire n8n environment. We recommend using PostgreSQL as the database instead of the default SQLite. SQLite is fine for testing, but PostgreSQL is more reliable for production workloads.

Create the file:

nano docker-compose.yml

Paste in this configuration:

version: '3.8'

services:

 # The n8n application
 n8n:
 image: n8nio/n8n
 restart: always
 ports:
 - "5678:5678"
 environment:
 # The hostname or IP where n8n will be accessible
 - N8N_HOST=your-domain-or-ip
 - N8N_PORT=5678
 - N8N_PROTOCOL=https
 # Database configuration (PostgreSQL)
 - DB_TYPE=postgresdb
 - DB_POSTGRESDB_HOST=postgres
 - DB_POSTGRESDB_PORT=5432
 - DB_POSTGRESDB_DATABASE=n8n
 - DB_POSTGRESDB_USER=n8n_user
 - DB_POSTGRESDB_PASSWORD=your_strong_password
 # Timezone setting
 - GENERIC_TIMEZONE=America/New_York
 # Base URL for webhooks and editor
 - N8N_EDITOR_BASE_URL=https://your-domain-or-ip
 volumes:
 # Persists n8n data on your host machine
 - n8n_data:/home/node/.n8n
 depends_on:
 - postgres

 # PostgreSQL database
 postgres:
 image: postgres:15
 restart: always
 environment:
 - POSTGRES_DB=n8n
 - POSTGRES_USER=n8n_user
 - POSTGRES_PASSWORD=your_strong_password
 volumes:
 # Persists database data on your host machine
 - postgres_data:/var/lib/postgresql/data

# Named volumes so data survives container restarts
volumes:
 n8n_data:
 postgres_data:

What each section does:

• image: The official n8n Docker image from Docker Hub
• restart: always: n8n restarts automatically if the server reboots or the container crashes
• ports: Maps port 5678 on your server to port 5678 inside the container
• environment: Sets all the config n8n needs to run. Replace your-domain-or-ip and your_strong_password with real values
• volumes: Keeps your data safe. Without this, all data is lost when the container stops
• depends_on: Tells Docker to start PostgreSQL before n8n

Save the file with Ctrl+X, then Y, then Enter., -

Step 3: Start n8n

docker-compose up -d

The -d flag runs the containers in detached mode, meaning they run in the background and don't tie up your terminal. Docker will pull the images on first run, which takes a minute or two., -

Step 4: Access n8n

Open your browser and go to:

http://your-server-ip:5678

If you're running this locally, use http://localhost:5678.

You should see the n8n setup screen., -

Step 5: Create Your First Account

n8n will prompt you to create an owner account on first launch. Fill in your name, email, and a strong password. This account has full admin access to your instance. See also: AI content pipeline architecture explained.

Once you're in, you'll see the n8n workflow editor. You're live.

Essential Post-Setup Configuration for a Production-Ready n8n

Getting n8n running is step one. Making it production-ready is step two. Here's what to do before you start building real workflows.

1. Add SSL/TLS with a Reverse Proxy

Right now, your n8n instance runs over HTTP. That means data between your browser and the server travels unencrypted. For any real use, you need HTTPS.

The standard approach is to put a reverse proxy in front of n8n. We recommend either Nginx or Caddy.

Caddy is the easier option. It handles SSL certificate renewal automatically via Let's Encrypt.

High-level steps:

1. Install Caddy on your server
2. Point your domain's DNS A record to your server IP
3. Create a Caddyfile that proxies your domain to localhost:5678
4. Caddy fetches and renews your SSL certificate automatically

For Nginx, the flow is similar but you'll also need Certbot to handle the SSL certificate from Let's Encrypt.

Once your reverse proxy is set up, update N8N_PROTOCOL=https and N8N_EDITOR_BASE_URL=https://your-domain.com in your docker-compose.yml, then restart with docker-compose up -d., -

2. Set the Right Environment Variables

A few environment variables matter a lot for production. Add or confirm these in your docker-compose.yml:

- N8N_EDITOR_BASE_URL=https://your-domain.com
# Ensures webhook URLs are generated correctly See also: [preparing your team](blog-preparing-team-ai-automation.html).

- GENERIC_TIMEZONE=America/New_York
# Set to your actual timezone so scheduled workflows fire at the right time

- N8N_BASIC_AUTH_ACTIVE=true
- N8N_BASIC_AUTH_USER=admin
- N8N_BASIC_AUTH_PASSWORD=another_strong_password
# Adds HTTP Basic Auth as an extra access layer before the n8n login screen

Basic Auth adds a second gate in front of your n8n login. Even if someone finds your URL, they hit a browser-level password prompt first., -

3. Set Up a Backup Strategy

If your server dies and you have no backup, your workflows are gone. Don't skip this.

Back up your PostgreSQL database:

docker exec -t your_postgres_container_name pg_dumpall -c -U n8n_user > n8n_backup_$(date +%Y%m%d).sql

Run this on a cron job daily and ship the file to an S3 bucket, Backblaze B2, or any offsite storage.

Back up your volumes:

Your n8n_data Docker volume holds credentials and settings. You can back it up with:

docker run, rm -v n8n_n8n_data:/data -v $(pwd):/backup alpine tar czf /backup/n8n_data_backup.tar.gz /data

Also keep a copy of your docker-compose.yml in version control or cloud storage., -

4. Monitor Logs

When something breaks, logs are your first stop.

docker logs n8n

Or follow logs in real time:

docker logs -f n8n

For server health, tools like Netdata or even basic htop give you a quick view of CPU and memory usage. If n8n starts consuming too many resources, you'll want to know before it causes problems., -

5. Keeping n8n Updated

The n8n team ships updates frequently. Staying current gets you bug fixes, new nodes, and security patches.

To update:

docker-compose pull n8n
docker-compose up -d

That's it. Docker pulls the latest image and restarts the container with the new version. Your data stays intact because it's stored in the named volumes, not inside the container itself.

We recommend checking the n8n changelog before major updates to catch any breaking changes. See also: learn more.

Take Control: Your Journey to Powerful, Private Automation Starts Now

Let's recap what we covered.

Self-hosting n8n gives you three things you can't get from a cloud plan: full control over your environment, complete data privacy, and costs that don't scale with your usage. You own the server. You own the workflows. Nobody else has access to your data.

Yes, the setup takes some effort. But this guide has broken it into clear, repeatable steps. You create a directory, write a docker-compose.yml, run one command, and you're in. The post-setup work, adding HTTPS, setting environment variables, and building a backup routine, takes an afternoon at most.

After that? You have a self-hosted automation platform that can run hundreds of workflows, connect to internal systems, and handle your most sensitive data without leaving your infrastructure.

n8n is one of the most capable automation tools available right now. And running it yourself means you get the full picture, no artificial limits, no per-task pricing, no vendor lock-in.

So here's our challenge to you: spin up your first self-hosted n8n instance this week. Build one workflow. See what it feels like to have that level of control.

We think you'll wonder why you didn't do it sooner.

If you want help building automation systems on top of your n8n setup, our team at GrowthSpike is here. We build and manage AI-powered automation workflows for businesses that want to move faster without hiring more people.