n8n Self-Hosted, Cloud, or Managed: Which Setup Fits Your Business?

Self-host it, use the cloud, or let someone run it for you? The answer comes down to three things: how much technical capacity you have in-house, how much it matters where your data lives, and how many automations you run. If you want to start fast and have no one to look after a server, n8n Cloud is the path of least resistance. If you have a technical team and want full control, you self-host. And if you want that control without running the operation yourself, you have n8n managed for you.

The Short Version: Which Setup for Whom?

Technically it's the same n8n in all three cases. Same nodes, same workflows, same interface. The only difference is who runs the server and where your data lives. That's exactly what decides which setup fits you.

I'm Not a Neutral Observer

Before I sort this out, the disclosure: at Pipewave I build and run n8n automations for companies, and managed hosting is part of that. So I make money when someone picks the third option.

Even so, I don't recommend it to everyone. If you have a developer on the team who knows Docker and can look after a server, self-hosting is simply the cheapest solution, and I'll say so. Managed is worth it for those who want full data control but have no one who wakes up at night when the server goes down. Which setup is right for which case is what I'm trying to separate honestly here.

n8n Cloud: The Path Without a Server

n8n Cloud is the hosted version, run directly by the vendor. You sign up, and n8n handles servers, updates, and availability. You just build your workflows. For getting started, this is the path of least resistance, especially when no one on the team wants to or can administer a server.

You pay per execution, not per user. An execution is one complete run of a workflow, no matter how many steps it has. That sounds harmless but adds up. A workflow that checks every five minutes whether a new email has arrived burns through roughly 8,600 executions a month, that one alone. The entry tier is used up faster than most expect.

One point to keep in mind with customers in the EU: your data runs through n8n's infrastructure. There is an EU region, but n8n remains a processor handling your automation data. For many cases that's fine. The moment sensitive customer data flows through the workflows, it becomes a topic for your data processing agreement.

Self-Hosted: Full Control, Full Operation

n8n is open source and free to run on your own server. You install it via Docker or npm on a VPS, and from then on the instance is yours. No execution limits, no per-run billing, your data stays on your server. For companies that take data protection seriously or run many automations, that's the most attractive part.

The price for it is work. You're now responsible for the operation: applying updates, setting up backups, securing the instance, maintaining an SSL certificate, switching to queue mode under heavier load. None of it is rocket science, but it's recurring work, and when the server goes down, every automation goes with it. That's why self-hosting is only cheap when someone on the team can and will take on that work.

The raw server cost is low. A small VPS for a few euros a month carries a surprising number of workflows. It doesn't get expensive at the server, but at the time the operation eats up.

Managed: Control Without the Operation

The third setup sits in between. Someone runs a self-hosted n8n instance for you, on a dedicated server or your own. You get the advantages of self-hosting – no execution limits, data under your control – without doing the maintenance yourself. Updates, monitoring, backups, and security are handled by the provider.

This fits companies that don't want the cloud for data protection reasons but also have no one to look after servers. Instead of assigning a person to it or letting it run on the side and hoping nothing breaks, you pay a predictable flat rate and have someone to call when something stalls.

To stay honest: this is the most expensive of the three, because the operation and responsibility are paid for too. It pays off when data control matters to you and your time is better spent on your business than on server updates.

The comparison has a catch the numbers alone don't show. The €5 server looks cheapest but also costs your time. The cloud looks predictable but climbs with volume. So don't just add up the invoice, add up the hours the operation costs you. With many small automations, the comparison quickly tips away from the cloud.

Which Setup for Whom

Boiled down to three sentences: n8n Cloud when you want to start fast, have no one for the server, and your volume stays modest. Self-hosted when there's a technical team in-house, control and data protection matter to you, and you can carry the operation yourself. Managed when you want exactly that control but would rather hand off the operation.

Most people underestimate how quickly a toy becomes a system that real processes depend on. As long as n8n just sends a notification, the setup doesn't matter. The moment your quotes, invoices, or lead handoffs run through the workflows, how stable and how compliant the operation is starts to count.

And If You're Unsure?

The three setups are technically identical, it's the same n8n everywhere. The decision isn't about features, it's about operation and responsibility. I run n8n for companies but will tell you honestly when self-hosting is the smarter and cheaper choice for your case. That's exactly the kind of read I give in n8n consulting.

If you're still weighing whether n8n is even the right tool, the comparison with the alternatives in my article on n8n, Zapier, and Make will help.

→ Let's spend 15 minutes figuring out which setup fits you

Written by Joshua Kresse. I build and run n8n automations for B2B companies, in the cloud, self-hosted, or managed, whichever actually fits.