n8n self-hosted vs cloud: full comparison and 2026 pricing

It is the first structural decision of any n8n project: pay for the managed Cloud offering from n8n GmbH, or run the community version yourself on a server? Both options execute exactly the same workflows and the same nodes. What changes is the cost model, the responsibility for your data and the time you are willing to spend on infrastructure. Here is the full comparison, with 2026 prices verified on the official pricing page and the thresholds where each option wins.

The two options in two sentences

n8n Cloud is the official SaaS: an instance online in minutes, HTTPS, backups, updates and monitoring handled for you, pre-registered OAuth for popular services, in exchange for a monthly subscription capped in executions.

n8n self-hosted means running n8n yourself — typically with Docker on a VPS, a NAS or an internal server. The software is free under the Sustainable Use license (internal use allowed, reselling the service forbidden), with no execution limit, but everything rests on you: installation, TLS, updates, backups, security.

n8n Cloud pricing in 2026

At the time of writing (August 2026), the official n8n pricing page lists, on annual billing:

• Starter — €20/month: about 2,500 monthly executions, 5 concurrent executions, unlimited users, 1 shared project.
• Pro — €50/month: about 10,000 executions, 20 concurrent executions, 3 shared projects, admin roles, workflow history, global variables.
• Business — €667/month: about 40,000 executions, SSO/SAML/LDAP, separate environments, Git-based version control, self-hosted option included.
• Enterprise — custom quote: custom volumes, 200+ concurrent executions, log streaming, dedicated support with SLA.

Monthly billing costs roughly 17% more than annual (Starter lands around €24/month). These numbers change regularly: our detailed n8n Cloud pricing guide tracks the plans closely, and the official page remains the reference.

The key point of the model: n8n counts workflow executions, not operations. A workflow chaining 40 nodes counts as one execution — far more generous than Zapier's or Make's per-task billing, as we quantify in our n8n vs Make vs Zapier comparison. The flip side: high-frequency triggers (polling every minute, a webhook receiving every incoming email) burn through the quota fast, and workflows can be paused once the limit is reached.

What self-hosting really costs

The software is free; the hosting almost is:

• VPS: in the €5-15/month range at a European provider (Hetzner, Scaleway, OVHcloud) for 2 vCPU / 4 GB RAM — plenty to start. Our guide to choosing a VPS for n8n covers sizing in detail.
• Domain + TLS: a few euros per year, Let's Encrypt being free.
• Your time: the hidden line item. Initial setup (1 to 3 hours with Docker Compose), then 30 to 60 minutes per month for updates, backup checks and monitoring.

If you bill your time at €60/h, one hour of monthly maintenance already "costs" more than the gap with the Starter plan. The full calculation — power, scaling, the cost of an incident — is laid out in our analysis of the real cost of self-hosted n8n.

On the licensing side, the community version has no limit on executions or workflows; some features (SSO, environments, advanced history) remain paid-plan territory, as we detail in what the free n8n license really allows.

Where is the economic tipping point?

This is the question behind most "n8n self host cost" searches. Three zones emerge:

1. Under 2,500 executions/month: Starter at €20/month is unbeatable once your time is priced in. Self-hosting only wins here for data reasons, not cost.
2. 2,500 to 10,000 executions/month: grey zone. Pro at €50/month stays reasonable; a €10/month VPS is cheaper on paper, but the ~€40/month gap disappears into a single hour of maintenance.
3. Above 10,000 executions/month: self-hosting takes the lead, and it becomes overwhelming at high volume. Between Pro (10,000 executions) and Business (€667/month for 40,000), the price jump is brutal; the same volume runs on a €15-30/month VPS, and queue mode with Redis lets you scale horizontally when a single container is no longer enough.

This inverted economy of scale has been documented for years: the reference study by Armbrust et al., "A View of Cloud Computing" (Communications of the ACM, 2010, Google Scholar), shows that cloud is economically optimal for variable or unpredictable workloads, while steady, sustained workloads eventually cost less on dedicated infrastructure — exactly the n8n Cloud vs VPS trade-off.

Side-by-side comparison, 2026

Criterion	n8n Cloud	n8n self-hosted
Starting cost	€20/month (Starter, annual)	~€5-15/month VPS + your time
Execution limit	2,500 (Starter) to 40,000 (Business)	None (bounded by your server)
Concurrent executions	5 to 200+ depending on plan	Depends on hardware (queue mode available)
Data location	n8n GmbH infrastructure (EU)	Your server, wherever you choose
GDPR	Compliant, but a processor (DPA required)	Data never leaves your infrastructure
Updates	Automatic	Manual, your responsibility
Backups	Included	Yours to set up (database + N8N_ENCRYPTION_KEY)
SSO / environments / Git	Business plan and above	Enterprise features behind a paid license
Community nodes	Yes (with verification)	Yes, unrestricted
Skills required	None	Docker, Linux, basic networking
Time to first workflow	5 minutes	1 to 3 hours

GDPR, security and governance

Often the deciding argument for European businesses. With n8n Cloud, your data transits through n8n GmbH's infrastructure, a German company with EU hosting — a solid setup, but n8n remains a processor: DPA to sign, records of processing to maintain, payloads (customer emails, CRM data) flowing outside your infrastructure.

With self-hosting, data never leaves your server, apart from the API calls your workflows explicitly make. For an accounting firm, a healthcare player or any regulated activity, that significantly simplifies your impact assessment. You also keep full control over user management and permissions without depending on a pricing tier.

The counterpart: security is on you. Mandatory HTTPS, a reverse proxy, a firewall, and above all backups of the database and the encryption key — without N8N_ENCRYPTION_KEY, your backed-up credentials are unrecoverable:

# The two things you must back up when self-hosting
docker exec n8n-postgres pg_dump -U n8n n8n > backup.sql
grep N8N_ENCRYPTION_KEY .env >> backup-secrets.txt  # store encrypted, elsewhere

Which profile are you?

• Freelancer / solo: Cloud Starter. You sell your time; €20/month for zero maintenance is a good trade as long as volume stays under 2,500 executions.
• Small business with no technical profile: Cloud Starter or Pro. Managed OAuth and included backups avoid depending on an external contractor.
• SMB with Docker culture in-house: self-hosted on a European VPS. Near-fixed cost, unlimited volume, data at home.
• Data / AI team: self-hosted, almost always. High-frequency AI workflows (enrichment, RAG, scoring) blow through Cloud quotas, and queue mode absorbs the load.
• Regulated enterprise (health, finance, legal): self-hosted for full control of data flows, or Business/Enterprise if IT requires SSO and SLA-backed support.

A study by Marston et al., "Cloud computing — The business perspective" (Decision Support Systems, 2011, Google Scholar), highlights that SaaS dramatically lowers the cost of entry for smaller firms — true for n8n Cloud — but identifies data location and vendor dependency as the main enterprise-side blockers: precisely the two reasons that push teams toward self-hosting.

The decision tree in four questions

1. Is your data sensitive or regulated? Yes → self-host (or Enterprise with contractual guarantees). No → question 2.
2. Will you exceed 10,000 executions/month? Yes → self-host. No → question 3.
3. Is anyone on the team comfortable with Docker and a reverse proxy? No → Cloud, no hesitation. Yes → question 4.
4. Do you value your hour above €40-50? Yes → Cloud often remains the rational choice. No, or you want control → self-host.

And remember that nothing is final: workflows export as JSON and re-import unchanged. Migrating from n8n Cloud to self-hosted (or the other way) takes about an hour; only credentials need recreating.

Key takeaways

Cloud sells peace of mind; self-hosting sells control and a near-zero marginal cost at high volume. In 2026, with a Starter plan verified at €20/month on the official page, Cloud is the right starting point for most independents. Once volume passes ~10,000 monthly executions or data location becomes non-negotiable, self-hosting on a European VPS takes back the lead — provided you own the maintenance. Either way, your workflows run identically on both sides: the decision is reversible.