n8n Self-Hosted Review: When Free Open-Source Automation Makes Sense (And When It Doesn't)

What n8n is

n8n is an open-source workflow automation tool. Visual node-based builder (like Make.com), but with two big differences:

1. Self-hostable. You run it on your own server, free forever (apart from hosting costs).
2. Open source. Code is on GitHub, fork it, modify it, contribute to it.

There's also a paid n8n Cloud ($24-$50+/month) for those who don't want to self-host.

The question everyone asks: "Is self-hosted worth the hassle to save the subscription cost?"

---

Self-hosted costs (real)

You need:

• A server. VPS at DigitalOcean, Hetzner, Linode: $5-$20/month for a small instance. Hetzner is cheapest (~$5/month for 2 CPU / 4GB RAM).
• A domain. Optional but recommended. $10-15/year.
• HTTPS certificate. Free via Let's Encrypt.
• Your time. Setup: 2-4 hours if you know Docker. Maintenance: 1-2 hours/month ongoing (updates, monitoring, troubleshooting).

Total monetary cost: $60-$250/year. Total time cost: 20-40 hours/year.

Compared to n8n Cloud at $24-$50/month = $288-$600/year. Self-hosted saves ~$200-$500/year in cash, costs 20-40 hours.

If your time is worth more than $15/hour: paid cloud is cheaper. If you genuinely have the time and want the control: self-hosted wins.

---

What n8n does well

Unlimited executions

Self-hosted has no operation/execution limits. Your only limit is your server capacity. For high-volume automation (50k+ executions/month), this is huge vs. Make/Zapier/n8n Cloud pricing.

Custom code nodes

n8n has "Code" and "Function" nodes that let you run JavaScript directly in your workflows. Full language access, not just formulas. If you know JS, you can do things that are painful in Make or Zapier.

Self-hosted data sovereignty

Data never leaves your server. For healthcare, legal, financial, or EU GDPR-critical work, this is a compliance advantage.

Community nodes

Users have built community nodes for niche tools not officially supported. 500+ community nodes available.

Standard automation features

Full parity with Make: visual builder, branching, error handling, iterators, webhooks, scheduled triggers. You're not giving up features to self-host.

---

Where n8n falls short

Setup is not trivial

You need to be comfortable with:

• Docker basics
• Terminal commands
• Environment variables
• Reverse proxies (Nginx/Caddy)
• HTTPS certificate management

If "curl" and "ssh" aren't in your vocabulary, self-hosted n8n will frustrate you. Stick with n8n Cloud or Make.

Updates require action

n8n releases new versions every 1-2 weeks. You have to docker pull and restart your container to update. Usually safe, occasionally breaks a workflow. You need a process for this.

No one to call when it breaks

If your n8n instance crashes at 2am, that's your problem. n8n Cloud has support; self-hosted has the community Discord and Stack Overflow.

Reliability depends on you

VPS goes down → your automation stops. Need backup strategy, monitoring, alerts. This is DevOps work, not "set and forget."

Less polished UI than Make

Make and Zapier have bigger product teams. UX polish shows. n8n is improving quickly but still a step behind on design details.

Integrations fewer than Make/Zapier

n8n has 400+ integrations. Make has 1,800+. Zapier has 6,000+. For niche tools, n8n sometimes requires HTTP nodes where competitors have native integration.

---

Self-hosted vs. n8n Cloud

| Dimension | Self-Hosted | n8n Cloud | |-----------|------------|-----------| | Monthly cost | $5-$20 (server) | $24-$50+ | | Setup time | 2-4 hours | 5 minutes | | Maintenance time | 1-2 hrs/month | 0 | | Execution limits | None | Varies by plan | | Support | Community | Included | | Data location | Yours | n8n servers | | Reliability | Your responsibility | n8n's SLA |

Pick self-hosted when:

• You're a developer or DevOps-comfortable operator
• You run high-volume automation where execution limits would be expensive
• You need data sovereignty
• You want to modify n8n core code

Pick n8n Cloud when:

• Your time is worth more than $15/hour
• You want to skip DevOps entirely
• Your volume fits in their plan pricing

---

Self-hosting step-by-step

For the DevOps-curious:

1. Get a VPS

Hetzner Cloud CPX11 ($5/month) or DigitalOcean $6/month droplet. Ubuntu 22.04 or later.

2. Install Docker

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

3. Run n8n in Docker

docker run -d --restart unless-stopped \
  --name n8n \
  -p 5678:5678 \
  -v n8n_data:/home/node/.n8n \
  -e N8N_HOST=n8n.yourdomain.com \
  -e N8N_PROTOCOL=https \
  -e WEBHOOK_URL=https://n8n.yourdomain.com \
  n8nio/n8n

4. Set up HTTPS

Use Caddy or Nginx + Let's Encrypt. Caddy is easier:

n8n.yourdomain.com {
  reverse_proxy localhost:5678
}

5. Set up database backup

By default, n8n uses SQLite. For production, switch to PostgreSQL and back it up daily with pg_dump to S3 or similar.

6. Monitor

UptimeRobot ($0-$7/month) for ping monitoring. Healthchecks.io for job monitoring. Basic setup covers the essentials.

---

When self-hosted makes sense

• You're technical and genuinely enjoy DevOps. Don't self-host because you "should save money." Self-host because you actually like managing infrastructure.
• You're running very high volume. 100k+ executions/month where Make would cost $100+ and n8n Cloud would hit limits.
• You have data sovereignty requirements. EU healthcare data, financial services, etc.
• You want to learn. Self-hosted n8n is a great project for learning Docker, servers, monitoring.

When self-hosted doesn't make sense

• You want to focus on business, not infrastructure. Self-hosted is a second job.
• You're non-technical. You'll struggle and blame the tool.
• Your volume is low. Under 10k executions/month, Make or Zapier or n8n Cloud is priced reasonably.
• You need enterprise reliability. Self-hosted reliability is what you build, not what you buy.

---

My honest take

Self-hosted n8n is genuinely great for the right person. I run production workflows on a self-hosted n8n instance for about $7/month on Hetzner. For my volume (30-50k executions/month), it's cheaper than Make and more flexible.

But I enjoy DevOps and have the skills to maintain it. For a client deployment where I need to hand off a system, I lean toward Make or n8n Cloud — self-hosted creates a dependency on me that I don't want.

If you're evaluating: try n8n Cloud first ($24/month Starter). If you love n8n and hit volume walls, switch to self-hosted. That path is better than starting with self-hosted and getting frustrated.

---

Sources

Pricing from n8n.io/pricing and n8n.io/cloud as of April 2026. VPS pricing from Hetzner, DigitalOcean, and Linode public pages. Feature comparisons from n8n's documentation, GitHub, and my own deployment experience. Integration counts are published counts from each platform.

Thinking about self-hosting n8n for a specific workflow? Let's talk — I can help you evaluate whether it's the right choice for your situation.