HomeReadTools deskn8n Self-Hosting on Hetzner: One Year of Operational Lessons and Cost Savings
Tools·May 31, 2026

n8n Self-Hosting on Hetzner: One Year of Operational Lessons and Cost Savings

This review examines a year of self-hosting n8n on a Hetzner VPS, detailing setup, costs, and operational trade-offs. We analyze the practical implications of owning your workflow automation…

This review examines a year of self-hosting n8n on a Hetzner VPS, detailing setup, costs, and operational trade-offs. We analyze the practical implications of owning your workflow automation infrastructure.

TL;DR

Best for: Developers or small teams prioritizing full control over workflow automation, comfortable with Docker and basic sysadmin, and seeking cost efficiency over SaaS convenience. Skip if: You require zero operational overhead, depend on vendor-managed upgrades, or lack the technical expertise for self-hosting. Bottom line: Self-hosting n8n offers significant control and cost savings, but demands a disciplined approach to versioning and environment management.

Methodology

This v0 review draws on the founder's published claims and operational notes at https://dev.to/lamas51/one-year-of-self-hosted-n8n-on-a-6-hetzner-vps-4ee7. Independent benchmarks are pending. Update cadence: re-tested when claims diverge from observed behavior.

This review covers n8n (version not explicitly stated for the initial setup, but later pinned to 1.45.x after an outage) as observed on 2026-05-27. The source signal details a year of continuous operation on a Hetzner Cloud CX22 VPS located in Falkenstein. We cover the specific Docker-based setup (n8n, Postgres, Caddy), the four production workflows running, the detailed cost breakdown, and the lessons learned from a single outage. What is not covered includes independent performance benchmarks under various loads, long-term workflow development velocity, or comprehensive security audits of the self-hosted environment. The analysis relies on the author's reported experience and conclusions.

What It Does

n8n is an open-source workflow automation tool, positioned as an alternative to SaaS platforms like Zapier. It allows users to define automated workflows that connect various services, APIs, and databases. The author's setup demonstrates a practical application of n8n in a self-hosted environment.

Core Automation Capabilities

n8n provides a visual interface for building workflows, handling triggers (webhooks, cron jobs, RSS polls) and actions (database writes, API calls, email sending, Slack/Telegram posts). The author uses it for four distinct production workflows, indicating its versatility for common automation tasks. These include a Telegram bot dispatcher, an RSS aggregator posting to Telegram, a form submission handler for CRM-lite functions, and a daily reporting cron job that pulls metrics and distributes digests.

Self-Hosted Architecture

The deployment leverages a Hetzner Cloud CX22 VPS (€4.51/mo) with 2 vCPU, 4 GB RAM, and 40 GB disk. The core stack runs within Docker, comprising the n8n container, a postgres:15 database for data storage and deduplication, and a caddy reverse proxy. Caddy is highlighted for its automatic TLS, HTTP→HTTPS redirects, and per-domain certificates, simplifying secure webhook reception. Backups are handled via borgbackup to a Hetzner Storage Box (€3.81/mo), with UFW configured to restrict inbound traffic to ports 22, 80, and 443.

Workflow Ownership

A key aspect emphasized by the author is that workflows are defined as git-tracked YAML files. This allows for version control, easier migration, and a clear audit trail of changes, contrasting with the opaque nature of workflows managed within many SaaS platforms. This ownership extends to the underlying infrastructure, providing complete control over data residency and system configuration.

What's Interesting / What's Not

The most interesting insight from this year-long review is the explicit articulation of the

Sources · how we verified
  1. One year of self-hosted n8n on a $6 Hetzner VPS

Every claim ties to a primary source. See our methodology.

Reported by the Riley desk on Founderr Pulse’s Tools beat. Every factual claim is tied to a primary source and linked; anything that can’t be stood up doesn’t run. Founderr (RIKHATH LLC) is the accountable publisher and corrects in place. How we work · About · File a correction.
R
Riley

The Riley desk covers tools — what founders are building with, switching to, and abandoning. Every claim is sourced and linked. Operated by Founderr (RIKHATH LLC) See the desk →

Founderr Pulse — free & independent. The desk for people who build & back.