DEV Community

SoloAgentFlow
SoloAgentFlow

Posted on Originally published at soloagentflow.com

n8n Cloud vs Self-Hosted: How a Solo Operator Should Choose (2026)

In short: 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's docs list Docker Compose for production and say npm installation is deprecated from n8n 3.0.

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.

This guide uses only what n8n's own pricing page and documentation say as of November 2026.

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. The real question is whether you want to trade a monthly fee for server work.

The Cloud limits that actually decide it

Executions per month. Starter includes 2,500 workflow executions a month and Pro includes 10,000. An execution is a single run of your entire workflow, regardless of the number of steps, 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. 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.

The Business plan is currently available only for self-hosted n8n, with a waitlist for a hosted version.

What you give up with the free Community edition

n8n's documentation lists these as not included:

  • 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

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, the ones you 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

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; 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.

Self-hosted installations use SQLite by default to store credentials, past executions, and workflows, with PostgreSQL available through environment variables. That database is your business logic. Backing it up is your job, and so is testing that a backup actually restores. 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. Cloud shifts infrastructure security to n8n, while you still control credentials and account access.

A decision framework

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.

Before your first production workflow

  • 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.

Originally published on SoloAgentFlow.

Top comments (0)