n8n operating cost calculator

Estimate n8n operation from workflow volume, run duration, worker capacity, execution history, paid features and the integrations that remain.

Last updated

In short

  • An execution count alone does not describe memory, runtime or peak demand.
  • Community and paid self-hosted editions have different rights and features.
  • Include API charges, retained tools and workflow maintenance alongside hosting.
On this page (4)

Costs and savings · Part of n8n

Interactive worksheet · no sign-up

Estimate n8n automation costs

Use the same currency and scope for both options. Inputs stay in this page; they are not included in analytics or sent with an enquiry.

1. Your current bill
2. The replacement

Business management: CHF 1,590/month for up to 3 apps; onboarding from CHF 9,900. Infrastructure and paid licences are extra.

Additional metered worker runtime

Include only runtime not already in infrastructure. An execution count alone cannot determine this.

Downstream billable API calls

External API, AI, SMS and enrichment charges continue after moving the orchestration.

A SaaS task, an n8n execution and a worker-hour are different units. Measure your workflow, retries and peak concurrency before deriving the replacement capacity.

3. Transition and overlap
Optional: value internal operating time

Time released is capacity, not automatically payroll or cash saved. Keep time already billed by Pilae or another supplier out of these fields.

How the calculation works
  1. Current monthly invoices = billed units × unit price + additional current spend.
  2. Replacement monthly invoices = Pilae management + additional infrastructure + target licences + workload usage + retained services.
  3. Transition = plan onboarding + new hardware + extra migration + training + parallel months × max(0, current invoices − retained services). Parallel months are capped at the comparison horizon.
  4. Total invoices = monthly invoices × horizon, plus transition for the replacement. Payback uses the full transition commitment divided by positive monthly invoice saving, including all entered overlap months even beyond the selected horizon.
  5. Economic saving adds the change in valued internal operating time. It does not assume headcount reduction.

Business includes up to 3 apps, then a published per-app fee (CHF 390 in CHF). Starter’s published CHF price is CHF 449/month. All Pilae figures come from the same price data as the pricing page. Workload inputs are your estimates, not supplier quotes. Taxes, price growth, discount rates, opportunity costs and differences in functionality are outside this arithmetic.

Two n8n workflows that each run once can have very different costs. One reads a small record; another downloads hundreds of documents, calls an AI model and waits on an external system. The calculator estimates the commercial envelope. Size the runtime from the work inside those executions.

Build a workload inventory

Export a representative period of run history and classify the workflows people depend on. Include monthly and quarterly jobs that a short observation window misses. Record duration, peak arrivals, typical payload size, binary files, external calls and the consequences of a missed or duplicated run.

Workflow class Capacity driver Cost often missed
Small scheduled sync Number of runs and API rate limits Connector maintenance
Large import Memory, records per batch and write rate Recovery from partial completion
Document processing Binary storage and CPU or model calls Extraction and API charges
Webhook intake Bursts and acceptable queue delay Public ingress and retries
Long-running approval Waiting state and durable history Retention and operational ownership

Do not equate a SaaS task count with an n8n execution count. One workflow can contain many operations, and licensing definitions should be read from the current n8n plans.

Price the chosen deployment shape

A single service is simpler to operate than a worker pool, but may not meet the workload. In queue mode, execution work is distributed through workers with shared dependencies. That introduces database, queue, networking, secret and monitoring requirements. More workers do not remove bottlenecks in a slow external API or database.

Budget capacity for the busy period and measure queue waiting time. A workflow that takes three minutes at lunchtime is not acceptable merely because the daily average looks inexpensive. Separate interactive webhook deadlines from overnight imports that can wait.

The licensing guidance distinguishes permitted internal use from arrangements requiring a commercial agreement. Check the actual hosting arrangement and required enterprise features. Paying an operator is not the same as buying every n8n feature.

A simple utilization example

Suppose a worker handles ten jobs a minute under a representative test, while the busiest period brings thirty. Three workers would match arrival rate only under those test conditions, with no spare capacity for failures or variability. It is a starting hypothesis, not a production recommendation. Add a failure scenario and measure the oldest queued job before accepting the design.

For the cost model, enter actual machine quotes, required licences, service operation and external API spend. Include the time to update workflows when source systems change. The live calculator reads Pilae service pricing centrally; infrastructure and migration still need a scoped estimate.

Count data and failure handling

Execution history, binary files and database indexes grow differently. Decide what is retained for debugging, how failed inputs are protected and when sensitive payloads are deleted. The execution-retention guide helps separate those decisions.

Before ending an existing subscription, recreate credentials, validate outputs and test failure paths. Protect the encryption material needed to read stored credentials and verify recovery into an isolated environment. If both old and new workflows can write, prevent double actions during the comparison period.

A lower infrastructure bill does not prove a cheaper automation service if someone must spend more time maintaining the flows. Keep that residual work in the model and compare the specific functions being replaced. The Zapier migration guide is useful for a move from Zapier; an existing n8n Cloud estate needs its own migration assessment.

Sources and further reading

Use the linked documentation to confirm the version, edition and contract that apply to your project.

Size our automation workload

Bring your current bill, required capabilities and workload assumptions. We will separate recurring operation from migration and retained services.