# n8n Cloud vs self-hosted n8n

> Choose n8n Cloud when you want n8n without running servers, backups or upgrades, and execution-based billing fits your volume. Choose self-hosted n8n when data must stay in your own environment, you run high volumes, or you need unverified community nodes and full configuration control. The free Community Edition has no execution fees, but you own uptime, security and upgrades.

|  | n8n Cloud | Self-hosted n8n |
| --- | --- | --- |
| Who runs it | n8n runs the infrastructure, upgrades and platform security | You run it on your own servers or cloud account |
| Billing model | Plan tiers with a monthly execution allowance; one execution is one full workflow run | Community Edition is free with no execution fees; Business and Enterprise use a paid license key |
| Your other costs | None beyond the plan | Server, database, backups, monitoring and engineer time |
| Data location | Workflow data is processed and stored in n8n's cloud | Everything stays in your environment |
| Community nodes | Verified community nodes only | Verified and unverified community nodes, plus your own custom nodes |
| Scaling | Handled by n8n within your plan | Queue mode with Redis and worker processes scales horizontally; multi-main setups need Enterprise |
| Reaching internal systems | Internal databases and APIs must be reachable from the internet or through a tunnel | Runs inside your network, next to internal databases and services |
| Enterprise features | SSO, log streaming and external secrets depend on plan | Community Edition lacks SSO, Git environments, log streaming and external secrets; Business adds SSO and Git environments, Enterprise adds the rest |
| Time to first workflow | Minutes | Hours to set up properly, longer for a production-grade deployment |

## Choose n8n Cloud if

- Nobody on the team wants to own servers, patching and backups
- Execution volume fits comfortably in a cloud plan
- Your data has no residency requirement that rules out a vendor cloud
- You want to start building today and decide on hosting later

## Choose Self-hosted n8n if

- Healthcare, finance or legal data must stay in your own cloud account
- You run high volumes and execution allowances are the main cost
- Workflows need to reach internal databases or services that should not be exposed
- You need unverified community nodes or custom nodes
- You have an engineer or partner to run upgrades, backups and monitoring

## The short version

n8n Cloud and self-hosted n8n run the same workflow engine. The difference is who operates it and where your data lives.

n8n Cloud is the right default for most small teams. You get a working instance in minutes and n8n handles upgrades, uptime and platform security. Self-hosting makes sense when data residency, volume, internal network access or custom nodes outweigh the cost of running it yourself.

## Where n8n Cloud wins

**No operations work.** No servers, no database backups, no upgrade weekends. For a company without an engineer who enjoys infrastructure, that is worth a lot.

**Fast start.** You can build and test workflows the same day, then revisit hosting once you know your real volume.

**Predictable responsibility.** When the platform has a problem, n8n fixes it. With self-hosting, your on-call person does.

**Verified nodes only.** The restriction to verified community nodes is also a safety feature. Unvetted packages are a supply-chain risk on any self-hosted instance.

## Where self-hosted n8n wins

**Data control.** Every payload, credential and execution log stays in your AWS, Azure or Google Cloud account, or your own data center. For regulated industries this often decides the question, and it simplifies conversations with auditors.

**Cost at volume.** The Community Edition has no execution fees. A team running hundreds of thousands of executions a month pays for servers instead of allowances.

**Internal network access.** A self-hosted instance can sit next to an internal Postgres database or a private API without exposing either to the internet. That matters when [connecting an LLM to internal data](/guides/connect-llm-to-internal-data/).

**Full configuration.** You control environment variables, execution timeouts, data retention, task runners and scaling. Queue mode with Redis and worker processes lets one instance handle much larger loads.

**Custom and community nodes.** Unverified community nodes and your own custom nodes are only available when you self-host.

## What self-hosting actually involves

A production self-hosted deployment needs Docker or Kubernetes, Postgres, automated backups, TLS, an auth layer in front of the editor, uptime monitoring and alerting on failed executions, and a routine for upgrades. Budget a few hours a month for maintenance on a small instance, more for a queue-mode cluster. If that work will not get done, choose Cloud.

## What we recommend

Start on n8n Cloud unless you already know data residency or volume rules it out. Move to self-hosted when a specific requirement appears, not on principle.

Lumeor sets up and maintains n8n on either option. Our [n8n automations work](/case-studies/n8n-automations-suite) shows the kind of workflows we build, and [the cost of an n8n automation program](/cost/cost-of-n8n-automation-program/) explains how we price builds and ongoing care.

## Frequently asked questions

### Is self-hosted n8n really free?

The Community Edition has no license or execution fees. You still pay for a server, a Postgres database, backups and monitoring, plus the engineer time to keep it patched and upgraded. For a small deployment the infrastructure is modest; the people time is the real cost.

### What does the free Community Edition leave out?

SSO and multiple environments with Git source control require a Business or Enterprise license, and log streaming and external secret stores are Enterprise only. The core workflow engine, nodes and AI Agent features are the same. Check n8n's current edition comparison before you commit.

### Is self-hosted n8n secure enough for sensitive data?

It can be, but security becomes your job. Put it behind SSO or a VPN, use Postgres rather than SQLite, keep the encryption key in a secret store, patch promptly and restrict which community nodes are installed. Healthcare data also needs a HIPAA-compliant hosting setup and BAAs with any vendor that touches it.

### Can I move from n8n Cloud to self-hosted later?

Yes. Workflows export as JSON and import into any n8n instance. Credentials need to be re-entered or migrated carefully because they are encrypted with each instance's key. Plan a short parallel run so webhooks and schedules switch over cleanly.

### How much server does self-hosted n8n need?

A small virtual machine handles light workloads. As volume grows, move to Postgres, then to queue mode with Redis and separate worker processes. Size from your peak executions per minute and the heaviest workflows, not the monthly total.

---

Source: https://www.lumeor.studio/compare/n8n-cloud-vs-self-hosted/
Published by Lumeor Studio, Newtown, PA. hello@lumeor.studio. Get a written scope: https://www.lumeor.studio/start/