n8n Cloud or self-hosting: choose who does the operating work

Cover: AI-generated editorial illustration.

Choose an operating model by deciding who will maintain it. A low server bill does not remove updates, backup work, credential management, or the need to investigate failures.

CiteLab’s current workflows run on a self-hosted instance. That gives us practical experience with our own environment. We have not run a controlled comparison against n8n Cloud, so this guide uses the official documentation to explain the decision rather than claiming a measured winner.

Start with the responsibility split#

Question	n8n Cloud	A self-hosted setup
Who operates the hosting platform?	n8n provides the hosted service	You or your hosting/operations provider
Who designs and checks workflow logic?	You	You
Who configures external accounts and integrations?	You	You
Who plans server updates and recovery?	Hosting responsibilities depend on the service terms	You need an explicit plan for your deployment
What should you check before choosing?	Current plan limits, access needs, costs, and applicable terms	Hosting resources, backups, access, updates, monitoring, and applicable license

Cloud hosting does not make an incorrect expression correct. Our own lost-job-ID bug was in the workflow’s data reference, not a problem that changing servers would necessarily solve.

Count more than the subscription#

Use a simple worksheet:

Monthly operating cost =
  platform or server charges
  + any backup or storage charges
  + connected service charges
  + time spent maintaining and recovering the setup

Do not assume that a free software edition means every connected service is free. Email, messaging, paid APIs, and optional AI calls may have separate costs. Count only the services your actual workflow uses.

Plan details change. Check n8n’s current pricing and billing period before purchasing, rather than treating a number in a tutorial as a permanent quote.

When Cloud deserves a closer look#

A managed service is worth evaluating when you want to focus on workflows and have limited interest in operating a server. Verify that the plan supports your expected volume and access needs, and establish how you will export and recover your work.

You still need to validate inputs, handle repeated events, control outgoing actions, and inspect results. Those responsibilities are visible in our draft-generation example.

When self-hosting deserves a closer look#

Self-hosting may fit when you understand the infrastructure, need an appropriate level of control, and can maintain the deployment. n8n publishes self-hosting installation options for several providers.

Before relying on it, document account ownership, backup and restore procedures, credential handling, update responsibilities, and who receives failure alerts. A working demonstration on a home server is not evidence that it is ready to carry another business’s production work.

A small decision exercise#

Write down the next three workflows you actually need. For each, identify its trigger, connected accounts, expected volume, acceptable delay, and consequence of failure. Then compare suitable operating options against those needs.

If you cannot explain how to recover the setup, use that as a learning task before moving an important process onto it. Our workflow review tool provides an editable record of those questions.

The external links in this guide are ordinary links at publication. No affiliate relationship or comparative performance result is being claimed.