n8n Self-Hosted vs Cloud: Which One a Solo Operator Should Pick

n8n Self-Hosted vs Cloud: Which One a Solo Operator Should Pick

In short5 min read

  • Pick n8n Cloud if you have no one to patch, back up and monitor a server.
  • Self-hosted Community edition runs without a license key but lacks projects, sharing, SSO and Git.
  • n8n Cloud counts one execution per full workflow run, regardless of the number of steps.
  • n8n's docs list Docker Compose for production and say npm installation is deprecated from n8n 3.0.

Short answer: if you are a solo operator who does not want to be on call for a server, start on n8n Cloud. If you are comfortable running Docker, care more about removing execution limits than saving time, or need your data on your own infrastructure, self-host the Community edition. Many people do both: prototype on Cloud, then move heavy or sensitive workflows to a self-hosted instance once they know what they actually run.

The rest of this guide explains the trade-offs in limits, maintenance, backups, and security, using only what n8n’s own pricing page and documentation say as of November 2026. If you are still deciding whether n8n is the right tool at all, or want the plan-by-plan price table, our n8n vs Make vs Zapier comparison covers that first.

In this article

  1. The core difference: who runs the machine
  2. The Cloud limits that actually decide it
  3. What you give up with the free Community edition
  4. The hidden cost of self-hosting: you are the ops team
  5. Security and data control
  6. A decision framework for solo operators
  7. Before your first production workflow

The core difference: who runs the machine

On Cloud, n8n hosts the instance and you work within your plan’s execution limits. Self-hosted, you run it on your own server, and n8n’s hosting docs say that without a license key it runs as the free Community edition. So the real question is not which version has more features. It is whether you want to trade a monthly fee for server work.

Choosing n8n Cloud or Self-Hosted: Estimate monthly runs, Check run duration, Assess ops skills, Check data rules, Start and export, Review after 30 days

The Cloud limits that actually decide it

You do not need the whole price list to make this call. Three limits on n8n’s pricing page do most of the work.

Executions per month. Starter includes 2,500 workflow executions a month and Pro includes 10,000. The page defines an execution as a single run of your entire workflow, regardless of the number of steps or the amount of data processed, so a 30-step workflow that runs once is one execution.

Maximum run time. A single execution can last up to 5 minutes on Starter and 40 minutes on Pro. This is the limit solo builders miss most often. If you run long AI jobs, large scrapes, or batch processing, check whether one run could exceed it.

What happens when you go over. The pricing FAQ says workflows keep running after you pass your quota, and overage charges may apply unless you move up a tier. Overage is listed as capped on Starter and Pro.

One more detail from the same page: the Business plan is currently available only for self-hosted n8n, with a waitlist for a hosted version. For current prices in your currency, check the official pricing page, which shows prices in your local currency.

What you give up with the free Community edition

n8n’s documentation lists the features not included in the Community edition:

  • Projects, and sharing of workflows and credentials
  • SSO, including SAML and LDAP
  • Version control using Git, and environments
  • External secrets and custom variables
  • External storage for binary data
  • Log streaming
  • Multi-main mode

The same page says registering the Community edition gets you a free license key that unlocks folders, debug in editor, and custom execution data. For a one-person business, most of the missing features are team and compliance tools you may never need. The ones solo operators are most likely to miss are Git-based version control and sharing with a contractor.

The hidden cost of self-hosting: you are the ops team

Self-hosting removes the monthly plan, but not the cost. You pay for a server, and you pay in attention. According to n8n’s hosting docs:

  • Docker Compose is the listed option for production deployments with databases and additional services.
  • A one-line setup installs n8n locally in one step; it requires Docker on Linux or macOS, or WSL on Windows.
  • npm installation is deprecated from n8n 3.0, so do not build a new production setup on it.

Then there is data. n8n’s database settings docs say self-hosted installations use SQLite by default to store credentials, past executions, and workflows, with PostgreSQL available through environment variables. Either way, that database is your business logic. Backing it up is your job, and so is testing that a backup actually restores.

A common way this goes wrong: a server runs fine for months, then a full disk or a rushed upgrade takes down workflows that were never exported anywhere else. Cloud removes the server, but not the value of your own copies. Export your critical workflows as JSON whichever option you choose.

Security and data control

Self-hosting gives you full control of where data lives, which matters if a client contract says their data cannot sit on a third-party platform. It also means patching, firewall rules, HTTPS, and credential protection are yours. If you would not notice an exposed admin panel for a week, that control is a liability.

Cloud shifts infrastructure security to n8n, while you still control credentials and who has access to your account. For most solo operators without a contractual requirement, that is the safer default.

A decision framework for solo operators

Answer these five questions. If most answers land in the Cloud column, start there.

Question Points to Cloud Points to self-hosted
Can you maintain a Linux server with Docker? No, or not reliably Yes, and you enjoy it
How many full workflow runs per month? Comfortably under your plan’s limit High volume, frequent polling
Do runs last longer than 5 minutes? Rarely, or Pro’s 40 minutes is enough Often, with long batch jobs
Does client data need to stay on your infrastructure? No contractual requirement Yes, required by contract
Is downtime costly to you? Yes, and you cannot fix it fast You can recover quickly yourself

A practical middle path: build and test on Cloud, export workflows as JSON, and move only the high-volume or data-sensitive ones to a self-hosted instance later. That keeps you shipping while you learn your real usage. If cost is your main driver, our guide to when Make or n8n actually saves you money over Zapier helps frame the numbers, and the n8n automation hub has workflow builds for both setups.

Before your first production workflow

Whichever side you land on, do these five things before a client or a lead depends on the instance:

  • Build one real workflow and note its execution count and longest run time for a week.
  • Turn on error alerts so a failed run reaches your inbox or Slack.
  • Self-hosted only: schedule database backups and restore one onto a spare machine.
  • Self-hosted only: put the editor behind HTTPS and a login you did not reuse elsewhere.
  • Put a monthly reminder on your calendar to export workflows and review usage.

Sources: n8n.io/pricing, docs.n8n.io/hosting, docs.n8n.io/hosting/community-edition-features and docs.n8n.io/hosting/configuration/supported-databases-settings, checked November 2026.

Check your longest workflow run against the 5-minute Starter limit

Write down your expected monthly workflow runs and your longest run time today. Compare those two numbers with the plan limits on n8n's official pricing page, and the right hosting choice usually becomes obvious.

Get new AI automation playbooks by email

One email when new guides and case studies go up. No spam, unsubscribe anytime.

Responses

  1. […] will notice a failed sync before a customer does. The trade-offs are similar to the ones covered in n8n self-hosted vs cloud, where control and low cost trade against maintenance […]

  2. […] does not mean free: you pay for the server and you own updates, backups and uptime. Our guide to n8n self-hosted vs cloud walks through that […]

  3. […] n8n Self-Hosted vs Cloud: Which One a Solo Operator Should Pick […]

  4. […] a self-hosted install. If you’re unsure which suits a one-person business, read our guide to n8n self-hosted vs cloud before you sign […]

Leave a Reply