n8n is the automation platform people move to when the per-step billing on everything else stops making sense. Its pricing counts complete workflow executions, so a thirty-node workflow costs exactly the same as a three-node one. It can also run entirely on your own infrastructure, which changes the conversation about where customer data lives. Both of those are genuine advantages. Both come with a bill that is paid in operational responsibility rather than subscription fees, and that trade is not right for every business.
The pricing model is the headline feature
Every mainstream automation tool bills you for steps. n8n bills you for completed workflow executions. One run of a workflow is one execution regardless of whether it contains four nodes or forty.
Work through what that means. Take a workflow that processes an incoming order: validate it, look up the customer, enrich the address, calculate tax, write to the database, notify the warehouse, email the customer, log to a sheet. That is eight steps. On a step-billed platform, a thousand orders a month costs you eight thousand billable units. On n8n it costs one thousand executions.
The practical consequence is that n8n removes a perverse incentive. On step-billed platforms you find yourself deliberately building worse, shorter workflows to control cost — skipping the validation step, skipping the logging step. On n8n, thoroughness is free.
What n8n costs
| Tier | Listed price | What you get |
|---|---|---|
| Community (self-hosted) | $0 licence | Source-available under n8n’s fair-code Sustainable Use Licence; you pay only for the server |
| Starter (cloud) | €20/mo | 2,500 workflow executions/month |
| Pro (cloud) | €50/mo | 10,000 workflow executions/month |
| Enterprise | Custom | Not published — contact sales |
n8n prices per completed workflow execution, not per step — a 30-node workflow and a 3-node workflow both count as one. Cloud pricing is listed in euros. Higher cloud tiers exist above Pro; check the live page. Source: the vendor’s own pricing page, read August 5, 2026. Prices change — verify before you commit.
Self-hosting: what you actually take on
The Community edition is source-available and free to run yourself. This is the part that gets oversold on the internet, so here is the unglamorous version of what "free" involves.
You need somewhere to run it — a small cloud server is usually adequate for a small business workload. You need a database behind it for anything beyond trivial use. You need it reachable over HTTPS with a real certificate if any external service is going to send it webhooks. And you need someone who will notice when it stops.
That last one is the whole thing. A self-hosted automation server is infrastructure. It needs updates applied, backups taken and restores tested, credentials rotated, and monitoring that alerts a human when the process dies at 2am. None of that is difficult in isolation. All of it is work that recurs forever.
If your business does not already have someone who maintains a server, self-hosted n8n is not a cost saving — it is a new job you have quietly created. Use n8n Cloud instead. You keep the execution-based pricing, which was the main advantage anyway, and someone else handles the 2am problem.
The three reasons small businesses actually choose n8n
1. Volume has made step billing absurd
This is the most common trigger. A business hits the point where its automation bill is a real line item, looks at what it is paying per step, and does the arithmetic on execution-based pricing instead. If your workflows are long and run often, the difference is not marginal.
2. The data cannot leave your control
Health records, legal files, financial detail, anything under a client contract that specifies where data is processed. Self-hosted n8n means the customer data in your workflows never transits a third-party automation vendor. For some businesses this is the only reason that matters, and no amount of pricing advantage on the alternatives changes it.
3. The workflows need real code
n8n has first-class Code nodes running JavaScript or Python. When a transformation is genuinely easier expressed as six lines of code than as fifteen drag-and-drop modules, you write the six lines. Simpler platforms make you choose between contorting the visual builder and giving up.
Where n8n is the wrong choice
- You are automating your first process. Learn what you actually need with Zapier or Make first. Choosing the most powerful tool before you know the requirements is how people end up with an unmaintained server.
- Nobody technical is staying. If the person who set it up is a contractor who finishes next month, self-hosting leaves you with a system you cannot fix. Cloud, or a different tool.
- Your integrations are niche. n8n's node library is good and growing, but narrower than Zapier's directory. It handles arbitrary HTTP well, which closes most gaps — at the cost of reading API documentation yourself.
- Volume is genuinely low. If you run two hundred executions a month, execution-based pricing saves you very little and you have taken on complexity for nothing.
A realistic adoption path
The sequence that works, in our experience, is: prove the workflow somewhere easy, measure what it actually costs, then migrate the expensive ones.
Build version one on a platform with no setup cost. Run it for a month against real data. Look at the bill and the failure rate. If the bill is trivial, you are done — the migration is not worth anyone's time. If the bill has become a real number, or if a compliance conversation has started about where data sits, that is the signal to move that specific workflow to n8n. You rarely need to migrate everything.
Whichever engine you land on, the judgement steps inside it — classifying an enquiry, extracting fields from a document, drafting a reply — are where an LLM node belongs. And if you would rather not own any of this yourself, that is exactly the case for bringing in an automation partner; the free audit is where that starts.