Self-Hosted n8n vs Cloud
Control vs convenience is the wrong frame. The real trade is money vs hours.
The comparison that matters
| Self-hosted | n8n Cloud | |
|---|---|---|
| Server cost | ~€10–50/mo | Included |
| Your hours/month | Real and recurring | ~0 |
| Data location | Wherever you put it | n8n's EU infrastructure |
| Custom nodes | Yes | Limited |
| Community nodes | All | Verified subset |
| Execution limits | Your hardware | Plan-based |
| Version control of upgrades | You decide when | Managed for you |
| Who's paged when it breaks | You | n8n (infra); you (workflows) |
The case for n8n Cloud
Zero maintenance, EU hosting, fast start, fair per-execution pricing at low volume. If your workflows are straightforward and nobody in-house wants to own a server, Cloud is the honest recommendation — we make it to clients regularly.
Its limits show up later: custom nodes for your industry ERP, heavy execution volumes, strict data-residency or SIEM requirements, and the fact that workflow failures are still yours to notice and fix.
The case for self-hosting
Full control: any node, any volume, your network, your compliance story. The catch is the second row of the table — updates, backups, TLS, Postgres care, queue-mode setup as you grow (scaling guide), and security hardening. We put real numbers on those hours in Self-Hosting AI Infrastructure Looks Free; for most SMEs the honest total exceeds the Cloud subscription many times over.
Self-hosting is right when the control is required (residency, custom nodes, volume) and a named person owns the maintenance.
The third option most comparisons skip
Operated self-hosting: n8n runs on your infrastructure — your data, your network, your compliance boundary — but a partner owns the operations and the workflow layer: monitoring, upgrades, error recovery, new builds. Control of self-hosting, hours of Cloud.
That's Oido's managed n8n on your servers (or ours, if residency doesn't bind you), including the AI agent layer n8n alone doesn't give you.
Deciding
- Data must stay on your infra, or you need custom nodes → self-host. With an owner → DIY; without → operated.
- Simple workflows, technical builder in-house, no residency constraints → n8n Cloud.
- Automation is business-critical and nobody wants to own ops → operated, either location.
All n8n hosting paths in detail: n8n hosting options.