How to Self-Host n8n in 2026:
Complete Beginner's Guide

If you've been looking for a way to automate your business workflows without paying Zapier's ever-increasing prices, n8n is probably already on your radar. It's open-source, incredibly powerful, and — when self-hosted — completely free to run with no execution limits.

But "self-hosting" can mean two very different things: managed hosting (someone handles the infrastructure for you) or DIY VPS setup (you install and manage everything yourself). Both have their place, and this guide covers both in detail.

What is n8n?

n8n (pronounced n-eight-n) is a free, open-source workflow automation platform that lets you connect hundreds of apps and services — Gmail, Slack, Notion, Airtable, Stripe, and hundreds more — without writing code.

Think of it like Zapier or Make.com, but open-source, self-hostable, and with unlimited executions on the self-hosted version. You build workflows visually using a drag-and-drop node editor, and n8n handles the connections between your apps.

It's used by solo founders to automate lead generation, by agencies to build client automation pipelines, and by enterprises to replace expensive SaaS middleware tools.

Why Self-Host n8n?

There are five compelling reasons teams choose to self-host n8n rather than use n8n Cloud:

1. No execution limits. n8n Cloud caps executions on all plans. Self-hosted n8n runs unlimited workflows and executions — no throttling.
2. Full data ownership. Your workflow data, credentials, and execution history never leave your infrastructure. Critical for GDPR compliance and sensitive business data.
3. Cost savings up to 95%. n8n Cloud starts at $24/month. A managed self-hosted n8n instance starts at $2.99/month — for unlimited executions.
4. Custom nodes and integrations. Self-hosted n8n lets you install community nodes and build custom integrations that aren't available on the cloud version.
5. White-labelling. Deploy n8n under your own domain with your branding — perfect for agencies building automation platforms for clients.

What You Need

Before you start, here's what's required:

• A server or VPS (2 GB RAM minimum, 4 GB recommended for production)
• A domain name (for HTTPS and webhooks to work properly)
• About 30–60 minutes if you're going the DIY route
• Or about 5 minutes if you use managed hosting

If you're not comfortable with the command line, Option 1 (managed hosting) is the right choice — no terminal access needed.

Option 1: Managed Hosting with OpenHosst (Recommended)

Managed hosting is the fastest and easiest way to get n8n running. The provider handles Docker, SSL certificates, nginx, security updates, and backups — you just connect your domain and start building workflows.

OpenHosst offers managed n8n hosting starting at $2.99/month with a 7-day free trial. Here's how to get started:

Step 1: Start your free trial

Go to portal.openhosst.com/apps and select n8n. Click Start Free Trial — no card payment required for the 7-day trial.

Step 2: Choose your plan

The Starter plan at $2.99/month covers most solo and small-team use cases. The Business plan at $12.50/month adds more resources for high-volume automation.

Step 3: Connect your domain

Add a CNAME or A record pointing your subdomain (e.g. n8n.yourcompany.com) to the server IP provided in your dashboard. SSL is provisioned automatically via Let's Encrypt.

Step 4: Log in and build

Within minutes, your n8n instance is live. Log in with the credentials from your dashboard and start building workflows. Everything else — updates, backups, monitoring — is handled for you.

Option 2: DIY VPS Setup

If you prefer complete control over your infrastructure, you can set up n8n yourself on any VPS. Here's a minimal production setup using Docker Compose.

Expected time: 60–90 minutes. Ongoing maintenance: 1–2 hours per month (updates, backups).

Step 1: Get a VPS

Choose any cloud provider — DigitalOcean, Hetzner, Linode, or Vultr all work well. You'll need at least:

• 1 vCPU, 2 GB RAM (minimum)
• 20 GB SSD storage
• Ubuntu 22.04 LTS (recommended)

Step 2: Install Docker

# Install Docker Engine
curl -fsSL https://get.docker.com | bash
sudo usermod -aG docker $USER
newgrp docker

Step 3: Create your docker-compose.yml

Create a new directory and a docker-compose.yml file:

mkdir ~/n8n && cd ~/n8n
nano docker-compose.yml

Paste this configuration (replace your-domain.com with your actual domain):

services:
  n8n:
    image: n8nio/n8n:latest
    restart: unless-stopped
    ports:
      - "127.0.0.1:5678:5678"
    environment:
      - N8N_HOST=n8n.your-domain.com
      - N8N_PORT=5678
      - N8N_PROTOCOL=https
      - WEBHOOK_URL=https://n8n.your-domain.com/
      - GENERIC_TIMEZONE=UTC
      - N8N_ENCRYPTION_KEY=change-this-to-a-random-string
    volumes:
      - ~/.n8n:/home/node/.n8n

Step 4: Set up nginx + SSL

Install nginx and Certbot, then configure a reverse proxy:

sudo apt install nginx certbot python3-certbot-nginx -y
sudo certbot --nginx -d n8n.your-domain.com

Add this server block to /etc/nginx/sites-available/n8n:

server {
    listen 443 ssl;
    server_name n8n.your-domain.com;

    location / {
        proxy_pass http://127.0.0.1:5678;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}

Step 5: Start n8n

docker compose up -d

Your n8n instance should now be accessible at https://n8n.your-domain.com. Set up your admin account on the first visit.

Cost Comparison

Here's a realistic breakdown of what self-hosting n8n actually costs across your three main options:

The DIY VPS option looks cheapest on paper at ~$6/month, but factor in your time (setup + maintenance) and the risk of misconfiguration, and managed hosting at $2.99/month wins on total cost for most users.

Common Mistakes to Avoid

After helping hundreds of teams get n8n set up, here are the mistakes we see most often:

1. Skipping backups

The ~/.n8n directory (or wherever your Docker volume is mounted) contains your entire n8n configuration — workflows, credentials, settings. If your server crashes without a backup, you lose everything. Set up daily backups before you do anything else.

2. Undersizing the server

Running n8n on a 1 GB RAM VPS works for very light usage, but complex workflows with many parallel executions will crash it. Start with 2 GB and upgrade if you see out-of-memory errors.

3. Using HTTP instead of HTTPS

n8n's webhook URLs must be HTTPS for most third-party services to trigger them. Always configure SSL before you start building production workflows.

4. Not setting N8N_ENCRYPTION_KEY

Without a strong, persistent encryption key, your stored credentials (API keys, OAuth tokens) are encrypted with a default key. If you rebuild the container without passing the same key, all credentials become invalid.

5. Ignoring updates

n8n releases updates frequently. Run docker compose pull && docker compose up -d regularly to stay on the latest version and receive security patches.

Frequently Asked Questions

Can I migrate from n8n Cloud to self-hosted?

Yes. n8n has a built-in export/import feature. Go to Settings → Export in your n8n Cloud instance to download all workflows as JSON, then import them on your self-hosted instance. Credentials need to be re-entered manually for security reasons.

What happens to my automations if the server goes down?

Scheduled workflows pause until the server restarts. Webhook-triggered workflows will fail while the server is down (callers will receive connection errors). With a managed provider like OpenHosst, uptime is monitored 24/7 and services are restarted automatically.

Can I use n8n self-hosted for commercial purposes?

Yes. n8n Community Edition is free for personal and commercial use under the Sustainable Use License. If you're embedding n8n into a product you sell, review the enterprise licensing terms.

How many workflows can I run on self-hosted n8n?

There are no artificial limits on the number of workflows, active workflows, or executions. The practical limit is your server's CPU and RAM. A 2 GB RAM server can typically handle 50–100 simultaneous workflow executions before slowing down.

Does n8n self-hosted support multi-user access?

Yes. Since n8n 0.227.0, multi-user support is included in the Community Edition. You can invite team members and assign roles (owner, admin, member) from the n8n settings panel.

Ready to get started? The fastest way to get n8n running today is with a 7-day free trial on OpenHosst — no card payment required, no DevOps knowledge needed. If you decide to go the DIY route, the steps above will get you there in about an hour.

For more on n8n pricing and how self-hosted compares to the cloud plans, see our n8n Cloud Pricing breakdown. For a comparison with other automation tools, read n8n vs Zapier.