We want to self-host n8n on Docker, what are the basics?
n8n self-host fits SMBs that want data control and lower cost. It doesn't need a Kubernetes cluster: a 4GB VPS with Docker Compose is usually enough.
Try this first
- 1Pick the host: Hetzner, DigitalOcean or Azure VM in EU region. 4GB RAM and 2 vCPUs is a comfortable starting point for SMB volumes.
- 2Use Docker Compose with n8n + Postgres + Traefik (or Caddy) for TLS. Put basic-auth or OAuth proxy in front, not directly exposed.
- 3Persist data: Postgres volume for database, local or S3 volume for binary data and credentials. Check n8n.io/hosting docs for the right env vars.
- 4Backup: daily Postgres dump to offsite (S3, Backblaze, own NAS). Without backup you lose workflow history and credentials on a disk crash.
- 5Updates: pin a version in compose and update deliberately each month. n8n rarely breaks, but 'latest' in prod is still a gamble.
When to bring us in
Need self-host n8n with multi-user, at-rest encryption, and backup monitoring, setup is a day's work. We can help.
See also
- n8n: self-host or cloud?Self-hosted is cheaper at volume and keeps data local. Cloud removes ops burden.
- Zapier or Make: which fits better?Zapier is straight-line; Make handles complex flows with routers and iterators for less money.
- Power Automate Cloud or Desktop: which to use?Cloud for SaaS integrations and triggers. Desktop for RPA against legacy Windows apps without APIs.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.