AUTOMATION PLATFORM DECISION
Self-hosted n8n vs n8n Cloud
The product is recognisably the same, but the operational responsibility is different. With n8n Cloud the provider runs the platform; with self-hosting you own the server work.
| Question | Self-hosted | n8n Cloud |
|---|---|---|
| Who maintains the server? | You | n8n |
| Who plans backups? | You | Provider manages platform operations; export/recovery needs still depend on your requirements |
| Where are credentials stored? | On infrastructure you control | Within the managed service |
| Can you place it on your private network? | Yes, subject to your network design | Managed cloud service |
| Maintenance effort | Higher | Lower |
Choose self-hosting for infrastructure control
Self-hosting can make sense when workflows need to reach services on your own network, when you want to control the database and update schedule, or when running the infrastructure is already familiar territory.
Choose Cloud to reduce operational work
If your goal is building workflows rather than maintaining a server, a managed service removes a substantial amount of routine administration. That convenience is part of what you are paying for.
Licensing still matters
Running the community edition yourself does not mean every commercial use is automatically permitted. n8n distinguishes internal use from scenarios such as hosting and managing clients' workflows or embedding n8n in a product. Check the current licence for your exact use case.
Do not self-host merely to avoid a subscription
Count the server, backups, monitoring and your time. The cheaper-looking option can be more expensive if you dislike maintaining it.
Start with what n8n actually does or plan the hardware.