![n8n Pricing Explained: Cloud vs Self-Hosted True Cost [2026]](/images/blog/n8n-pricing-explained.webp)
Here is the punchline before the details: the exact same automation can cost you $0, $24, or $70+ a month — and which number you land on has almost nothing to do with how much work the automation does. It depends on how the tool counts. n8n counts differently than almost everything else in the category, and once you understand its billing unit, its pricing stops looking confusing and starts looking like a lever you can pull.
Most "n8n pricing" pages just reprint the tiers off n8n's website. That's the least useful part. The useful part is the one design decision underneath the tiers — n8n bills per workflow execution, not per step — and the honest math on whether "free and self-hostable" is actually free once you count your own time. That's what this breakdown covers.
The one thing that makes n8n pricing different
Nearly every mainstream automation tool bills by the step. On Zapier, each action in a Zap is one task. On Make, each module that runs is one operation. Run a 10-step workflow once and you've burned roughly 10 billed units. Run it a thousand times and you've burned about 10,000. The bill scales with steps × runs.
n8n throws that model out. Its billing unit is the execution: one entire run of one workflow, start to finish, counts as a single execution — whether that workflow has two nodes or two hundred. A simple two-step notifier and a sprawling 50-node AI agent both cost you exactly one execution per run. Your bill scales with runs only. Steps are free.
This is the whole ballgame. If you've been burned by a surprise Zapier or Make bill, it's almost always because a workflow you thought was "one automation" was quietly multiplying into thousands of billed steps. n8n removes that multiplier. We wrote a whole piece on why these billing units diverge so wildly — see what actually counts as a task — because it's the single most misunderstood line item in automation software.
n8n Cloud pricing tiers (2026)
These are n8n's managed-cloud plans as of August 2026. n8n prices in euros, so the dollar figures drift slightly with exchange rates; the monthly-billing numbers below are the higher, no-commitment prices, with annual billing knocking them down.
| Plan | Price (monthly) | Executions / mo | Best for |
|---|---|---|---|
| Starter | ~$24 (~$20 annual) | 2,500 | Solo builders, side projects, low-volume internal automations |
| Pro | ~$60 (~$50 annual) | 10,000 | Small teams running steady production workflows |
| Business | ~$800 | 40,000 | Teams needing queue mode, Git version control, and SSO without a full enterprise contract |
| Enterprise | Custom (annual) | Negotiated (often 600k+/yr) | Large orgs needing dedicated support, advanced RBAC, and scale guarantees |
Two 2026 changes matter for budgeting. First, n8n removed active-workflow caps across all cloud tiers — you can build unlimited workflows and add unlimited users, and your bill is driven purely by execution volume. Second, the permanent free cloud tier was retired; you now get a trial, after which you either pay or self-host to keep workflows live. And a small mercy: failed test runs inside the editor no longer count against your monthly executions, so debugging doesn't quietly eat your allowance.
What an "execution" actually costs you — the math vs Zapier and Make
Abstract billing units mean nothing until you run a real workload through them. So take one concrete workflow and price it three ways.
Scenario: a lead-routing workflow with 8 steps, firing 1,000 times a month
Same trigger, same eight actions, same 1,000 monthly runs on every platform. Here's how each tool counts it:
- n8n: 1,000 executions (steps don't count) → fits Cloud Starter at ~$24/mo with headroom, or ~$10/mo of VPS if self-hosted.
- Make: ~8,000 operations (8 modules × 1,000 runs) → lands in Make's lower paid tiers, roughly $12–19/mo.
- Zapier: ~8,000 tasks (each action step counts) → well past the entry tier and into Zapier's ~$70+/mo Professional brackets at 2026 rates.
The structural point holds regardless of the exact dollar figures, which shift as vendors reprice: n8n counts 1,000 billed units for this workflow while Zapier and Make count ~8,000. That 8× gap in billed units is entirely a function of step count, and it's why teams running deep, multi-step workflows so often migrate to n8n. If you want the full Zapier ladder, we broke it down in Zapier pricing explained.
But be honest about where the model flips. Because n8n bills per run, a high-frequency, low-complexity workflow is where it gets expensive. A two-step workflow that fires 50,000 times a month is 50,000 executions on n8n — that's Business-tier territory ($800/mo) — while on Make those same 100,000 operations might cost less. The rule of thumb: n8n rewards depth and punishes frequency. Deep workflows that don't run constantly are its sweet spot.
Is n8n really free? The true cost of self-hosting
"Free and open" is n8n's headline, and it's mostly true — with an asterisk on both words. The self-hosted Community Edition carries no license fee and no execution or workflow caps. But it's released under n8n's Sustainable Use License, a "fair-code" model rather than a strict open-source (OSI) license: you can run it freely for internal business use, but you can't repackage and resell it as your own hosted product.
The bigger asterisk is that "no license fee" is not the same as "no cost." Self-hosting moves the bill from a line item on n8n's invoice to a set of costs you absorb yourself:
- Infrastructure: a small VPS runs ~$5–15/mo; heavier workloads (queue mode, workers, a real database) cost more.
- Setup time: initial deployment, reverse proxy, TLS, and environment config — a few hours if you know Docker, longer if you don't.
- Maintenance: version upgrades, dependency patches, and breaking-change migrations, indefinitely.
- Reliability: backups, monitoring, and securing the instance are on you. There's no SLA — if your server goes down at 3 a.m., so do your automations.
- Your hours: the real cost. If a self-hosted instance eats even two engineer-hours a month, that "free" tool is quietly costing more than a $24 Cloud plan.
None of this makes self-hosting a bad deal — it makes it a different deal. We go deeper on this tradeoff in self-hosted vs cloud workflow automation, but the short version is below.
Cloud vs self-hosted: which is actually cheaper for you
Skip the ideology and answer three questions:
- How much execution volume do you have? Below ~10,000 executions/mo, Cloud Starter or Pro almost always beats the loaded cost of self-hosting. Once you're pushing tens of thousands of executions, self-hosting's marginal cost approaches zero and Cloud's climbs.
- Do you already have ops capability? If a server, monitoring, and someone who owns it already exist, adding n8n is cheap. If you'd be standing all of that up from scratch just for automation, Cloud is cheaper than it looks.
- Do you have data-residency or compliance constraints? If data can't leave your infrastructure, self-hosting isn't a cost decision — it's the only option, and the price stops mattering.
The honest crossover: for most individuals and small teams under ~10k executions/mo with no existing ops team, Cloud Starter/Pro is the cheaper and saner choice once you value your time at all. Self-hosting wins for high-volume workloads, teams with existing infrastructure, and anyone with compliance requirements that force the data on-premise.
n8n Enterprise: when custom pricing kicks in
Above the Business tier, n8n moves to custom annual contracts. There's no published list price, but administrators on n8n's own forums report Enterprise floors in the neighborhood of €20,000/year — roughly $2,000–3,000/mo — for allocations around 600,000 executions annually, with dedicated support priced separately. What you're actually buying at that tier is less about executions and more about advanced RBAC, log streaming, SSO, environments, and a support SLA. If you're comparing enterprise automation platforms at that budget, the calculus shifts entirely — that's the world we mapped in the four tiers of workflow automation tools.
Bottom line: which n8n price is yours
n8n doesn't have a price — it has three doors, and the per-execution model decides which one is cheapest for your specific workload:
- Solo builder, deep workflows, moderate volume → Cloud Starter (~$24/mo). The per-execution billing is doing you a favor here.
- Small team, steady production automations → Cloud Pro (~$60/mo), unless you already run infrastructure.
- High volume, existing ops team, or compliance constraints → self-host the Community Edition and pay only for infrastructure.
- High-frequency simple workflows → price a per-operation tool too; n8n's run-based model is working against you here.
Do the one calculation that matters before you pick a plan: multiply your busiest workflow's step count by its monthly run count, then compare that to n8n's execution allowance. If the gap is large, n8n's pricing is a feature, not a footnote. And if you land on "n8n isn't the right shape for me," we keep a running list of n8n alternatives sorted by exactly this kind of billing math.
Not sure n8n's billing model fits your workflows?
Compare 18 automation platforms side by side — pricing model, free tier, and integration depth — on one page.
Compare automation tools →Frequently asked questions
Does n8n have a free plan?
The self-hosted Community Edition is free with no execution cap — you only pay for infrastructure. n8n Cloud no longer offers a permanent free tier; after the trial you must pay or self-host to keep workflows active.
Does a failed run count as an execution?
Production failures still count. As of 2026, failed test runs inside the editor no longer count against your monthly execution allowance, so debugging doesn't eat your budget.
Is self-hosted n8n really unlimited?
On billing, yes — there are no execution or active-workflow caps. Your real ceiling is your server's capacity, and the tradeoff is that hosting, upgrades, backups, security, and uptime are all yours to manage.
Is n8n cheaper than Zapier?
Usually, for multi-step workflows, because n8n bills per whole-workflow execution while Zapier bills per action step. The exception is high-frequency simple workflows, where n8n's per-run model burns executions faster than a per-task tool would.