Cloud costs $20 a month and caps you at 2,500 runs. Self-hosted costs about $5 a month for the server and caps you at nothing — except your own time. The right choice is a math problem, and most people solve it with the wrong numbers, because they count the server bill and forget the execution count.
The Cloud prices, as they stand
n8n prices Cloud in US dollars, and one execution is one full run of a workflow, however many steps it has. A 3-node workflow and a 50-node workflow both cost one execution. Prices below are from n8n's pricing page as checked live on 16 November 2026; n8n changes packaging, so check the page before you buy.
- Starter — $20 a month on annual billing ($24 month to month). 2,500 executions a month, 5 concurrent executions, 1 shared project, single runs capped at 5 minutes.
- Pro — $50 a month on annual billing ($60 month to month). 10,000 executions a month, 20 concurrent executions, 3 shared projects, single runs capped at 40 minutes.
- Pro 50K — $120 a month on annual billing. 50,000 executions a month.
Every Cloud plan includes unlimited users and unlimited workflows — only execution volume changes the bill. Cloud data is hosted in Frankfurt, and n8n patches, backs up and keeps the service up for you.
The execution math that decides it
Count runs per month, not workflows. A schedule that fires every 5 minutes lands at roughly 8,600 to 8,900 executions a month for one workflow alone.
- 1 workflow, hourly: 720–744 runs a month. Starter covers it, with room to spare.
- 3 workflows, hourly: 2,160–2,232 runs a month. Still Starter.
- 1 workflow, every 15 minutes: 2,880–2,976 runs a month. Starter is out — Pro, at $60 a month.
- 1 workflow, every 5 minutes: 8,640–8,928 runs a month. Pro, nearly full.
- 2 workflows, every 5 minutes: over 17,000 runs a month. Above the 10,000 Pro tier — a bigger Pro size, or self-hosted.
Polling is what eats the budget. A workflow that checks an inbox every 5 minutes costs more in a month than a workflow that runs a hundred times a day on webhooks, because webhooks only fire when something happens.
The self-hosted side
The Community edition is free software with no execution cap — you pay only for the server. A small VPS runs about $5–6 a month, and the setup runs n8n 3.0 in Docker on Vultr: 3.0 killed npm installs, so Docker is the way in.
What you pay for in Cloud, you do yourself here: you patch n8n when a release lands, you back up the database, you watch the disk fill up, you restart the container at 2 a.m. when a workflow dies. That is the real price, and it is paid in your evenings, not on a card. For client work, there is one more line: run it on the client's Cloud account, not yours — https://whoisalfaz.me/go/n8n — so the executions, support and uptime belong to the business that depends on them, and your fee stays a fee for the build.
What worked
Cloud is the right default for client work. No server to keep alive, no patch night, no 2 a.m. restart. The client gets support and uptime from n8n, and you get a bill you can show them. For anything a business depends on, that is worth $20.
Self-hosted wins on volume. Once your runs pass 10,000 a month, Cloud pricing climbs past the cost of a small server by a wide margin. A $5 server running 20,000 executions costs the same as a $5 server running 200 — the cap is gone, and polling every 5 minutes stops being a billing decision.
The 3.0 guide makes the self-hosted route safe. The upgrade guide walks through the 37 nodes 3.0 replaces and the one-way upgrade — 1.x support ends 31 December 2026, so the move is coming either way. Read it before you touch production, whichever side you pick. Guide: https://whoisalfaz.me/blog/how-to-upgrade-to-n8n-3-without-breaking-workflows/
What broke — or rather, what is hard
Starter's 5-minute run cap bites quietly. A workflow that processes a big export can run past 5 minutes on Starter and stop halfway. Pro lifts the cap to 40 minutes. If your workflows are long, the plan choice is about run time, not execution count.
Self-hosted means you are the support desk. There is no one to call when the container will not start. If you have never run Docker in production, budget a weekend to learn it — or pay Cloud until you have.
The free tier is not a business plan. Community is free and it is real software, but it has no SSO, no environments, no Git version control and no shared projects. A team of two sharing workflows will feel that gap fast.
Who it is for
Cloud fits if your workflows run a business, your runs fit inside 2,500 or 10,000 a month, or you would rather pay $20 than own a server. Self-hosted fits if your runs are past 10,000 a month, your data has to stay on your own server, or you already run Docker and enjoy it. It fits neither way if you have not counted your executions yet — count first, then choose, because the wrong side of this line costs either $60 a month or a weekend of your life.
The deal, plainly
Cloud, for client work and anything a business depends on: https://whoisalfaz.me/go/n8n — Starter $20 a month on annual billing, Pro $50. Self-hosted, for volume: the server is Vultr, https://whoisalfaz.me/go/vultr — run n8n 3.0 in Docker on it, since 3.0 killed npm installs. Count your runs, then pick a side.
The server is cheap. Your evenings are not.
Top comments (0)