n8n pricing and total costs: Cloud or self-hosted?

The following selection was checked on the official n8n pricing page on 27 September 2026. It reflects the annual billing selection shown there. Monthly billing is a separate contractual choice. Check tax, checkout location, additional services and the final order independently.

The table shows four n8n plans from the official n8n pricing page with their monthly equivalent when billed annually, the monthly executions included and the deployment.

Community Edition is another self-hosted option within its licence conditions. This table is not a complete feature comparison. Check concurrency, shared projects, permissions, retention and support separately. A plan can provide sufficient executions while lacking a governance feature your organisation requires.

What counts. An n8n execution is a workflow run. To budget properly, examine the process: how often does it start, which other workflows start independently, how many retries are expected, and which calls or features count under the selected plan? Validate your estimate against a representative pilot and the usage display in your account.

Consider an illustrative example. Sixty form enquiries per working day over 22 working days produce 1,320 incoming cases. Add one daily reconciliation workflow, approximately 30 starts. That gives 1,350 planned starts before retries and unrelated workflows. This is a planning assumption, not measured consumption or a guarantee of the bill.

Illustrative example: five-minute schedule. By comparison, a schedule running every five minutes starts 8,640 times during an assumed 30-day month. If it mostly checks for unchanged data, the trigger deserves more attention than the number of processing steps. An event supported by the source application may avoid unnecessary polling. However, event delivery, repeat notifications and recovery after missed events must then be designed properly.

Separate units. Do not simply combine message volume, API calls and executions in one number. They are different units. Record which unit each supplier bills and preserve those distinctions in the spreadsheet.

The following scenarios are calculation examples only. They explain why an identical number of business cases can create different technical costs. Before selecting a plan, reconcile planned starts with the actual workflow and the account’s billing rules.

Event-driven office process: Each of 1,500 new cases starts once. Assuming an additional five percent for retries produces 75 more starts. Adding 30 daily reconciliation runs gives 1,605 planned starts. That is numerically below 2,500, but concurrency and required features still need checking. Execution count alone does not establish that the plan is suitable.

Scheduled reconciliation: A workflow checks for changes every five minutes. In a 30-day month that produces 8,640 starts before additional checks or retries. The same business volume can therefore need a different allowance from an event-driven design. Whether a webhook is more economical also depends on the work required for dependable delivery and recovery of missed events. The cheapest architecture is not automatically the one with the fewest starts.

Document processing with AI: A business processes 800 documents per month. Platform costs may remain modest while OCR, model calls, storage and human review dominate. An assumed €0.08 per document produces €64 in external charges; €0.60 produces €480. These invented unit values are not vendor prices. An average of two minutes of human review per document also creates around 26.7 hours of work. That remaining effort belongs in the benefit calculation.

Separate budget lines. n8n can call paid APIs, request document extraction and use language models. Put these charges on separate budget lines. A platform subscription does not automatically cover every connected provider.

Units of each supplier. Estimate model costs from realistic inputs and outputs. A short contact note and a hundred-page document are different workloads. OCR may be priced by page, communications by message or minute, and storage by volume and retention. Use the units in the actual supplier contracts.

Exceptions. Budget for exceptions as well. If an unsupported file is submitted to a paid extraction service five times, you may incur repeated charges without obtaining a usable result. Bounded retries and a clear stopping condition protect both quality and expenditure.

Pilot cases. For a pilot, capture the cost of a normal case, a large case and a failed case. A single average from ideal examples can hide an expensive tail. Set a review threshold so that a change in document size or conversation length triggers investigation before the monthly invoice arrives.

When you use cloud hosting, you still need someone responsible for the rules the workflow follows. Running your own infrastructure does not automatically save money. Compare both alternatives using the same service boundaries:

Internal work. Do not price internal work at zero. If an employee spends two hours a month on maintenance, checks and incidents, include that effort. Existing operating capacity can make self-hosting attractive; missing absence cover can make it expensive and difficult to sustain.

Recovery time. The comparison should also account for your required recovery time. A workflow supporting an internal weekly report and a workflow supporting urgent customer requests may need different operating arrangements even when their execution counts are identical.

The following numbers are invented assumptions for one bounded office process. They are not modernagents prices, market averages or results from a measured customer project.

The table lists the five invented assumptions behind this first-year budget for one bounded office process.

First-year total. The first year totals €4,800 plus twelve months at €250: €7,800. A subsequent year without another implementation phase would budget €3,000 under the same assumptions. This does not promise that substantial changes will never be needed.

Sensitivity. Now test the sensitivity. If recurring expenditure rises to €500 per month, the first year becomes €10,800. If a one-off interface change costs another €2,000, the original scenario becomes €9,800. These alternatives reveal which assumptions deserve the most careful technical examination and commercial discussion.

Changes of unknown scope. Keep a separate allowance for changes whose scope is not yet known. For example, adding another legal entity or introducing a new approval policy can be a new project rather than a routine maintenance task.

Assumed time value. For an illustrative capacity calculation, assume 600 cases each month, three genuinely saved minutes per case and an internal fully loaded rate of €40 per hour. That produces 30 hours or €1,200 in calculated time value per month. Subtract the assumed €250 recurring cost and the difference is €950 before other effects.

No guaranteed saving. That is not guaranteed cash saving. Released time must be usable, correction work must be counted, and salary expenses do not automatically disappear. During the pilot, measure remaining review time, exception handling and the consequences of errors. Only the difference from the previous total workload supports a credible business case.

Payback estimate. A simple payback estimate divides the €4,800 initial investment by the usable monthly net benefit. At the hypothetical €950, payback is roughly five months. At €200, it is 24 months. The result changes whenever the assumptions change.

Decision calculation. A simple decision calculation is the monthly usable value of time released minus ongoing total costs. To recover implementation within a chosen period, allocate its cost across those months for planning purposes. This is an operational calculation, not accounting depreciation.

Threshold with three minutes. Assume €4,800 implementation and €250 monthly running costs. Recovering the initial investment over twelve months requires €650 of usable value each month: €400 towards implementation and €250 for operation. If three minutes per case are genuinely released after review and rework, and the assumed hourly value is €40, each case contributes €2. The resulting threshold is 325 cases per month.

Threshold with one minute. If only one net minute is released, the value falls to approximately €0.67 per case. The threshold rises to about 975 cases. If less of the released capacity can actually be used, it rises further. Measure the difference between the old and new complete handling process, including exceptions, rather than the duration of one replaced click.

What the pilot must establish. Use the calculation to identify what the pilot must establish. If your current monthly volume is 400 cases, the three-minute assumption is decisive. A demonstration that saves thirty seconds cannot support the same business case. Record the uncertainty before buying, then replace assumptions with observed handling times during the pilot.

Separate cost lines. Ask for separate lines covering implementation, recurring operation, usage-based services and future changes. Establish whether monitoring, recovery, updates and support are included. A promised response time is different from a promised resolution time.

Scope and assumptions. Document the assumed number of processes and monthly cases. Specify the included interfaces, fields and approval steps. Agree what happens when the target application changes or volume grows substantially. Ownership of accounts, workflow files and operating documentation also belongs in the scope.

Next inputs. The next useful inputs are your current total monthly workload, realistic transaction volume including peaks, and required features. Together, these support a defensible plan choice and first-year comparison without turning a low software subscription into an unrealistic forecast for the whole process.

Fictional options A and B. Consider two further fictional offers with the same business scope. Option A costs €50 in platform fees. Option B costs €25 for infrastructure but needs another one and a half hours of technical attention at an assumed internal rate of €60. Option B therefore costs €115 per month before any paid edition features are included.

What the example shows. This does not prove that cloud hosting is always preferable. Existing operating capacity or specific network requirements may change the decision. It shows that a €25 difference in platform or hosting charges can be outweighed by a small amount of additional work. Use real capacity, cover arrangements and agreed service scope in the comparison.

Baseline, peak and outage. Record a baseline, peak and outage assumption. A peak might be a seasonal month with twice the normal intake. The outage assumption describes controlled catch-up processing without repeatedly sending every transaction through expensive analysis. Give each scenario a warning signal and an owner. The result is a budget that can be managed, rather than a static price comparison.

Payment timing. Also check payment timing. Annual payment in advance affects cash flow differently from twelve monthly invoices. Keep that cash-flow plan separate from the monthly equivalent used to compare costs.

These pages cover the service overview and the related decisions for n8n costs:

• n8n implementation and workflow operations
• n8n Cloud or self-hosting: assign operating responsibility
• Maintain n8n workflows with business-level monitoring
• AI automation costs: a first-year budget for SMEs

For a workflow review, start with the task, systems involved and typical exceptions. Discuss it with modernagents.