Is self-hosting cheaper than the cloud version?

The software is free, but you pay for the server and for the upkeep. With few workflows the cloud version is often better value once you count the hours. At high volume or with strict data requirements it tips towards self-hosting.

Which server do I need?

For most small-business workflows a small VPS with 2 CPUs and 4 GB of memory is enough. If you run heavy workflows or many at once, you scale up.

How do I keep it secure?

Put n8n behind HTTPS, enable authentication, limit who can reach it and make daily backups of the database. Keep the version up to date for security fixes.

Guide · 1 min read

Self-hosting n8n: when, how and what to watch out for

Running n8n yourself on your own server gives you control and keeps your data in-house. The trade-offs, a Docker setup in outline, and what really needs your attention.

Self-hosting n8n means you run it on a server you manage, instead of on n8n's cloud. Two reasons to do that: your data stays inside your own environment, and at high workflow volumes it's cheaper in the long run. The price you pay: you're responsible for updates, backups and security yourself.

Not quite sure yet what n8n is? Then start with the explanation.

Cloud or self-hosted

Choose the cloud version if you want to start quickly and don't want to lie awake over server management. Choose self-hosting if you process sensitive data (customer details, medical or financial data), if you run a lot of workflows, or if you simply like to keep control. For many of our clients with a privacy requirement, that's the deciding factor.

The setup in outline

The usual way is with Docker. On a fresh VPS it comes down to:

Install Docker and Docker Compose on your server
Create a docker-compose.yml with the n8n image and a Postgres database for storage
Set the basics (username, password, your domain name)
Put a reverse proxy in front of it (Caddy or Nginx) to handle HTTPS
Start the container and log in to your own n8n

Sound like a lot? It is, the first time. After that it runs quietly in the background.

What really needs your attention

Backups. Your workflows and login details live in the database. Back it up daily, and test once that you can restore it.
Security. HTTPS on, authentication on, and limit who can reach the server. An open n8n on the internet is asking for trouble.
Updates. n8n releases new versions regularly, including security fixes. Schedule a fixed moment to update.
Secrets. API keys belong in n8n's credentials vault, not loose in a workflow.

This is exactly the kind of work that makes the difference between "it runs" and "it still runs a year from now". How we set that up is covered under system integrations.

Rather not do it yourself

Self-hosting is powerful, but it's something you have to do well. Want the benefits without the management? We set up your n8n safely and keep it running, whether you build on from there yourself or hand it all over. Want to talk it through first? Get in touch.