How to Decide Between n8n Cloud and Self-Hosted n8n
Self-hosted n8n has no execution limit and runs on a $6/month VPS, while n8n Cloud starts at $24/month and caps you at 2,500 executions. The right pick depends on three things: monthly run volume, where your data is allowed to live, and whether you want to deal with servers at all.
How many executions do you actually run each month?
Count them before you choose. A daily workflow that triggers once is 30 runs a month. A webhook that fires on every new form submission across three forms can hit 4,000 before you notice.
On Cloud, the pricing ladder is $24 for 2,500, $60 for 10,000, and $800 for 40,000. On the community edition, executions are free — the ceiling is your server’s RAM. A 2GB droplet handles a surprising amount of light automation, and 4GB is plenty for most solo setups.
| Factor | Self-hosted | n8n Cloud |
|---|---|---|
| Monthly cost | ~$6 VPS | $24+ |
| Execution cap | None | 2,500 / 10,000 / 40,000 |
| Maintenance | You patch and back up | Handled |
| Data location | Anywhere you choose | EU or US region |
Does data residency rule out the cloud?
Sometimes it does. Cloud regions are limited to the EU and US, so if a client contract demands that records stay inside a specific country, or your legal team is nervous about a third party holding credentials, self-hosting on your own infrastructure is the only option that satisfies them.
For a solo operator with no such constraints, that concern disappears. The hosted build stores credentials encrypted with your instance key either way.
What does maintenance really cost you?
Running n8n yourself is not hard, but it is not zero work. Docker Compose plus a reverse proxy for TLS is a weekend job the first time. After that you own upgrades, database backups and log rotation.
Be honest about your tolerance here. If a personal project goes down for a day, nobody cares. If a client invoicing workflow fails silently on a Friday, that is a different conversation.
Can you migrate later?
Yes, and this is the strongest argument for starting on Cloud. Export any workflow as JSON from the canvas menu, then import it into a self-hosted instance. Nodes, connections and credentials references come across, though credentials themselves must be re-authenticated on the new instance.
That means the decision is reversible. Start hosted so you can learn the tool this week, then move to a VPS when your execution count or your paranoia justifies it.
Key Takeaways
- Cloud costs $24/month for 2,500 executions; a $6 VPS runs the community edition with no cap.
- Choose Cloud for zero maintenance and fast setup; choose self-hosted for volume or strict data residency.
- Workflows export as JSON, so Cloud to self-hosted migration is straightforward apart from re-authing credentials.
- Only EU and US regions exist on Cloud, which is the main disqualifier for regulated projects.
Last updated: September 2026.
