n8n Cloud vs Self-Hosted: The Real Cost Breakdown

The n8n Cloud vs self-hosted question has a boring, correct answer that most articles dodge: it depends on whether your time is cheaper than a server. On the invoice, self-hosting wins nearly every time. Once you price in the hours you'll spend on backups, upgrades, and the occasional 2 a.m. restart, the math can flip. This post runs the actual numbers so you can decide with a spreadsheet, not a vibe.

n8n Cloud is the hosted version n8n runs for you: no server, no upgrades, capped by an execution allowance. Self-hosted n8n is the same open-source software running on infrastructure you own, with no execution meter and full data control. Both run identical workflows. They cost your money and your time in opposite proportions.

Plenty of pricing posts list the plan tiers and stop. A Sliplane breakdown and an InstaPods cost guide both cover cloud vs self-hosting, but the piece buyers actually need, a breakeven by team size that weighs maintenance time honestly, is usually missing. So is a clean list of exactly what self-hosting makes you responsible for. Here's both.

Quick comparison

The real numbers

Start with the published figures. Per the official n8n pricing page, n8n Cloud Starter is 20€/mo billed annually and includes 2,500 workflow executions with 5 concurrent executions. Pro is 50€/mo for 10,000 executions and 20 concurrent. That execution cap matters more than the headline price.

Self-hosting flips the model. A small VPS runs roughly $3–7 a month, per multiple 2026 cost guides, and it has no execution meter at all. You could run 2,500 executions or 250,000 on the same box, bounded only by the server's RAM and CPU.

Here's the trap the Cloud tiers hide. A single workflow polling Gmail every few minutes can burn through the Starter plan's 2,500-execution allowance in under two weeks, per the cost analysis in community pricing breakdowns. Execution-heavy automation is exactly what n8n is good at, and it's exactly what the metered plans penalize.

What self-hosting actually makes you own

This is the list most comparisons skip. When you self-host, the following stop being someone else's problem:

• Backups. The n8n SQLite or Postgres database holds your workflows, credentials, and execution history. Nobody backs it up but you.
• SSL certificates. A public n8n instance needs HTTPS. That means a reverse proxy and certificate renewal that doesn't lapse.
• Version upgrades. New n8n releases ship often. Upgrades occasionally change node behavior, so you test before you roll forward.
• Uptime. If the box goes down at 3 a.m., your workflows are down until you notice. Cloud handles this; your VPS doesn't.
• Security patching. OS updates, dependency patches, and locking down the instance are on you.

None of this is difficult for someone comfortable with a Linux box. All of it is time. The n8n self-hosting guide walks the setup end to end, and the n8n production setup checklist covers the hardening most first-timers miss.

The breakeven by team size

Rough guidance, based on the published prices above and typical maintenance load:

Solo technical builder

Self-host. A $5 VPS with unlimited executions is the obvious win, and if you're already comfortable with Docker, maintenance is minutes a month. This is the clearest case there is.

Solo non-technical user

n8n Cloud. Your time isn't free, and an hour spent debugging a failed upgrade is an hour not spent on your actual business. The Starter plan's simplicity is worth the 20€.

Small team, moderate usage

It's a genuine toss-up. If someone on the team enjoys running infrastructure, self-host and pocket the difference. If nobody does, Cloud's zero-maintenance story usually wins even at the higher price, because the maintenance would otherwise land on your most expensive person.

Growing team, heavy usage

Self-host, almost always. Once execution volume climbs past the Pro plan's 10,000 monthly runs, the metered model gets expensive fast, and the flat cost of a beefier server wins decisively. High volume is where self-hosting's no-meter advantage compounds.

What you can run either way

The workflows are identical on both. The kinds of jobs teams run on n8n:

• Score and route inbound leads before a human sees them
• Validate incoming data before it corrupts downstream systems
• Monitor other workflows and alert when one fails
• Sync records between a CRM, a database, and a spreadsheet
• Run nightly ETL and drop the output into a report
• Trigger drip campaigns from user behavior

None of these care whether you're on Cloud or self-hosted. What changes is the bill and who owns the uptime.

Getting started, either path

1. Estimate your monthly execution volume honestly, since that's the number that decides everything.
2. If it's under ~2,500 and you don't want to run a server, start on n8n Cloud Starter.
3. If it's higher, or you need data residency, deploy self-hosted with Docker (the self-hosting guide covers it).
4. Either way, set up error handling early so failures reach you instead of dying quietly.
5. Add a workflow-failure monitor so a broken automation pages you the moment it breaks.
6. Start from a pre-built template so your first workflow is doing real work, not teaching you the canvas.

The verdict: self-host if you're technical or your volume is high, since the invoice math is lopsided in your favor. Choose Cloud if your time is scarce and your usage is light, because maintenance is a real cost even when it's not on the bill. For the deeper setup, read the n8n self-hosting guide and the n8n production setup checklist, then grab the workflow failure monitor so nothing breaks silently on the box you now own.