n8n self-hosting guide: when it's worth it, and how to do it safely

Self-hosted n8n costs almost nothing in software and keeps your workflow data on infrastructure you control. It also means you own the uptime, backups, and security. Here's how to decide, and what a safe setup actually needs.

Full platform comparison: n8n vs Zapier vs Make. This guide only covers the self-hosting decision and setup, for readers who already know they want n8n specifically.

Self-hosted vs n8n Cloud: when to choose which

Choose n8n Cloud if: you want zero server maintenance, predictable per-execution billing works for your volume, and nobody on the team wants to own a Linux box.

Choose self-hosted if: data residency or compliance rules mean workflow data can't sit on third-party cloud infrastructure, your execution volume would make cloud billing expensive, or you want full control over update timing and backup policy rather than a vendor's schedule.

What it actually costs

The software cost is close to zero. The real cost is the time to set it up correctly and keep it patched — that's the trade you're making against n8n Cloud's monthly fee.

A basic Docker setup

The standard path is Docker Compose on a small Linux VPS. At minimum you need:

• A VPS with at least 1 vCPU / 2GB RAM for light workloads
• Docker and Docker Compose installed
• A Postgres database (SQLite works for testing, not production)
• A reverse proxy (Caddy or nginx) handling SSL termination
• A domain or subdomain pointed at the server

n8n publishes an official Docker Compose reference in their hosting documentation— start there rather than a third-party tutorial, since self-hosting instructions change between n8n versions.

Security checklist most teams skip

• Enable basic auth or SSO on the n8n editor UI itself — an unauthenticated instance exposed to the internet is a real, common misconfiguration.
• Use environment variables for credentials, not hardcoded values in workflow nodes, so secrets don't leak into exported workflow JSON.
• Set up automated database backups — workflow definitions and execution history live in Postgres. No backup means a server failure erases everything.
• Plan for updates. New n8n versions ship regularly. Self-hosting means you own upgrade timing — decide a cadence rather than running an ancient version indefinitely.
• Restrict webhook exposure to what actually needs to be public. Not every workflow needs an internet-facing endpoint.
• Name an owner. An unowned self-hosted instance is the same risk as an unowned automation — see the cost of an unowned automation.

When to hire this out instead

If the workflow is core to revenue or compliance, a DIY server that nobody owns is a liability, not a cost saving. We set up and hand over self-hosted n8n instances — hardened, backed up, documented — as part of a fixed-price build, with credentials transferred so you're never locked in. See pricing.

FAQ