n8n Self-Hosting vs Cloud: Cost, Effort and Control Compared

You have settled on n8n and now face the next question: self-host or cloud? With n8n self-hosting you pay almost nothing and carry the responsibility. In the cloud it is the other way round.

I have run n8n self-hosted for years. Our own brands nano, mate and MUSTAX run entirely on it. For clients we set up both variants. Here is the comparison I wish I had had back then.

If you are still on the tool question: read n8n vs Make vs Zapier first. This article assumes n8n is settled.

The short version

Both routes work. The question is what you want to pay with: money or responsibility.

n8n self-hosting: full control, full effort

Self-hosting means n8n runs as a Docker container on your own server. For us that is a VPS at Hetzner for about 15€ a month. All workflows for three brands run on it.

The upsides

• Fixed cost. The server costs the same whether 100 or 100,000 executions run. At serious usage that is the biggest lever.
• Your data stays with you. Customer addresses, orders, emails: everything runs through your server, not through third parties.
• No limits. Unlimited workflows, unlimited executions, all features of the community edition.
• Your own packages and scripts. You can install npm packages and build custom nodes. In the cloud that is only possible to a limited degree.

The downsides

• You are the admin. Updates, backups, disk space, SSL certificates: all your job. That costs us a real 1 to 2 hours a month.
• Outages are your problem. If the server dies at night, nobody wakes you. You need monitoring, otherwise you notice it through missing revenue.
• Security is on you. An open n8n server without authentication is a way in. Firewall, HTTPS and strong passwords are mandatory, not optional.
• The learning curve is real. Anyone who has never driven a server over SSH needs patience or help. Basic Docker knowledge is effectively a prerequisite.

An example from our daily work: at nano the entire order processing hangs on n8n. Once we installed an update without reading the changelog first, and a workflow broke. The fault was fixed in 30 minutes. But those 30 minutes are part of the bill.

n8n Cloud: pay and go

The cloud variant is n8n as a finished service. Create an account, build a workflow, done.

The upsides

• No server, no maintenance. Updates, backups and availability are n8n's problem, not yours.
• Fast start. Your first workflow runs in 5 minutes. How that works is in Your first n8n workflow.
• Support included. If something goes wrong there is someone to talk to. With self-hosting you rely on the community and the forum.

The downsides

• Cost grows with you. The entry plans cap executions and active workflows. Scale up and you slide into higher plans quickly. At intensive usage we are talking about a multiple of the server cost.
• Less freedom. Custom npm packages and deep system access are restricted.
• Your data runs across someone else's servers. For many use cases that is fine. For some it is not. More on that in a moment.

GDPR: the point that often decides

Many people look for a Zapier alternative with a GDPR focus and land on exactly this question. Rightly so. Personal data flows through your automation tool: names, addresses, order histories, emails.

The situation in short:

• Zapier is a US provider. Data transfers rest on the EU-US Data Privacy Framework and standard contractual clauses. That is legally possible, and you remain dependent on the stability of those agreements. The predecessor agreement, Privacy Shield, was struck down by the European Court of Justice in 2020.
• n8n Cloud comes from n8n GmbH, based in Berlin. A data processing agreement is available. For most shops that is a clean basis.
• n8n self-hosting is the strictest variant: the data never leaves your server in the first place. You need no data processing agreement with the tool provider, because there is no provider in the chain. Only your hosting company remains, and with a German host like Hetzner that is straightforward too.

Important: self-hosting does not automatically make you GDPR compliant. You stay responsible for access control, deletion periods and secure processing. It only shortens the chain of parties involved. This is not legal advice, and when in doubt the topic belongs with your data protection officer.

When which route fits

Take the cloud if:

• you have fewer than about 5 workflows and simply want to start
• nobody on the team can or wants to administer a server
• your workflows do not move highly sensitive data
• uptime without your involvement matters more than the price

Self-host if:

• your workflows are business-critical and run a lot
• you process customer data at scale
• you have basic technical knowledge, or someone who does
• you want to keep cost predictable and low

There is a middle route as well: start in the cloud, move later. n8n workflows can be exported and imported as JSON. The move is work, and it is not a fresh start. You have to re-enter credentials, and webhook URLs change.

What we run at Flowhouse ourselves

Self-hosting, without exception for our own brands. The entire engine room of nano, mate and MUSTAX runs on a self-hosted n8n: order processing, fulfilment, returns, customer service triage, reporting.

The reason is the combination of three points. At 300+ orders a day across all brands, cloud executions would be expensive. Our customers' data should not leave our server. And we need custom code in places where standard nodes are not enough.

With Flowhouse clients we decide case by case. A team without a technical owner does not get a server from us that nobody maintains afterwards. That would be an outage with an announcement. Then rather cloud, or a setup where we take on the maintenance.

The minimal setup for self-hosting

If you decide to self-host, here is the short version of our setup, so you know what is coming:

• A VPS at a European host, 2 CPU cores and 4 GB RAM go a long way.
• Docker Compose with n8n and a Postgres database. The default SQLite database is fine to start with, for continuous operation take Postgres.
• HTTPS through a reverse proxy, for example Caddy or Traefik. Without an encrypted connection your credentials travel across the network in plain text.
• Daily backups of the database, automated, to a second location. Your workflows are business logic. Lose them and you spend weeks rebuilding.
• An uptime monitor that pings you when the server stops responding. Free services are enough for this.

That is an afternoon of work if you know Docker. A weekend if you do not. After that it runs remarkably undramatically: our server has done its job for years, the monthly upkeep is manageable.

The limits of both routes

However you host, three things neither variant solves:

• Bad processes stay bad. A chaotic workflow just becomes faster chaos through n8n.
• APIs change. If Shopify or your fulfilment partner adjusts the interface, you have to react. In both variants.
• Monitoring is mandatory. A workflow that dies quietly is worse than none. Build alerts in from the start.

Conclusion

n8n self-hosting wins on cost, control and data protection. The cloud wins on simplicity and peace of mind. Both are fair deals, just in different currencies.

My rule of thumb: whoever wants to scale and has basic technical knowledge self-hosts. Whoever wants to start fast takes the cloud and keeps the move in mind as an option.

If you are unsure which route fits your setup, or you are looking for someone to take on the hosting including maintenance: get in touch with Flowhouse. We will also tell you when the cloud is the better choice for you.