You have decided that n8n is the right automation tool. Good. Now comes the question many founders get stuck on: do you run it on your own server, use n8n Cloud, or have a partner manage it? It looks like a technical decision, but in practice it is about control, cost, GDPR and how much time you want to spend internally on maintenance. This article lines up the three paths in numbers and scenarios, and gives you a decision checklist that delivers an answer in ten minutes. No sales pitch. Just an honest assessment you can apply the same afternoon.
For the broader trade-off see our AI automation SMB guide and zapier vs make vs n8n.
What is n8n exactly?
n8n is an open-source automation platform, designed in Berlin. Comparable to Zapier or Make in terms of visual flows, but with two important differences: it is free to download, and you can run it on your own server. As a result you have no variable cost per action, and your data never leaves your environment unless you want it to. n8n combines a visual canvas with the option to drop JavaScript or Python code into your flow, so you do not get stuck on standard connectors.
For the broader comparison between automation tools read Zapier vs Make vs n8n. Short summary: for SMBs with serious volume or sensitive data, n8n is the best choice in 80 percent of cases. But once you choose n8n, you face a second question: hosting.
Which hosting options do you have?
There are three realistic paths for n8n in a production setup. Each path has its own price tag, control level and maintenance burden.
- Self-host on your own VPS. You rent a server from Hetzner, DigitalOcean or TransIP, install n8n via Docker and manage everything yourself. Full control, lowest cost, highest maintenance load.
- n8n Cloud (the official managed version). The company behind n8n offers a hosted version from around €20 per month. You do not need to install or maintain anything, but you pay per execution above the base volume and run on their infrastructure.
- Managed hosting via an agency. A partner like us at TopDevs installs n8n on your own VPS (or ours), handles backups, monitoring and updates, and delivers an SLA. Fixed monthly price, your own data residency, but you rely on an external party for incidents.
In practice we see founders often consider Cloud because it looks “easier”, but they do not run the math on a one-year basis. Others pick self-host because it looks “cheaper”, but underestimate the hours that go into updates and monitoring. Hence this comparison.
What do the costs look like?
Costs vary widely based on volume. For n8n the rule is: the higher your volume, the bigger the gap between Cloud and self-host. Below the three paths side by side at four volume levels.
| Volume per month | Self-host VPS | n8n Cloud | Managed via agency |
|---|---|---|---|
| 1,000 executions | €10-15 | €20 (Starter) | €95-150 |
| 10,000 executions | €10-15 | €50 (Pro) | €95-150 |
| 100,000 executions | €15-30 | €220 (Business) | €150-250 |
| 500,000 executions | €30-60 | €500+ (Enterprise) | €250-450 |
What stands out: self-host stays the cheapest option across the board on raw euro cost. But that is only the tooling portion. For self-host at larger setups, count on an average of 2 to 4 hours per month of internal maintenance. At an hourly rate of €75 that is already €150 to €300 of hidden cost per month. Only then do you compare apples to apples.
What are the control and technical differences?
Cost is one side. What you can and may do technically is another. Below a feature matrix on the points that come up most in SMB projects.
| Feature | Self-host VPS | n8n Cloud | Managed via agency |
|---|---|---|---|
| Own data location | Full (choose VPS region) | EU or US (Cloud setting) | Full (your own VPS) |
| Custom code nodes (JS/Python) | Full | Full | Full |
| Custom Docker images or plugins | Yes | Limited | Yes |
| Automatic backups | Set up yourself | Included by default | Included by default |
| Security updates | Maintain yourself | Automatic | Handled by agency |
| Uptime SLA | None | Standard 99.9% | Tailored per contract |
| Setup time | 2-4 hours | 15 minutes | 1-2 weeks (including migration) |
| Scalability at peak | Server upgrade needed | Automatic | Handled by agency |
In short: n8n Cloud wins on ease and automation, self-host wins on control and cost, and managed combines the best of both for a fixed monthly fee. Which combination works for you depends on two variables: how sensitive is your data, and how much devops capacity do you have internally.
How does GDPR and EU hosting fit in?
For Dutch SMBs working with customer data, personal data or sensitive documents, data residency is a real concern. GDPR requires you to know where data sits, who can access it, and which sub-processors you work with. The three paths differ significantly here.
- Self-host on Hetzner Nuremberg or a Dutch VPS gives you full control. Data never leaves your server, you choose the region yourself and you only have a handful of sub-processors (cloud provider, possibly a backup target). For legal, medical or financial clients often the only workable choice.
- n8n Cloud is GDPR-compliant and offers EU hosting (Frankfurt). Well documented in the hosting docs. But n8n is a German company with operations that partly run via American parties (such as Stripe for billing). Fine for most use cases, for strictly regulated sectors it is wise to read the DPA and sub-processor list carefully.
- Managed via a Dutch agency gives you a Data Processing Agreement under Dutch law, a server in the Netherlands or Germany, and a single point of contact for incidents. For most SMBs the most pragmatic option.
A fair nuance: GDPR compliance is about more than just server location. It also covers who has access, how you set up encryption, which logs you keep and how you report incidents. But as a starting point: for sensitive data, self-host or managed via an EU party is by far the safest route. Also read ai-automatisering-mkb-gids for the broader GDPR context with AI flows.
What are the real maintenance costs of self-hosting?
On paper self-host costs €10 to €30 per month. In practice there is more to it. Honest overview of what a healthy n8n installation costs in time, based on our own client projects over the past 18 months.
- Initial setup: 4 to 8 hours one-off. Provision server, install Docker, configure n8n, set up reverse proxy (Caddy or Traefik), SSL certificate, firewall rules, first backup job. We have standardized this, but the first time on your own takes a day.
- Backups: 1 hour initially, then automatic. A daily dump of the Postgres database and the workflow files to, for example, Cloudflare R2 or an offsite bucket. Once set up it runs, but you must verify the backup restore monthly.
- Monitoring: 2-3 hours initially. A healthcheck to healthchecks.io or UptimeRobot. Slack alert on downtime. Optional: log aggregation to Grafana or Loki. Without monitoring you only learn n8n is broken when a customer calls, and by then you are too late.
- Security updates: 1-2 hours per month. n8n releases regularly, sometimes with breaking changes. You need to track versions, test in staging, and upgrade in production. Plus OS patches on the VPS itself.
- Incident response: unpredictable. Once per quarter something breaks (failed deploy, expired SSL, disk full). Count on 2 to 4 hours per incident, with an occasional outlier of a full day.
Combined: on average 3 to 5 hours per month for a healthy n8n installation on your own server. At an internal hourly rate of €75 that is €225 to €375 per month in hidden cost. Compare that to the €50 that n8n Cloud costs for an average SMB volume, and the balance shifts quickly. Self-host pays off mainly if you already have someone internally who can do this on the side, or if your volume is so high that the tooling savings comfortably offset the hours.
When do you choose n8n Cloud?
n8n Cloud is strong when speed and simplicity matter more than long-term cost or full data control. Three scenarios where Cloud is the right pick:
- You want to be live with your first workflow within 15 minutes, without server installations or Docker commands.
- Your team has no devops capacity and you do not want to carry the mental load of a production system internally.
- Your volume stays below 50,000 executions per month and the €50 subscription is no issue against the savings on internal hours.
For solo founders, small teams (under ten people) and businesses that use n8n mostly as an experimentation platform, Cloud is often the pragmatic choice. Setup is trivial and you pay for what you use.
When do you choose self-host?
Self-host is the choice if you prioritize control, cost at scale, or very sensitive data. Three scenarios where self-host is the clear winner:
- Your volume exceeds 100,000 executions per month and Cloud costs are creeping toward €200+ per month.
- You work with data that legally or contractually cannot leave the Netherlands or the EU (think legal files, medical data, financial transactions).
- You have someone internally with basic Linux or Docker skills who can take on server management, or you work with an agency that handles this for you.
Self-hosting sounds heavy, but in practice a healthy n8n installation runs at our shop on a Hetzner VPS of €10 per month, with automatic backups, monitoring and SSL. Once set up it runs for months without intervention. How we set this up for a real client you can see in our Planit case study. Want to have this built as a custom platform, we deliver the full setup including code ownership and an SLA.
How does managed hosting via an agency work?
The third path is what we at TopDevs do for the majority of our clients: self-host on a Hetzner VPS, with monitoring, backups and updates that we handle via a fixed monthly SLA. The client retains data residency and code ownership, while we carry the operational load.
In practice the setup looks like this. A one-off fee of €495 to €1,500 for the initial install (provision server, configure n8n, migrate first workflows, set up monitoring). Then €95 to €250 per month for the SLA, depending on volume and desired response times. The server is registered in the name of the client or our shop, depending on preference. All workflow files are JSON that the client can export at any time.
- Fixed monthly price. No surprises when volume grows, unless we need to upgrade the server (agreed upfront).
- Your own data residency. Server in the Netherlands or Germany, no US intermediary, DPA under Dutch law.
- Code ownership. All workflows, scripts and configuration belong to the client. No lock-in, no hidden proprietary layers.
- Fix guarantee. What we build must work as agreed. We resolve bugs within the agreed response time without extra cost.
Whether this makes more sense for your business than doing it yourself or picking Cloud depends on internal capacity and yearly volume. For an SMB with 50,000+ executions per month and no internal devops, managed is almost always the cheapest path over three years, simply because the hidden maintenance hours of self-host exceed the SLA cost.
How do you start concretely?
A fast decision checklist based on five questions. Answer them in order, and within five minutes you know which path fits.
- How many executions per month do you expect in year 1? Below 10,000? Start with Cloud. Above 100,000? Go directly to self-host or managed.
- How sensitive is your data? Customer personal data, legal files or medical data? Self-host or managed within the EU. Standard business data? Cloud is fine.
- Do you have someone internally with Docker or Linux experience who can take this on? Yes? Self-host works. No? Cloud or managed.
- How important is predictability of cost? Fixed monthly price essential? Self-host or managed. Per-execution model acceptable? Cloud is fine.
- Do you want to be able to take the reins back in the future without migration pain? Self-host or managed deliver you the JSON files by default. With Cloud you can export, but you lose the hosting layer.
Still unsure? Book a free intake call. In thirty minutes we look at your volume, your data requirements and your internal capacity, and give honest advice on which path delivers most. No sales pressure, even if the conclusion is that you can run it yourself on n8n Cloud. Our way of working and guarantees are in our terms, so you know in advance what to expect.
