Skip to content
Underread.
Reviews

n8n Review: Self-Hosted Automation That Finally Makes Sense

Four months, thirty-one production workflows, one small server. What broke, what it actually cost, and who should not do this.

By Vemuri AbhiramUpdated 18 November 20264 min read
Laptop displaying charts on a desk at night
Laptop displaying charts on a desk at night

Disclosure: some links here earn me a commission if you buy, at no extra cost to you. It never changes what I recommend, and I only link to things I’ve actually paid for and used.

The verdict

n8n (self-hosted)

4.5/5
Check current price →
On this page

I moved 31 automations off a per-task platform onto self-hosted n8n and ran them for 4 months. Here's the honest account, including the two times it broke.

:::key The short answer: worth it if someone on your team is comfortable with Docker (the tool that packages the app so it runs the same on any machine) and you either run LLM steps in loops or pay over about $50 a month in task fees. The bill went from roughly $180 a month to $14, in exchange for about 2 hours of maintenance a month. 4.5 out of 5. :::

#What it's

A workflow automation tool you run yourself. Same visual node-and-edge model as the hosted platforms — triggers, actions, branches — except the execution meter doesn't exist, because the server is yours. There's a paid cloud version too. It removes the maintenance and keeps the model, but you lose the main financial argument.

#What's genuinely good

The error handling is the reason to switch. Every execution is stored with its full input and output. You can replay a failed run after fixing the cause. On a per-task platform you mostly get a red icon and a retry button that starts from scratch. The first time a client asked what happened to an invoice 3 weeks ago, I pulled up the exact payload in about 30 seconds.

Code nodes are first-class. Dropping into JavaScript or Python mid-flow is normal rather than an escape hatch. That matters more than it sounds: the awkward 10% of a workflow stops dictating which tool you can use for the other 90%.

LLM steps stop being scary. An agent that loops 12 times costs 12 executions, which costs nothing, because you're paying for a server rather than a counter. This single fact is why I moved.

:::pros

  • Full execution history with replay, which no hosted tier matches at this price
  • No per-task meter, so retries and agent loops are free
  • Code nodes are first-class, not an escape hatch
  • Data never leaves your infrastructure, which settles most client security reviews in one sentence :::

:::cons

  • Noticeably fewer integrations than Zapier; you'll write HTTP nodes by hand
  • You now own backups, upgrades and uptime
  • The editor gets sluggish on workflows past roughly 40 nodes
  • Source-available licence, not OSI open source — read it before reselling :::

#What actually went wrong

Twice in 4 months. A connection pool exhausted during a backfill. Executions queued silently rather than failing loudly, so I didn't notice for about 2 hours. Fix was a bigger Postgres pool and an alert on queue depth. My fault, and the kind of thing a hosted platform absorbs for you.

A minor-version upgrade changed a node's output shape and broke 3 workflows at once. Fix was pinning the image version and testing upgrades against a copy first. Also my fault, also absorbed by hosted platforms.

Neither was a bug in n8n. Both were the cost of owning infrastructure, which is the real subject of this review.

:::warn Self-hosting means the 3am page is yours. If nobody on your team wants that, the per-task pricing on a hosted platform isn't a rip-off — it's exactly what you're buying. Don't switch to save money and then discover nobody owns the server. :::

#The numbers

Before (hosted) After (n8n self-hosted)
Monthly cost ~$180 ~$14 VPS
Workflows 23 31
Executions / month Metered, watched Unmetered, ignored
Maintenance 0 hours ~2 hours
Outages in 4 months 0 2, both self-inflicted

The workflow count went up because the meter stopped being a reason not to automate something small. That's a real second-order effect and the one I didn't expect.

#Should you use it?

Yes, if someone is comfortable with Docker. You're either running LLM steps in loops, or paying more than about $50 a month in task fees. No, if nobody wants to own infrastructure. 2 hours a month is real, and it lands at inconvenient times. Consider the cloud version if you want the error handling and the code nodes without the server. You lose the cost argument and keep everything else.

#What you should check before you migrate

If you're moving off a hosted platform, rebuild your 3 most complex flows first rather than your 3 simplest. You'll find out within a day whether the integrations you depend on exist. You generally won't discover that from the integrations page. What matters is whether the specific trigger and the specific field you use are supported, not whether the logo is listed. I lost most of a day to an integration that existed but didn't expose the one webhook I needed.

Related reading: the full automation tool comparison, and cutting your LLM bill, which is usually the other half of this problem.

Frequently asked questions

Is the cloud version worth it instead?

It removes the maintenance and keeps the model. You lose the main financial argument but keep the error handling and the code nodes.

What does it cost to run?

A small VPS and a managed Postgres handles dozens of workflows comfortably. Mine is about $14 a month.

Is the licence actually open source?

It's source-available under a sustainable-use licence, not OSI open source. Fine for internal use; read it carefully before reselling it.

How long does setup take?

An afternoon for a working instance with Postgres and backups. Migrating existing workflows is the longer job, because they need rebuilding rather than importing.

What happens if the server goes down?

Your automations stop. Put it on a host with a status page, alert on queue depth, and keep the database backed up somewhere else.

Written by

Vemuri Abhiram

Founder & Editor

I write every post here. The tools I review are ones I pay for and run on real client work, not demo accounts, and every number you see came off my own invoice or dashboard.

More from Underread, once a week.

The guides worth reading and the tests worth trusting. One email, every Friday.

No spam. Unsubscribe in one click.