n8n Cloud or self-hosted: a small-business decision guide

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

The choice is about operational ownership

n8n offers managed Cloud and self-hosted deployment options. Its documentation separates that deployment choice from the choice of plan or edition. Cloud hands infrastructure management to n8n; self-hosting gives your team responsibility for its own environment. For a small business, the useful first question is who will maintain and recover the service when the original builder is unavailable.

Write down the owner before the budget

Assign one person to the business outcome and one to the operating environment. The business owner decides whether a completed workflow is correct. The technical owner handles the environment, updates and recovery. Those roles may be filled by one person in a small company, but write both responsibilities down. A workflow with no backup owner becomes difficult to rely on during holidays or a supplier change.

Imagine a five-person agency using automation to create project records from accepted enquiries. Its operator should be able to explain where the workflow runs, how access is revoked when someone leaves, how failed inputs are identified and how the destination is reconciled after recovery. These are operating questions rather than claims that one deployment option automatically guarantees a particular security or compliance outcome.

Use a total-cost worksheet

A self-hosted server bill covers only one part of operating the system. For an illustrative budget, assume USD 15 per month for infrastructure, USD 5 for backup storage and two hours of operator time valued at USD 60 per hour. That is USD 140 per month before setup work, any paid n8n edition and connected app or AI-provider charges. These numbers are invented assumptions for the worksheet, not vendor prices or a real customer result.

Build an equivalent Cloud column using its current quote and the operating work your team still performs. Cloud can remove infrastructure tasks while leaving workflow design, permissions in connected apps, error handling and business reconciliation with you. Compare both columns at the same volume and required features. Do not compare a free edition with a paid edition while assuming that their feature entitlements are identical.

Choose Cloud when the operating capacity is missing

For a team that needs a quick start and has nobody assigned to maintain infrastructure, managed Cloud is a sensible option to investigate. This is an editorial decision rule based on ownership, not a benchmark verdict. Check the selected plan's limits, features, data requirements and support arrangements against the workflow you intend to run.

Write down which work remains yours. Who updates a broken mapping when a CRM field changes? Who checks whether a successful run produced the right record? Who receives an alert and has permission to intervene? Managed hosting does not replace those business responsibilities, and leaving them implicit can make either deployment choice disappointing.

Choose self-hosting when control has an owner

Self-hosting is worth investigating when you have a concrete deployment requirement and a person or provider who can operate it. Specify the requirement rather than using control as an abstract benefit. For example, record the environment you need to manage, the integration constraint it solves and how you will verify that the selected edition supports it. Get current licensing and feature details from n8n before committing.

Use a recovery exercise as part of the evaluation. With synthetic data, demonstrate how the service is restored, how the operator obtains required access and how completed destination records are distinguished from work that still needs processing. Record the steps and the time observed in your own trial. This guide has not performed that recovery exercise or measured either option's availability.

Keep a short acceptance checklist

1. Name the business owner, technical owner and backup operator.
2. Record the required integrations, selected edition and current quote.
3. Test one normal case, one rejected input and one repeat submission.
4. Demonstrate a recovery path and reconciliation using synthetic records.
5. Compare recurring costs, initial setup and the work that remains with your team.

The better choice is the one your business can operate reliably for its actual workflow. Revisit the decision when the workflow becomes business-critical, operating responsibility changes or a new feature requirement appears. A cheaper infrastructure line alone does not settle that decision.

Make an operations rehearsal part of the hosting decision

Whichever hosting route you choose, nominate an owner for failed runs and rehearse recovery with synthetic data. Ask that person to trace one production webhook, reconcile a multi-page read, receive a controlled failure alert and restart an interrupted write without creating duplicates. If the team cannot explain those steps, include training and operational support in the ownership estimate before comparing hosting invoices.