n8n Review | What It Does, Pricing, Alternatives, My Verdict
AUTOMATION · TOOL REVIEW

n8n

★★★★

Self-hostable, extremely capable and cheapest at scale. The developer's choice, and it asks something of you.

CATEGORY
Automation platform
PRICE
Free self-hosted / Paid cloud
MY RATING
4.5 / 5
LINK TYPE
No commission
BEST FOR
Technical teams wanting automation without per-task pricing

What it is

n8n is a workflow automation platform you can self-host, with a node-based visual builder, the ability to write JavaScript inside workflows, and no per-task pricing when you run it yourself.

It also offers a hosted cloud version priced by workflow executions rather than by individual operations, which is cheaper than both Zapier and Make at volume.

It is aimed at people comfortable with a server and a little code, and it rewards them substantially.

What it does

Node-based workflows similar to Make's, with the significant addition that you can drop into JavaScript or Python at any step to do something the nodes do not cover.

Self-hosting means your data never leaves your infrastructure, which resolves the compliance objection that rules out hosted automation for some businesses.

AI agent nodes let you build workflows where a model makes decisions or processes content mid-flow, and this is currently the most practical automation-plus-AI tooling I have used.

Its integration library is smaller than Zapier's, mitigated by a generic HTTP node that connects to any API you are willing to read the documentation for.

Who it's for

01Technical teams and developers.
02Businesses with data that cannot leave their infrastructure.
03Anyone running automations at high volume.
04Teams building AI-driven workflows.
05People who find per-task pricing unacceptable in principle.

Features

Self-hosting
Run it on your own infrastructure at no licence cost.
Node-based builder
Visual workflows with branching and loops.
Code nodes
JavaScript or Python inside any workflow.
AI agent nodes
Models making decisions mid-workflow.
HTTP node
Connect to any API, documented or not.
Execution-based cloud pricing
Cheaper at volume than per-task rivals.

Pros and cons

PROS
Free to run yourself with no task limits.
Code nodes remove every capability ceiling.
Best AI workflow tooling of the three.
Self-hosting satisfies data residency requirements.
Cloud pricing by execution, not per operation.
CONS
Self-hosting requires a server and maintenance.
Smaller integration library than Zapier or Make.
Steepest learning curve of the three.
Fewer templates and tutorials.
Debugging assumes some technical comfort.

Pricing

PLAN WHAT YOU GET WORTH IT FOR
Self-hosted community Free, unlimited workflows and executions. Technical teams with a server.
Cloud Starter Hosted, limited executions. Small teams avoiding server management.
Cloud Pro More executions and concurrency. Regular heavy use.
Enterprise SSO, air-gapped deployment, support. Regulated organisations.

Self-hosting is free apart from your server cost, typically a few pounds a month. Cloud pricing counts whole executions rather than individual steps.

MY RECOMMENDED PLAN

Self-hosted on a small cloud server if you or somebody in the business is comfortable with that. Otherwise Cloud Starter, which is still cheaper than the equivalent Zapier plan.

Alternatives

Make
Easier, hosted, cheap enough for most businesses. My recommendation for non-technical teams.
Zapier
Easiest and most expensive, with the widest integration support.
Custom scripts
Sometimes simpler for one critical automation.
Activepieces
Another open-source alternative worth knowing about.

My verdict

n8n is the best automation platform for anybody technical, and the least suitable for anybody who is not. Self-hosted it costs the price of a small server, has no task limits, and the code nodes mean you never hit a wall.

Its AI tooling is currently ahead of both rivals. If you want a workflow where a model reads incoming enquiries, classifies them and routes them, this is where I would build it.

The honest caveat: self-hosting is maintenance. If nobody in the business will update a container or investigate a failed run, use Make and pay for somebody else to worry about it.

Try n8n →

Who should use it

01Technical teams and developers.
02Businesses with data residency requirements.
03Anyone running automations at high volume.
04Teams building AI-driven workflows.

Who should avoid it

01Non-technical users, who should use Make.
02Businesses with nobody to maintain a server.
03Teams needing a large template library.
04Anyone who wants their first automation running in ten minutes.

Affiliate disclosure

I earn nothing from this recommendation. There is no affiliate link on this page and I pay for my own subscription where one is needed. When a review on this site does carry a commercial link, it says so in this same place on the page.

All recommended tools Last reviewed September 2026