n8n pricing for cloud plans per month, the execution limit and the real cost of self-hosting
Markdownn8n pricing in 2026: Starter 20 EUR, Pro 50 EUR, Business (self-hosted) 667 EUR a month billed yearly, execution limits, and the cost of self-hosting.
Starter and Pro run on n8n Cloud. Business is available only for self-hosting. Enterprise is available hosted by n8n or self-hosted. n8n starts at 20 EUR a month on annual billing for 2,500 workflow executions, rises to 50 EUR a month for 10,000 executions on Pro, and reaches 667 EUR a month for 40,000 executions on Business. Enterprise pricing is quoted by sales. Billed monthly, the same three plans cost 24 EUR, 60 EUR and 800 EUR, respectively, which reflects the 17% annual discount n8n advertises. Prices were read from n8n.io/pricing on 30 September 2026 and are listed in EUR. The self-hosted Community Edition is free and open source with unlimited executions, so its cost is server time plus the hours spent maintaining it.
Key takeaways
- The meter is the execution. One full workflow run counts as one execution, no matter how many nodes it has.
- Active workflow limits are gone. Since April 2026, every plan lets you keep as many workflows switched on as you like.
- The Pro (Cloud) to Business (self-hosted) step is steep. 50 EUR to 667 EUR a month is a 13x jump for 4x the executions. The Business licence excludes infrastructure and operating costs.
- Hitting the limit stops work. On cloud plans, executions over the monthly allowance are not queued. n8n's support site says they fail immediately with an error.
- Free is not free of cost. Self-hosting is cheap in dollars and expensive in engineering hours.
How much does n8n cost?
n8n costs 20 EUR a month for 2,500 executions, 50 EUR a month for 10,000, and 667 EUR a month for 40,000, all on annual billing as listed on n8n.io/pricing on 30 September 2026. Enterprise pricing is quoted. Self-hosting the Community Edition costs nothing in license fees.
The plans differ on more than execution count. Concurrency, the number of workflow runs that can be in flight at the same time, is the limit teams hit second most often, and AI credits are metered separately from executions. Here is how the published tiers line up.
| Plan | Price (annual billing) | Executions / month | Concurrency | Notable |
|---|---|---|---|---|
| Starter | 20 EUR / mo | 2,500 | 5 | 1,600 AI Assistant credits a month |
| Pro | 50 EUR / mo | 10,000 | 20 | Up to 9,600 AI Assistant credits a month |
| Business | 667 EUR / mo | 40,000 | 30 | Listed as self-hosted only; 4,000 EUR per extra 300,000 executions |
| Enterprise | Contact sales | Custom | 200+ | 365 days of insights |
US buyers should note the EUR listing. The card charge is converted and moves with the exchange rate, so a plan quoted at 50 EUR is not a fixed dollar line in the budget. This may matter when finance asks why the number changed.
Is n8n free?
Yes, in one specific form. The n8n Community Edition is free and open source on GitHub. You can run it on your own server, and it has no execution cap. What you give up is managed hosting, enterprise features gated behind paid tiers, and vendor responsibility for uptime. The Cloud plans are the paid product.
There is no free Cloud tier, only a trial. The choice is who runs the infrastructure. Teams with a platform engineer and an existing container setup may find self-hosting inexpensive. Teams without one may pay for it in engineering time.
Does n8n charge per step or per execution?
Per execution. One complete workflow run counts as one execution regardless of how many nodes or steps it contains, so a 40-node workflow with branches, loops and error handling bills the same as a two-node one. This is the main structural difference between n8n's pricing and per-task tools like Zapier, and it favors complex workflows.
The practical effect is to consolidate. If you can do the same job in one workflow with several branches instead of five workflows chained by webhooks, you cut your execution count by five. Sub-workflows called from a parent count separately, so account for that pattern when optimizing. Since April 2026, n8n has removed the active-workflow limits that used to cap how many workflows you could leave switched on, so there is no longer a need to disable useful automations to stay inside a tier.
What pushes your n8n bill up?
Four things, roughly in this order: high-frequency schedules, per-record loops that trigger child workflows, retries that rerun a whole workflow, and concurrency caps that force a tier jump before execution count does. None may be obvious when you build the first automation, and all can compound over time.
A schedule trigger firing every minute is 43,200 executions a month on its own, exceeding the 40,000 Business (self-hosted) allowance with one workflow. Move it to every five minutes and it is 8,640.
Retries can be easy to miss. If a workflow fails partway through and a retry reruns the whole thing, an API that is flaky for an hour can double or triple executions for that window. Concurrency is another constraint: Starter allows 5 concurrent runs and Pro allows 20, so a burst of webhooks can queue or fail at a volume well below your monthly execution allowance. You may need to upgrade for concurrency rather than execution count.
What happens when you run out of n8n executions?
On Starter and Pro, the workflow stops running. n8n's support documentation states that executions at the limit are not queued and fail immediately with an error, and that limits reset at the start of each calendar month regardless of your billing date. A sync that overruns on the 24th is down until the 1st unless you upgrade. Pro has a 50,000-execution tier at 145 EUR a month, or 1,450 EUR a year, before the jump to Business (self-hosted). n8n's help center says Pro customers on monthly billing can buy additional executions through the admin panel, while annual Pro customers have to email support to ask. The fix is self-serve on one billing cycle and slower on the other.
Business is the only plan with a published overage price: 4,000 EUR for each extra bucket of 300,000 executions, according to the pricing page on 30 September 2026. The same page lists Business as self-hosted only, with the cloud version of that tier not yet offered, so a team that wants n8n to run the servers and needs more than Pro offers has to ask sales about Enterprise. That changes the risk profile: on lower tiers, the failure mode is an outage; on Business, it is an invoice. Neither is desirable for a data sync.
Is self-hosting n8n worth it?
It depends on whether your team already runs servers. A small VPS capable of handling n8n for a modest workload costs a few dollars a month, so infrastructure is close to free. The real cost is operational: version upgrades, database backups, TLS certificate renewal, queue-mode setup at scale, monitoring, and someone reachable when a workflow silently stops at 2am.
Put a number on it honestly. If self-hosting costs four hours a month of an engineer's time at a loaded rate of $90 an hour, that is $360 a month of hidden spend, seven times the Pro plan. If your team already has CI, container orchestration and paging in place, the marginal hours may be much closer to zero, making self-hosting a strong choice. The middle case, where one technical person inherits n8n alongside their regular job, is where self-hosting can quietly become expensive.
If you go self-hosted, treat it like production from day one. Pin the version, back up the Postgres database on a schedule you have actually tested restoring from, and put the instance behind a reverse proxy with automatic certificate renewal. Teams that do not want to handle server provisioning and zero-downtime deployments in-house should account for that work before calling the Community Edition free, because it continues to take time after launch.
Is n8n cheaper than Zapier?
For complex, multi-step workflows, usually yes, because n8n bills one execution per workflow run while Zapier bills per task, meaning per step. A 15-step workflow run 5,000 times a month is 5,000 executions on n8n and 75,000 tasks on Zapier. For simple two-step automations at low volume, the gap narrows.
The comparison that matters more for a data team is metered versus flat pricing. The table below compares the two shapes as volume climbs, using n8n's published EUR figures and another provider's published USD tiers. At 10,000 runs a month, n8n Pro at 50 EUR may be cheaper than other options, which is an advantage of its model.
| Monthly workflow runs | n8n | n8n price | Flat tier |
|---|---|---|---|
| 2,000 | Starter (Cloud) | 20 EUR / mo | Starter, $49 / mo |
| 9,000 | Pro (Cloud) | 50 EUR / mo | Starter or Growth, $49 to $149 / mo |
| 35,000 | Business (self-hosted) | 667 EUR / mo | Growth, $149 / mo |
| 120,000 | Enterprise (Cloud / self-hosted) | Quoted by sales | Scale, $399 / mo |
At 35,000 runs per month, compare a higher Pro Cloud quota with the self-hosted Business licence and the cost of running it. The sync frequency and the choice between webhooks and polling affect that comparison.
Which one you should pick depends on what you are doing. n8n is a general automation and AI workflow builder with hundreds of nodes and a code node, and it can be good value for branching logic. If your job is narrower—moving records between a database, a warehouse and a few SaaS systems on a schedule with retries and logs—a purpose-built data integration platform may require less maintenance and offer a bill that does not move with run count.
Put this guide to work with Ailoot
Connect AI models to your applications, agents and automations through one Ailoot API. Choose the model that fits your task and follow the Ailoot documentation to get started.