Automation · Tools Self-hosting n8n in the EU: server, licence, security and operation

Cloud or self-hosted?

The cloud is the simplest route if your processes mainly connect cloud services. Self-hosting pays off if n8n needs to reach systems on your own network, if your data protection requirements demand a specific location or if you run many processes with high volumes.

What the licence allows

n8n is published under the Sustainable Use License. It allows use and modification for your own internal business purposes and for personal or non-commercial purposes. A company may therefore run n8n on its own servers and automate its processes with it. What is not allowed is offering n8n itself as a paid service to others. Some features for larger organisations are part of the Business and Enterprise editions and need a licence key. Without a key, the free Community Edition runs.

The building blocks of a clean setup

1. A server in the EU: a virtual server with a provider that has a data centre in the EU, or a server in-house. For many businesses a small machine is enough to start with.
2. Docker Compose: n8n recommends Docker Compose for production. n8n, the database and the proxy then run as separate containers.
3. PostgreSQL: by default n8n uses SQLite. For production we recommend PostgreSQL, because backups, maintenance and later expansion are easier.
4. HTTPS through a reverse proxy: n8n runs internally, and a proxy such as Caddy, Traefik or nginx handles the certificate and forwards requests.
5. Secure the key: n8n encrypts stored credentials with its own key. If it is lost, all stored credentials become unusable.
6. Limit access: user accounts with two-factor sign-in, the editor ideally only via VPN or approved addresses, webhooks public only where intended.

The most important settings in the environment file look roughly like this:

DB_TYPE=postgresdb
DB_POSTGRESDB_HOST=postgres
N8N_HOST=n8n.example.eu
N8N_PROTOCOL=https
WEBHOOK_URL=https://n8n.example.eu/
GENERIC_TIMEZONE=Europe/London
N8N_ENCRYPTION_KEY=a-long-random-key
N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true

Operation: what comes after setup

• Updates: keep n8n up to date. The project publishes security advisories regularly; on 14 October 2026 alone there were ten. Test updates in a copy first if important processes depend on them.
• Backups: back up the database and the key daily, separately from the server. Once a quarter, actually try out the restore.
• Monitoring: have failed executions reported, for example by email or chat, and keep an eye on storage, load and certificate.
• Clean up execution data: n8n stores the inputs and outputs of executions. Decide how long this data is kept, also for data protection reasons.
• Scaling: with many simultaneous executions, n8n can run in queue mode with Redis and several worker processes.

Data protection: what the server location solves and what it does not

A server in the EU only solves part of the questions. As soon as a process sends data to other services, such as a language model, a CRM or an email provider, their locations and contracts apply. For every connected service, check where it processes data and conclude the necessary data processing agreements. For AI building blocks there are models that run in EU data centres or models you operate yourself. More in our article AI with your own company data.

Operate it yourself or have it operated?

Self-hosting fits if your IT has experience with Linux, Docker and backups and plans time for updates. If that is missing, the cloud version or a service provider who runs the server is usually the better choice. When an agency pays off and what it should deliver is covered in the article n8n agency or DIY.