n8n self-hosted or cloud: which should you choose in 2026?
Published 10 February 2026 · 3 min read
n8n is one of the rare automation platforms you can genuinely run yourself. That freedom creates the first real decision of any n8n project: pay for n8n Cloud, or host it on your own server? Both run the same workflows — including everything sold on this site — but they differ sharply in cost structure, responsibility and data control.
What n8n Cloud actually gives you
n8n Cloud is the hosted offering by n8n GmbH. You get an instance provisioned in minutes, TLS, backups, updates and monitoring handled for you, plus features like managed OAuth for popular services (connecting Gmail or Slack is noticeably easier because the OAuth apps are pre-registered).
Pricing is execution-based. At the time of writing, the entry plan sits around €20–24/month for 2,500 executions, with higher tiers as volume grows. One execution = one workflow run, however many nodes it contains — a pleasant contrast with per-operation pricing elsewhere (see our n8n vs Make vs Zapier comparison).
The trade-offs: your data transits through n8n GmbH's infrastructure (EU-hosted, but still a third party), execution and memory limits apply, and a handful of self-hosted-only options (custom community nodes, some environment flags) are unavailable or restricted.
What self-hosting actually costs
The software is free to run for internal use under n8n's sustainable-use license. The realistic bill:
| Item | Typical cost |
|---|---|
| VPS (2 vCPU / 4 GB, e.g. Hetzner, OVH) | €5–15 /month |
| Domain + TLS (Let's Encrypt) | ~€1 /month |
| Your time: initial setup (Docker, reverse proxy) | 2–4 hours once |
| Your time: maintenance (updates, backups, monitoring) | 30–60 min /month |
The money is trivial; the honest cost is the maintenance. n8n releases frequently, and skipping updates for six months makes upgrades riskier. If nobody on the team is comfortable with Docker, a reverse proxy and a docker compose pull, the €20/month of Cloud buys real peace of mind.
Data control and GDPR
Self-hosting is the strongest argument for European businesses processing personal data. With a self-hosted instance:
- Email content, documents and customer records never leave your server except toward the APIs you explicitly call (OpenAI, Anthropic…).
- You choose the hosting country and provider, which simplifies your GDPR records and vendor list.
- Credentials are stored in your own encrypted database.
n8n Cloud is GDPR-compliant with EU hosting, and is perfectly defensible for most use cases. But if your workflows handle sensitive data — HR files, health data, audit records like our Compliance & Audit Pack — self-hosting removes an entire third party from your data-flow diagram.
Performance and limits
Self-hosted instances have no execution quota: a €10 VPS happily runs tens of thousands of executions a month. What actually limits you is memory — large binary files (PDF ingestion, media) can exhaust a small VPS. For RAG pipelines that chunk hundreds of PDFs, 4 GB of RAM is a comfortable floor.
On Cloud, heavy workloads translate directly into plan upgrades. High-volume, low-value executions (polling triggers, webhooks receiving every email) are exactly where execution-based pricing stings.
The decision in practice
Choose n8n Cloud if: you want to be productive today, no one owns server maintenance, your volumes are modest, and easy OAuth matters more than infrastructure control.
Self-host if: you have basic Docker literacy, you process sensitive or regulated data, your execution volume is high, or you simply want your automation layer to cost €10/month flat.
A common trajectory we see: start on Cloud, validate that the workflows earn their keep, then migrate to a VPS once volume or compliance justifies it. Migration is undramatic — export the workflows as JSON, import them on the new instance, reconnect credentials. It's the exact same import mechanism our packs use, which is why every FlowKit workflow runs identically on both: the JSON doesn't care where n8n lives.