When I tell clients I run n8n for their automations, one of the first questions is: where does it actually run? The answer is on a private server. That's what self-hosting means, but it's not one single thing. There are several ways to do it, and they have very different levels of complexity, cost, and control.
What self-hosting actually means
Instead of using n8n's cloud service (where n8n runs everything on their own servers and bills you per execution), you run n8n on infrastructure you control. That infrastructure could be a managed cloud platform, a rented virtual server, or even a machine sitting in your home office.
The workflows still look the same. The editor still opens in a browser. The difference is entirely in who controls the environment it runs in.
The three ways to self-host n8n
1. A managed platform (Zeabur, Railway, Render)
This is the lightest version of self-hosting. Platforms like Zeabur let you deploy n8n as an application. You don't manage a server, you just configure and deploy the app. The platform handles uptime, infrastructure, and scaling.
This is actually how I run my own n8n instance. It sits on Zeabur, which means I get the benefits of self-hosting (my own instance, my own data, flat monthly cost) without managing the underlying server infrastructure myself.
Good for: people who want to self-host without deep technical server management. You still get a dedicated n8n instance and predictable pricing.
Watch out for: you're still relying on the platform's availability and pricing. More control than n8n Cloud, but less than a VPS you manage yourself.
2. A VPS (Hetzner, DigitalOcean, Contabo)
A virtual private server is a rented slice of a physical machine in a data centre. You get root access, install whatever you need, and manage it yourself. For n8n, a typical setup uses Docker Compose: n8n, a PostgreSQL database, and a reverse proxy for SSL.
Hetzner's CX22 (2 vCPU, 4 GB RAM) runs at around €4–6 per month and handles most business automation setups without issue. For EU clients this is often the right choice because the servers are in Germany or Finland, which makes GDPR compliance straightforward.
Good for: full control, lowest cost, GDPR-friendly data residency. You decide everything.
Watch out for: you're responsible for updates, backups, security patches, and recovery if something goes wrong. It's not complicated, but someone has to do it.
3. A home server
You can also run n8n on your own physical hardware: an old computer, a Raspberry Pi, a NAS device, or a dedicated home server. The software setup is identical to a VPS, but the machine sits in your home rather than a data centre.
The main appeal is cost: if you already have the hardware, the ongoing running cost is just electricity. For personal projects or internal tools that only need to be accessible from home, this can work well.
Good for: personal use, experimentation, situations where the automation only needs to run locally.
Watch out for: home internet connections typically have variable uptime and no guaranteed bandwidth. If your router restarts or your ISP has an outage, your automations stop. You'll also need to handle dynamic IP addresses if you want external access, and your data sits at home rather than in a data centre with proper physical security.
Cloud vs self-hosted: the real differences
| n8n Cloud | Self-hosted | |
|---|---|---|
| Setup | Instant, no configuration | Varies: minutes (platform) to a few hours (VPS/home) |
| Your data | Stored on n8n's servers | Stays within your infrastructure |
| Cost | Per-execution pricing | Flat cost: platform fee or server rental |
| Maintenance | Handled by n8n | You, or your automation partner |
| Execution limits | Based on your plan | Unlimited |
| External access | Always available | Depends on setup |
When self-hosting makes sense
Data privacy and compliance. For businesses handling client data, financial records, or anything under GDPR, self-hosting means that data never passes through n8n's infrastructure. Whether you use Zeabur, a VPS, or a home server, the data stays within what you control.
Cost at scale. n8n Cloud charges per execution. Once you have dozens of workflows running thousands of times per month, that adds up quickly. A self-hosted instance, whether on a platform or a VPS, has a flat monthly cost that doesn't care how many times your workflows run.
Ownership and control. You decide when to update, how to back up, and how to recover. You're not subject to pricing changes or feature limits set by someone else.
When the n8n cloud is fine
If you're just getting started with automation, the cloud version is perfectly reasonable. There's no setup, updates happen automatically, and you can focus on building workflows rather than infrastructure.
The cloud also makes sense if your usage is low and your data isn't sensitive. If your workflows run a few hundred times per month and you're not dealing with anything compliance-relevant, the per-execution cost is manageable and the simplicity is worth it.
One thing most people underestimate
Self-hosting is not just a technical decision. It's also an operational one. Someone needs to make sure the instance stays up, updates get applied correctly, and backups actually work. That looks different depending on which path you choose: a managed platform handles more of this for you, while a VPS or home server puts it fully on you.
If you're not technical, it's worth factoring this in before you commit to a setup. You can go with n8n Cloud and leave all the management to n8n, or self-host and handle it yourself. If you want to self-host but don't want to deal with the ongoing management, that's a retainer conversation, not something that comes included with a one-time setup.
Curious which self-hosting option fits your situation, or whether n8n Cloud would actually be fine? That's a free discovery call.