Contents
- Fast answer
- Quick facts
- What this covers
- Why it matters
- Where to go next
- Outcomes
- Step by step
- The methodology: what the calculator actually computes
- How to read the result when the pricing unit changes
- A worked example: chasing overdue invoices at an accounting firm
- The limits: what this cost model leaves out
- n8n Cloud tiers, verified against the pricing page
- The cross-platform math on a real workflow
- Self-hosting economics with real 2026 infrastructure prices
- What changed in 2025 and 2026
- At a glance
- Mistakes to avoid
- FAQ
- Related guides
Fast answer
The n8n workflow cost calculator estimates your true monthly automation cost across the four layers that actually drive it: execution volume, hosting choice, AI model calls, and maintenance time, then compares the total against what the same workflows would cost on Zapier or Make. The methodology reflects how n8n pricing really works. n8n charges per workflow execution rather than per step, which is why multi-step workflows that get expensive on task-priced platforms often run far cheaper on n8n. You enter monthly executions, average steps, and how many workflows call AI models, then pick a hosting path: n8n Cloud starting around 25 dollars per month, or self-hosting on a 10 to 40 dollar VPS plus the admin hours that actually dominate self-hosted cost. The output is a monthly total, a per-execution cost, and a side-by-side against Zapier and Make at your real volume, which is the comparison that matters, since platform rankings flip depending on steps per run.
Facts last verified 2026-07
Quick facts
- n8n Cloud Starter
- EUR 20/mo billed annually; 2,500 executions, 5 concurrent, 2,300 AI credits
- n8n Cloud Pro
- EUR 50/mo billed annually; 10,000 executions, 20 concurrent
- Execution definition
- One run of the whole workflow counts once, regardless of steps (n8n pricing page)
- Self-host server cost
- Hetzner ~EUR 4-9/mo; DigitalOcean $6-24/mo; license-free via Sustainable Use License
- Comparable entry tiers
- Zapier Professional $19.99/mo for 750 tasks; Make Core $9/mo for 10,000 credits
- n8n company scale
- $180M Series C at $2.5B valuation; ARR above $40M (Oct 2025)
On this page
What this page covers
A tool visitor should leave with a decision, not just a number: build now, prepare first, choose another workflow, or follow a course path.
- 01Runs
- 02Workflows
- 03AI calls
- 04Hosting
- 05Comparison
- 06Recommendation
Why does this matter now?
The subscription price is the least interesting number in an automation stack, and comparing platforms by it produces bad decisions in both directions. Zapier bills per task, Make per operation, and n8n per execution, so the same workflow can differ in cost by five to ten times across platforms depending on how many steps each run contains. Self-hosting muddies it further: the server is cheap, but updates, backups, and debugging are paid in hours. Agencies quoting client work without this math either underprice and eat the difference or overprice and lose the deal.
Internal path
Where to go next from this page
These links are part of the A8gent learning and conversion path. Use them to move from concept, to diagnosis, to workflow build, to course.
What you should be able to do after this
- Estimate n8n cost
- Compare Zapier and Make
- Budget AI calls
- Choose hosting
How do you do it, step by step?
1. Count executions and steps per workflow
Estimate how many times each workflow runs per month and how many steps a typical run contains, including branches and error retries. This distinction is the whole game: n8n charges per execution regardless of steps, while Zapier and Make charge per step or operation. A 15-step workflow running 1,000 times a month is where the platforms diverge dramatically.
2. Choose the hosting path with honest labor costs
n8n Cloud starts around 25 dollars per month and removes infrastructure work. Self-hosting needs a 10 to 40 dollar VPS plus Docker upkeep, updates, backups, and security patching, realistically two to five admin hours per month. Price those hours at your real rate before concluding self-hosting is cheaper. For one or two workflows, it usually is not.
3. Add AI model costs separately
n8n does not bill for your model usage; your OpenAI or Anthropic account does. Estimate calls per execution, including retries and multi-step agent nodes, times average prompt size, times the per-token price. AI-heavy workflows often spend more on model calls than on n8n itself, and this line is the most common surprise on the first real invoice.
4. Budget maintenance and debugging time
Workflows break when APIs change, credentials expire, and edge cases appear. Plan two to five hours per month across a small workflow portfolio, more if you self-host. For agencies, this is billable retainer scope; for internal teams, it is someone's job that must be named. Unmaintained n8n instances fail quietly until a client notices missing data.
5. Compare against Zapier and Make at your actual volume
Run the same volume math on all three: executions times steps against Zapier's task pricing and Make's operation pricing. n8n typically wins on multi-step, high-volume workflows, while Zapier can win for a handful of simple zaps where its higher per-task cost buys zero infrastructure thought. Decide on your numbers, not on platform marketing.
6. Re-check the math as volume grows
Cost rankings flip with scale. A stack that is cheapest on n8n Cloud at 5,000 executions may justify self-hosting at 50,000, and a client project that fit Zapier's free tier can become its most expensive line item. Re-run the calculator quarterly or whenever a workflow's volume doubles, and before quoting any new client retainer.
The methodology: what the calculator actually computes
The model has four inputs and one chain of arithmetic. Volume is the number of items your workflow handles each month. Resolution rate is the share the agent handles end to end without a person. Manual cost is what one of those items costs you today in labour. AI cost is what one item costs to run through the model. From those, resolved items equal volume times resolution rate, gross monthly saving equals resolved items times manual cost, and inference cost equals resolved items times AI cost.
On top of that sits a fixed 5 percent operations overhead, applied to the gross saving rather than to the whole volume. That line stands for the monitoring, the prompt maintenance, the failed executions you re-run, and the person who reads the error log. Net monthly saving is gross minus inference minus that overhead. Annual return subtracts a one-off investment figure, and the payback label divides that same investment by the net monthly saving to express a time.
Two things are worth naming plainly. The resolution rate is doing an enormous amount of work in this model, and it is the input people guess at most freely. A workflow at 55 percent resolution and one at 80 percent are different businesses, not different settings. And the 5 percent operations overhead is a flat assumption, not a measurement. For a stable workflow running for a year it is probably generous; for a workflow in its first month it is nowhere near enough.
The calculator prices the workflow, not the platform. Your n8n bill sits on top of the numbers above and follows its own unit. n8n cloud charges per execution, where one execution covers a whole workflow run regardless of how many steps it contains. Published cloud pricing as of August 2026 is Starter at EUR 20 a month for 2,500 executions, Pro at EUR 50 for 10,000, and Business at EUR 667 for 40,000, all on annual billing, quoted in euros only.
How to read the result when the pricing unit changes
The most expensive mistake in workflow cost modelling is comparing platforms on headline price while ignoring what they count. n8n charges one execution per workflow run. Make.com charges credits, roughly one per module action, so a scenario with fifteen steps consumes fifteen times what a one-step scenario does. Zapier charges tasks, where a task is one successful action step, and triggers, polling, failed actions and built-in Formatter, Paths and Filter steps do not count.
That difference decides which platform is cheaper for you, and it is not a small effect. A long, branchy workflow run a modest number of times is dramatically cheaper on execution pricing than on per-step pricing. A short two-step workflow run tens of thousands of times can be cheaper on the per-step model, because you never pay for depth you do not use. Run the volume through both units before you accept anyone's comparison, including ours.
For reference, Make.com published a free tier at 1,000 credits with Core at $9 a month, Pro at $16 and Teams at $29, each starting from 10,000 credits, as of August 2026. Zapier on annual billing published a free tier at 100 tasks a month, Professional from $19.99 for 750 and $49 for 2,000, and Team from $69 for 2,000 and $119 for 5,000, with monthly billing running about 50 percent higher. Those are three different currencies of consumption wearing the same dollar sign.
A poor result here usually means one of two things. Either the resolution rate is honest and low, in which case the workflow needs narrowing until the agent can finish what it starts, or the manual cost per item is genuinely small, in which case volume has to be very large before automation is worth the maintenance. Neither is a reason to change platform. Both are reasons to change the workflow.
A worked example: chasing overdue invoices at an accounting firm
Take a bookkeeping team chasing overdue invoices. The volume is 900 reminder cycles a month across their client base. Today someone opens the ledger, checks whether payment landed, drafts a polite chaser, sends it and logs the result. Timed honestly that is about six minutes of work, which at a loaded rate near $35 an hour is roughly $3.50 per item. Enter 900 volume, $3.50 manual cost, and a resolution rate of 70 percent, because the awkward cases where a client disputes an amount still go to a person.
That gives 630 resolved items and a gross monthly saving near $2,200. The AI cost per item on a workflow that reads a record, drafts three sentences and writes a log line is small, well under a cent for most current models, so inference barely moves the total. The 5 percent operations overhead takes about $110. Net lands close to $2,000 a month before the platform bill.
Now add the platform. At 900 runs a month this workflow sits inside the n8n Starter tier at 2,500 executions, because n8n counts the run and not the eleven nodes inside it. The same workflow on credit-based pricing would consume roughly eleven credits per run, close to 10,000 credits a month, which puts it into a paid tier immediately. That is the pricing-unit effect in one paragraph, and it is why invoice chasing is one of the workflows where execution pricing wins clearly.
The honest caveats on this example are worth as much as the numbers. Six minutes per item is a measured figure, not a remembered one, and it should be measured in your own firm before you trust the output. The 70 percent resolution rate assumes a clean connection to the accounting system; without one, a person still has to confirm whether payment landed, and the resolution rate collapses toward zero no matter how good the drafting is.
The limits: what this cost model leaves out
The calculator does not include your platform subscription, your telephony or messaging fees, or any per-message carrier charges. In the United States, automated business texting also requires A2P 10DLC registration, which our own cost research puts at $2 to $50 a month, small but routinely missing from quotes. None of that appears in the output, so treat the net figure as pre-platform.
It does not model failure. Real workflows retry, hit rate limits, and occasionally process the same item twice, and each of those consumes budget without producing value. Nor does it model the cost of a wrong output reaching a customer, which on a chasing or messaging workflow is the risk that actually matters. A single message sent to someone who already paid costs more goodwill than the workflow saves that day.
It assumes a flat cost per item on both sides. In practice, manual cost per item varies enormously between an easy case and a hard one, and the agent usually resolves the easy ones. That means the items left for a person are, on average, more expensive than the average you entered, so the true saving is somewhat lower than a flat model suggests. If you want to correct for this, price the manual cost using only the simple cases.
Finally, it is silent on self-hosting. Running n8n yourself removes the subscription and replaces it with server cost, upgrades, backups, and someone's attention when it stops at two in the morning. That is a genuine trade and it can go either way depending on what your time is worth. Model the running cost of both before you assume free software is free.
n8n Cloud tiers, verified against the pricing page
The numbers the calculator uses come straight from n8n's published pricing. The Starter plan costs 20 euros per month billed annually, or about 24 euros month to month, and includes 2,500 workflow executions, 5 concurrent executions, and 2,300 AI credits for model calls. Pro is 50 euros per month billed annually for 10,000 executions and 20 concurrent runs, Business is 667 euros per month for 40,000 executions with SSO and Git-based version control, and Enterprise is custom with 200 or more concurrent executions. Every plan includes unlimited users and unlimited workflows.
The definition doing the economic work is n8n's own: an execution is a single run of your entire workflow, regardless of how many steps it contains or how much data it processes. That sentence is why the calculator asks for executions and steps separately. On n8n, steps are free and only runs count; on Zapier, every step in a Zap consumes a task; on Make.com, every module action consumes a credit. The same automation portfolio can therefore sit in a different price class on each platform without any difference in what it does.
Watch two tier boundaries when projecting growth. Concurrency limits bite before execution limits for workflows triggered in bursts, because a Starter plan queues anything beyond 5 simultaneous runs, which can matter for webhook-driven workloads even at low monthly totals. And the jump from Pro at 50 euros to Business at 667 euros is the steepest cliff in the lineup, so a portfolio approaching 10,000 executions should evaluate self-hosting economics before it hits the wall rather than after.
The cross-platform math on a real workflow
Take a concrete portfolio: one 8-step workflow running 2,000 times a month plus two smaller 4-step workflows running 500 times each. On n8n that is 3,000 executions, just above the Starter allowance, so it fits Pro at 50 euros or Starter with headroom management. On Zapier the same portfolio consumes 20,000 tasks per month, which is far beyond the 750-task Professional entry tier at 19.99 dollars and requires a much higher task tier. On Make.com it consumes roughly 20,000 credits, double the 10,000 credits included with Core at 9 dollars.
The ranking is workload-dependent, which is the calculator's whole point. Flip the example to five single-step notification zaps running 100 times a month, 500 tasks total, and Zapier's entry tier covers it for under 20 dollars with the least setup effort of the three, while an n8n instance would be underused. Make.com's generous 10,000 credits at 9 dollars makes it the value pick for mid-complexity, mid-volume portfolios. n8n's advantage compounds specifically as steps multiply and volume grows, because its price is insensitive to both steps and, when self-hosted, largely to volume.
Add the AI line separately on every platform, because it is billed separately. n8n Cloud includes AI credits, 2,300 on Starter, but serious AI workflows bring their own OpenAI or Anthropic key, and those model calls are invoiced by the provider on top of any platform fee. A workflow making five model calls per run at 3,000 runs a month generates 15,000 calls whose cost depends entirely on prompt size and model choice, and on AI-heavy portfolios this line routinely exceeds the automation platform fee itself.
Self-hosting economics with real 2026 infrastructure prices
The n8n Community Edition is free to self-host for internal business use under n8n's Sustainable Use License, a fair-code license whose main restriction is that you cannot resell n8n itself as a hosted service. The infrastructure is genuinely cheap: Hetzner's current shared vCPU plans run roughly 4 to 9 euros per month after its June 2026 price adjustment, and DigitalOcean droplets suitable for n8n run 6 to 24 dollars per month depending on memory. A capable n8n server costs less per month than a single Zapier Professional seat.
The honest self-hosting total adds labor: Docker updates, backups, SSL, security patches, and the debugging session when an update breaks a community node, realistically two to five hours per month. Priced at anything like the market rate for the person doing it, labor dominates the server bill several times over. Managed middle grounds split the difference: Sliplane hosts n8n from 9 euros per month per server and Elestio from around 11 dollars per month, buying you updates and backups while keeping data on dedicated infrastructure.
The decision rule the numbers support: n8n Cloud until the portfolio outgrows Pro, self-hosting when volume pushes toward the 667 euro Business tier, when data residency demands it, or when an agency can amortize one instance and its admin hours across many client workloads. At 40,000 executions per month, the choice is between 667 euros on Business and roughly 10 euros of server plus a few admin hours, which is exactly the kind of gap that justifies hiring the DevOps competence if you do not have it.
What changed in 2025 and 2026
Platform viability stopped being a discount factor in the math. n8n raised a 180 million dollar Series C at a 2.5 billion dollar post-money valuation in October 2025, led by Accel with NVIDIA's venture arm participating, on the back of roughly tenfold usage growth, more than 3,000 enterprise customers, and reported annual recurring revenue above 40 million dollars. Betting a client automation portfolio on n8n in 2026 is a mainstream infrastructure decision, not an open-source gamble.
The comparison denominators moved underneath old spreadsheets. Make.com shifted its billing language from operations to credits during 2025, Zapier continued pricing agent activities separately from automation tasks with overages at 1.25 times the base rate, and Hetzner announced higher prices for its compute plans effective June 2026. None of these changes flips the structural ranking, n8n still wins multi-step volume, but they are why the calculator carries a verification date and why any annual commitment deserves a fresh look at the official pricing pages.
AI moved inside the workflows and changed what drives cost. With around 75 percent of n8n customers using its AI capabilities and agent nodes becoming ordinary workflow steps, the marginal cost question shifted from platform fees toward model calls, retries, and the review time AI outputs demand. The durable advice: re-run this calculator quarterly, whenever any workflow's volume doubles, and before quoting a client retainer, because in this stack the cheapest configuration is a moving target and the recalculation takes five minutes.
At a glance
n8n hosting and platform cost options (verified July 2026)
| Option | Price | What is included |
|---|---|---|
| n8n Cloud Starter | EUR 20/mo (annual) | 2,500 executions, 5 concurrent, 2,300 AI credits |
| n8n Cloud Pro | EUR 50/mo (annual) | 10,000 executions, 20 concurrent, admin roles |
| n8n Cloud Business | EUR 667/mo (annual) | 40,000 executions, SSO, Git version control |
| Self-hosted (Hetzner VPS) | ~EUR 4-9/mo plus 2-5 admin hours | Community Edition, unlimited executions on your hardware |
| Self-hosted (DigitalOcean) | $6-24/mo plus admin time | Droplet sized to workload |
| Managed n8n (Sliplane, Elestio) | From ~EUR 9-11/mo | Hosting, updates, and backups handled |
What mistakes should you avoid?
- Comparing platforms on subscription price when per-step versus per-execution billing is what actually moves the total.
- Forgetting that AI model calls are billed by the provider on top of n8n, often exceeding the platform cost.
- Calling self-hosting free while ignoring the two to five monthly admin hours it actually consumes.
- Quoting client automation work without a maintenance line, then absorbing every API change unpaid.
- Never revisiting the math as volume grows, missing the point where a different hosting tier or platform becomes cheaper.
FAQ
- How does n8n pricing actually work?
- n8n cloud bills per execution, where one execution covers a whole workflow run no matter how many nodes it contains. Published cloud pricing as of August 2026 is Starter at EUR 20 a month for 2,500 executions, Pro at EUR 50 for 10,000, and Business at EUR 667 for 40,000, all on annual billing and quoted in euros only. That unit is why deep, branchy workflows are usually cheaper here than on per-step platforms.
- Is n8n cheaper than Zapier or Make?
- It depends entirely on the shape of your workflow, not the headline price. n8n counts one execution per run. Make.com counts credits at roughly one per module action. Zapier counts tasks, one per successful action step, with triggers, polling, failed actions and Formatter, Paths and Filter steps excluded. A long workflow run occasionally favours n8n heavily. A two-step workflow run tens of thousands of times can favour the per-step platforms.
- What resolution rate should I enter?
- Enter the share of items the agent finishes end to end with no human touch, and be strict about it. An item that the agent drafts but a person edits before sending is not resolved. Most first workflows land between 50 and 75 percent once you count exceptions honestly. This input has more influence on the output than any other, so guessing high here is the fastest way to a number you cannot defend to a finance team.
- Does the calculator include the platform subscription?
- No. It prices the workflow economics, meaning labour saved against inference and a flat 5 percent operations overhead. Your platform subscription, telephony or messaging fees, and in the United States A2P 10DLC registration, which our automation cost pages put at $2 to $50 a month, all sit on top. Subtract them from the net monthly figure before comparing the result to anything.
- Is n8n cheaper than Zapier?
- Usually yes for multi-step workflows at volume, because n8n charges per execution while Zapier charges per task, so a 15-step workflow costs one n8n execution but 15 Zapier tasks. For a few simple, low-volume zaps, Zapier's convenience can be worth its premium. Run both pricing models at your real monthly volume before deciding; the ranking depends entirely on steps per run.
- How much does it cost to self-host n8n?
- The server is cheap: a capable VPS runs 10 to 40 dollars per month, and the community edition is free to run. The real cost is labor - Docker updates, backups, SSL, security patches, and debugging - typically two to five hours monthly. Priced honestly, self-hosting beats n8n Cloud mainly at higher volume or when data residency requires it.
- How does n8n pricing work?
- n8n Cloud bills by workflow executions per month, starting around 25 dollars, and an execution counts once no matter how many steps it contains. That per-execution model is n8n's core cost advantage over per-task and per-operation competitors. Self-hosted community edition has no license fee for standard use; you pay for infrastructure and your own time instead.
- Should an agency self-host n8n for clients?
- Only if infrastructure is genuinely part of your offer: you can commit to updates, backups, monitoring, security, and support response times, and you price that into retainers. Otherwise use n8n Cloud or a managed host and spend your hours on workflows, which is what clients pay for. A neglected self-hosted instance is a client-losing incident waiting to happen.
- What makes n8n workflows expensive to run?
- Three things, roughly in order: AI model calls billed by your provider on top of n8n, especially agent nodes with retries and large prompts; maintenance hours when APIs and credentials change; and execution volume growth pushing you into higher plan tiers. The platform fee itself is rarely the problem, which is why calculating all four layers matters.
Sources & further reading
Was this page helpful?
