GUIDE
Self-hosted vs cloud n8n
Self-hosting keeps data on your infrastructure and removes the platform fee. The cloud removes the operations work. The right choice depends on your volume, your data, and who runs the servers.
Last updated October 2026.
| Dimension | Self-hosted | Cloud |
|---|---|---|
| Data location | Your infrastructure. | n8n cloud. |
| Platform fee | None. You pay for the server. | Per plan and execution volume. |
| Operations | You handle updates, backups, monitoring, and restarts. | Handled for you. |
| Control | Full: versioning, queue mode, custom nodes, scaling. | Good, within the platform. |
| Best for | Privacy needs, high volume, or a team that already runs servers. | Small teams that want to skip ops. |
Choose self-hosted when
Data cannot leave your environment, volume makes per-execution pricing expensive, or you want the workflow logic versioned and deployed like code. It also unlocks queue mode for high-volume work. The tradeoff is that backups, updates, and monitoring become your responsibility.
Choose cloud when
You want to skip the operations work and the volume is modest. It is the faster start, and for a small team with a handful of workflows it is usually the right one. You can move to self-hosted later if volume or data rules change.
If you self-host, do these
- Automated backups and a tested restore.
- Access control and secret handling that does not leak credentials.
- Monitoring so failures surface before a person notices.
- A repeatable update process.
Related: n8n automation service and migrating from Zapier.
Not sure which n8n you need?
Tell me your data constraints and volume. I will tell you which one fits, and what it takes to run it.
Get a free automation audit