Comparison
n8n Cloud vs Self-Hosted: The Honest Cost Breakdown (2026)
What n8n Cloud really costs vs running it yourself — execution limits, VPS pricing, the hidden cost of your time, and the break-even point.
“Just self-host it, it’s free” and “just pay for Cloud, your time is worth more” are both lazy answers. The real comparison depends on how many executions you run, how spiky they are, and whether an hour of server maintenance costs you €0 or €200 in lost billable time.
We run self-hosted n8n in production and have used Cloud. Here’s the honest math for 2026 — including the costs each camp likes to pretend don’t exist.
How each side charges
The fundamental difference isn’t the monthly number — it’s what the meter measures.
- n8n Cloud charges per plan tier, and each tier caps workflow executions per month (one execution = one full run of a workflow, no matter how many steps it has). The entry plan sits around €24/month for 2,500 executions, the Pro tier around €60/month for 10,000, with higher tiers negotiated from there.
- Self-hosted n8n (Community edition) is free software. You pay for a server, and executions are unlimited — the meter is your hardware. A VPS that comfortably runs n8n with Postgres costs €4–12/month.
That single structural difference decides almost everything:
| n8n Cloud | Self-hosted (VPS) | |
|---|---|---|
| Base cost | ~€24/mo (Starter) | ~€4–12/mo |
| Executions | Capped per tier | Unlimited |
| Cost growth | Steps up with volume | Flat until hardware limit |
| Setup time | ~5 minutes | ~30–45 minutes |
| Maintenance | None | Yours: updates, backups, security |
| Data location | n8n’s cloud | Your server |
| Uptime responsibility | Theirs (SLA on higher tiers) | Yours |
| Some enterprise features (SSO, env-per-stage) | Higher tiers | Paid/enterprise licence |
The self-hosted bill, itemised
For a realistic production setup — the one from our VPS guide:
- VPS: Hetzner CX22 (2 vCPU / 4 GB) ≈ €4–6/month. On DigitalOcean, the comparable droplet runs ~$12–18/month. This runs n8n + Postgres + Caddy with headroom for thousands of executions a day.
- Domain: ~€10/year ≈ €1/month (you likely have one already).
- Off-site backup storage: object storage for nightly dumps ≈ €0–1/month at this scale.
- TLS, database, proxy: €0 — Caddy’s certificates are free, Postgres runs on the same box.
Call it €6–14/month all-in, whether you run 500 executions or 500,000.
Then there’s the line item nobody puts in the table: your time.
- Initial setup: 30–45 minutes once.
- Ongoing: realistically 15–30 minutes a month — pulling updates, glancing at backups, occasionally reading release notes before a version jump. Automate backups properly (guide here) and quiet months round to zero.
- The tail risk: the rare bad day — a disk fills up, an upgrade misbehaves — costing an hour or two. It’s infrequent, but it will be your hour, possibly at an inconvenient time.
Where the break-even actually sits
Low volume (< 2,500 executions/month), no ops appetite: Cloud Starter at ~€24/month is genuinely fine. You’re paying ~€15/month over a VPS to never think about servers. Reasonable trade.
Growing volume (2,500–10,000/month): This is where Cloud’s meter starts to sting — you’re pushed to the ~€60/month tier for volume a €5 VPS handles without noticing. Self-hosting saves €600+/year here.
High volume (10,000+/month, polling workflows, AI agents): No contest. Per-execution pricing punishes exactly the workflows n8n is best at — schedules that poll every 5 minutes (that’s ~8,600 executions/month per workflow), chatty webhooks, multi-step AI agents. Self-hosted, these are free. On Cloud, a single 5-minute polling workflow nearly exhausts the entire Pro tier.
One workflow that polls every minute = ~43,000 executions/month. Read that again if you’re on metered pricing.
What Cloud gives you that money can’t easily replicate
Fairness requires the other column. Cloud isn’t just “n8n without Docker”:
- Zero-touch upgrades with rollbacks handled for you.
- Someone else wakes up at 3 a.m. when the instance is down.
- Official support and one-click version management.
- No security surface to own — you never patch an OS or configure a firewall.
And one myth to kill: your credentials are not “less safe” self-hosted — but their safety becomes your job. If you won’t do the hardening basics, Cloud is the more secure option for you.
The middle path: managed self-hosting
There’s a third column people forget: run your own n8n instance on a platform that owns the infrastructure. You keep unlimited executions and control over the instance, but skip the OS, firewall, and reverse-proxy work. On Railway, n8n deploys from a template in a few minutes and typically lands around $5–15/month depending on usage.
That’s the setup we suggest to people who are convinced by self-hosting economics but honestly won’t maintain a server — full walkthrough in Deploy n8n on Railway.
Our verdict
- Under ~2,000 executions/month and zero interest in servers → n8n Cloud. Pay the convenience tax with a clear conscience.
- Anything with polling, webhooks at volume, or AI agents → self-host. The economics aren’t close: €6–14/month flat vs a meter that climbs past €60.
- Want the economics but not the sysadmin hat → Railway (or a similar managed platform) as the middle ground.
- Regulated data, or credentials that must not leave your infrastructure → self-host on your own VPS, full stop. That’s not a cost decision anymore.
We self-host — our automation volume made it a ~€700/year difference, and the maintenance is a solved, scripted routine. If you go the same way, start with the production VPS setup, then immediately set up backups. That order matters.