Installing n8n on Hetzner: GDPR-compliant automation server

n8n can be self-hosted on a Hetzner Cloud server via Docker Compose: the official n8n documentation recommends the CPX11 server type for Hetzner deployment, along with the Caddy reverse proxy for TLS encryption and domain connection. Because Hetzner operates German and other European data centers, workflow data, credentials, and connections to third-party systems remain within the EU, which creates the basis for GDPR-compliant automation. Anyone who self-hosts n8n also takes on full responsibility for server maintenance, updates, and security. As of: July 2026.

Which Hetzner server does n8n need?

For most use cases, the smallest cloud server type, CPX11, is sufficient according to the n8n documentation. When creating the server, select the Docker CE image directly in the Apps section so that Docker is already preinstalled. For access to the server, n8n recommends SSH authentication instead of a password, since it is significantly more secure. Only when workflows process very many parallel executions or large amounts of data does a larger server type with more memory become worthwhile.

How do you install n8n with Docker Compose on Hetzner?

The installation follows a fixed process, which the official Hetzner guide from n8n describes.

• Install the Docker Compose plugin: After a system update, the docker-compose-plugin package is installed.
• Clone the repository: The official n8n-io/n8n-docker-caddy repository provides the matching Compose configuration including Caddy.
• Create Docker volumes: Separate volumes are created for Caddy data and n8n data respectively, so that certificates and workflow data survive restarts.
• Set environment variables: In the .env file, you specify the domain, time zone, and other basic values for the installation.
• Open the firewall: Ports 80 and 443 must be opened for HTTP and HTTPS.
• Adjust the Caddyfile: The subdomain in the format n8n.yourdomain.tld is entered in the Caddyfile so that Caddy automatically obtains a valid TLS certificate.
• Start the containers: The command docker compose up -d starts n8n and Caddy in the background.

For updates, the same three-step process applies as for any Docker Compose installation: pull the new image, stop the container, restart the container with the new version.

Why does the server location matter for GDPR-compliant n8n hosting?

The server location is an important but not the only building block of GDPR compliance. If n8n runs at a German or European Hetzner location, personal data from your workflows generally does not leave the European legal area, provided that connected third-party systems such as email delivery, CRM, or AI services are also chosen accordingly. Full compliance additionally depends on a data processing agreement with Hetzner, a well-thought-out backup strategy, and securing the server against unauthorized access. n8n explicitly points out in its own documentation that self-hosting requires expertise in server configuration, container management, scaling, and security, and that mistakes can lead to data loss, security vulnerabilities, or downtime.

How does the Hetzner installation differ from a generic Docker Compose installation?

The Hetzner-specific guide relies on Caddy as the reverse proxy, while n8n's general Docker Compose guide uses Traefik. Both variants perform the same task: they handle TLS encryption via Let's Encrypt and forward requests to the n8n container on port 5678. In the generic variant, you configure, among other things, the variables N8N_HOST for the reachable domain, N8N_PROTOCOL for https, WEBHOOK_URL for the public webhook address, and GENERIC_TIMEZONE for the time zone of your planned workflows, as n8n's Docker Compose documentation describes. For productive use with multiple users, switching from the included SQLite database to PostgreSQL is also recommended.

For whom is self-hosting on Hetzner worthwhile instead of n8n Cloud?

Self-hosting is worthwhile above all for companies that have their own server expertise in-house or commission a fixed contact person for maintenance and security. n8n itself recommends the hosted cloud variant to beginners without experience in server administration, because with self-hosting, updates, backups, and security patches are entirely the user's own responsibility. For SMEs that value German data sovereignty but do not want to build up their own capacity for server operation, we at NordFlux take over the setup and handover of a Hetzner-based n8n server as a fixed-price project, see our n8n services. This gives you a documented, maintainable server without having to familiarize yourself with Caddy configuration and Docker networks.

Frequently asked questions about n8n on Hetzner

Is Hetzner GDPR-compliant for n8n hosting?

A Hetzner server in a German or European data center forms a solid basis for GDPR-compliant hosting, because data remains within the European legal area. Full compliance additionally requires a data processing agreement, a documented backup strategy, and careful protection of the server against unauthorized access.

Which Hetzner server type is sufficient for n8n?

According to the n8n documentation, the smallest cloud server type, CPX11, is sufficient for most usage levels. Only with many parallel workflow executions or large amounts of data does a more powerful server become worthwhile.

Does n8n on Hetzner necessarily need its own domain?

Yes, a secure HTTPS connection via Caddy or Traefik requires a subdomain that points to the server IP via a DNS A record. Without a valid domain, no automatic Let's Encrypt certificate can be obtained, which would leave webhooks and access to the interface insecure.

Can n8n also be installed on Hetzner without Docker?

n8n itself names Docker as the variant recommended for most deployments, among other things because it avoids operating system and tooling incompatibilities and simplifies database and environment management. According to the documentation, an installation via npm is rather intended for local development, testing, or simple single-server deployments, not for a productively running Hetzner server.