n8n self-hosted vs Cloud: compare the real operating budget

Start with the workflow and its owner

Choose n8n Cloud when its current plan fits the work and you want to buy a hosted service. Consider self-hosting when you have a specific infrastructure requirement and someone responsible for operating it. A small server invoice alone cannot settle that choice. This is a budgeting framework, not a performance benchmark or an installation we have tested.

n8n documents a self-hosted Community edition and licensed self-hosted editions. Its public pricing describes paid plans using monthly workflow executions. Hosting model, edition and required features are separate decisions: compare the exact combination you would use. Primary documentation was checked on November 3, 2026; verify current terms before buying.

Fill in the same worksheet for both options

Put an owner and evidence beside each estimate. An invoice supports a hosting number; a timed maintenance exercise supports an effort estimate. An untested assumption should remain labeled as an assumption. Do not treat an unavailable cost as zero, and do not add the same model bill twice if a service already includes it.

A worked example with deliberately hypothetical numbers

Suppose a hypothetical hosted option costs 60 currency units per month for the workload you need, and administering workflows takes one hour. Suppose a self-hosted option costs 18 for compute, 7 for backup storage, and three hours for the combined workflow and infrastructure work. Value an hour of that person's time at 30. These are invented inputs for the worksheet, not vendor prices or measured maintenance times.

The hosted estimate is 60 + (1 × 30) = 90. The self-hosted estimate is 18 + 7 + (3 × 30) = 115. Add the same external API costs to each if the usage is identical. If only 500 jobs produce accepted results, the estimates before those API costs become 0.18 and 0.23 per accepted job. A different workload or maintenance requirement can reverse the result.

The useful question is how sensitive the decision is to the uncertain inputs. In this example, self-hosting reaches the same 90-unit total when combined monthly administration takes (90 − 25) ÷ 30, or approximately 2.17 hours. Use that threshold to decide what to measure next rather than assuming every future month will match the estimate.

Budget for the recovery you would actually need

This checklist describes work to plan and verify. It does not assert that a particular n8n plan supplies a backup or recovery guarantee. Read the current documentation and agreement for the edition and deployment you select.

• Write down which workflows matter, who responds to a failed run, and how long an interruption is tolerable.
• List the data, credentials and configuration that your recovery plan depends on; define who can access them.
• Ask how you would detect missing or duplicated work after a restart. A running process is not proof that every business result was saved.
• Schedule a restore exercise in a safe environment and record what you restored and how long it took.
• Define the maintenance window and how you would recover from a failed update before counting administration as negligible.

Make a decision you can revisit

Record a small decision table: expected accepted jobs, required capabilities, monthly cost range, responsible person and recovery requirement. Keep the uncertain high-impact assumptions visible. Choose the option that satisfies those requirements at an acceptable operating cost, then review it after an observed period of real work.

If you cannot name an operator or describe recovery, self-hosting needs more preparation. If a Cloud plan lacks a required capability, a cheaper invoice does not solve that gap. The decision can change as the workload, feature requirements or available team time changes.

• Compare n8n and Make billing units ↗
• Build the full AI workflow cost estimate ↗
• Get the blank workflow cost template ↗