n8n is one of the rare tools where the vendor genuinely supports both paths: you can pay for n8n Cloud and let the vendor run it, or self-host the same product on your own infrastructure. Both are legitimate choices. This page compares them honestly, because the right answer depends on your usage volume, your data requirements and how much your automations touch internal systems. Node offers managed n8n hosting in the UK, so we clearly have a preference, but we would rather you pick the option that actually fits.
n8n Cloud vs self-hosted n8n at a glance
| n8n Cloud | Self-hosted n8n, managed by Node | |
|---|---|---|
| Pricing model | Per-plan subscription with execution limits; published pricing starts at around 20 euros a month at the time of writing | Flat monthly fee based on instance resources, regardless of usage |
| Workflow and execution limits | Capped per plan; more executions and active workflows mean a higher tier | No plan limits; capacity is bounded only by the resources you size, and resizing is a support request |
| Data residency | Hosted in Germany at the time of writing, on the vendor's infrastructure | UK by default, or your own cloud account or datacentre, with an Article 28 DPA |
| Single sign-on | n8n's built-in SAML SSO sits in its enterprise tier | The same enterprise licensing applies to n8n's built-in SSO, but Node can integrate platform-level sign-on with your identity provider, such as Keycloak or Authentik, in front of the instance |
| Version control | Git-based source control is an enterprise-tier feature | Workflows export as JSON, so you can keep them in your own git repositories and build your own review and promotion process |
| Custom and community nodes | Verified community nodes are supported; arbitrary custom code is restricted at the time of writing | Any community node, any custom node your team writes, and direct network access to internal systems |
When n8n Cloud is the right choice
We will be straight about this: n8n Cloud is a good product, and for some teams it is the better option.
Very small teams and light usage: if you run a handful of workflows and a few thousand executions a month, the entry-level Cloud plan is likely to cost less than any managed hosting arrangement. Paying around 20 euros a month for something that just works is a perfectly rational decision.
No operations requirements: n8n Cloud is zero-ops. Upgrades, uptime and scaling are the vendor's problem. If you have no data residency constraints and your workflows only touch public SaaS APIs, the simplicity is worth a great deal.
Trying n8n out: Cloud is the fastest way to evaluate whether n8n fits your team at all. Workflows export as JSON, so nothing you build there is wasted if you later move.
When self-hosted n8n wins
Volume: execution limits are where Cloud pricing bites. Automation tends to grow: one useful workflow becomes fifty, and a workflow that polls every five minutes burns thousands of executions a month on its own. A self-hosted instance has no per-execution meter, so heavy automation costs the same as light automation.
Data residency and compliance: every workflow execution passes your data through the platform. If that data includes customer records, financials or anything covered by UK GDPR obligations, running n8n on UK infrastructure you control, with a direct data processing agreement, is materially simpler to defend than routing it through a third-party processor in Germany.
Integration with internal systems: this is often the deciding factor. A self-hosted instance can sit inside your network and talk directly to internal databases, private APIs and on-premises applications, and can run any custom node your team writes. Reaching internal systems from a vendor-hosted cloud instance means tunnels, allow-lists or exposing services, and restrictions on custom code.
Predictable cost at scale: a flat fee that does not move when your execution count triples is easier to budget than a usage-based subscription.
What it costs in practice
Third-party prices change, so treat these as illustrations and check n8n's current pricing; ours is on the pricing page.
Light usage, a few workflows and a few thousand executions a month: n8n Cloud's starter plan, at around 20 euros a month at the time of writing, is hard to beat. Managed hosting only makes sense here if data residency or internal integration forces it.
Medium usage, dozens of active workflows and tens of thousands of executions: you are into Cloud's higher tiers, published at around 50 euros a month and upwards at the time of writing, and approaching their limits. A managed instance on a Medium resource profile is comparable in cost, with no execution caps and UK residency included.
Heavy usage, hundreds of workflows, polling triggers and six-figure monthly executions: Cloud pricing at this level is typically a custom enterprise conversation. A managed self-hosted instance remains a flat monthly fee, sized to the resources the workload actually needs, and usually costs a fraction of the equivalent usage-based bill.
The honest summary
If you are small, unregulated and light on volume, use n8n Cloud and enjoy it. If you are automating at volume, handling data that must stay in the UK, or wiring workflows into internal systems, self-hosted n8n wins, and with Node it arrives without the operational burden: we run it on our UK platform, with high availability, backups, monitoring and support included. Read more about managed n8n hosting or talk to us about which side of this comparison you are actually on.
Frequently asked questions
Is self-hosting n8n legal and properly supported?
Yes. n8n is published under the Sustainable Use License, which explicitly permits self-hosting for internal business use, and the community edition is a first-class product that the vendor develops and documents. With Node, self-hosted does not mean unsupported: we deploy, monitor, patch and support the platform as a managed service with UK-based engineers.
Who handles n8n upgrades and security patches on a managed self-hosted instance?
Node does. n8n releases frequently, and we test and apply upgrades as part of the managed service, along with operating system patching, backups and monitoring. Your team builds workflows; we keep the platform current and secure.
Where does my data live with n8n Cloud versus self-hosted n8n?
n8n Cloud is hosted in Germany at the time of writing, so your workflow data and credentials sit on the vendor's EU infrastructure under their terms. A self-hosted instance managed by Node runs in the UK by default, or in your own cloud account or datacentre, with an Article 28 data processing agreement and no third-party processor in the middle of your workflows.
How does migrating from n8n Cloud to self-hosted n8n work?
Workflows export as JSON, so migration is straightforward: we stand up your managed instance, import your workflows, recreate credentials securely, and run both environments in parallel while you verify each workflow. Most teams cut over gradually with no interruption to running automations.
What does managed self-hosted n8n cost compared with n8n Cloud?
n8n Cloud's published pricing starts at around 20 euros a month at the time of writing, with execution and workflow limits per plan, and costs rise as usage grows. Managed n8n from Node is a flat monthly fee based on the resources your instance needs, not on how many workflows you run. At light usage n8n Cloud is often cheaper; at medium to heavy usage the flat fee usually wins. See our pricing page for current figures.
Can I use custom and community nodes on each option?
Self-hosted n8n can run any community node and any custom node your team writes, which matters when you integrate internal systems. n8n Cloud supports a set of verified community nodes but is more restrictive about arbitrary custom code, at the time of writing.