What’s the best server configuration for n8n?
When deciding what’s the best server configuration for n8n, a small Docker-based VPS with 2 vCPU, 2–4 GB RAM, persistent storage and daily backups is a solid starting point. This setup gives beginners a balance of cost, reliability and ease of management while supporting typical automation workloads.
Recommended setup: what’s the best server configuration for n8n?
Start with a single VPS that runs n8n in a container or under Node.js. Use persistent disk for workflow data and a separate location for logs. Choose a plan that offers at least 2 vCPU and 2–4 GB RAM to avoid performance bottlenecks during normal use.
Why these choices matter
CPU affects how fast workflows run, especially when many tasks run in parallel. RAM protects against crashes when large payloads are processed. Persistent storage ensures workflows and credentials survive restarts. Swap can help for brief memory spikes.
Hosting options and trade-offs: Docker, VPS, Node.js
Docker on a VPS is the simplest for new users. It isolates n8n and makes updates easier. Running n8n directly with Node.js can be lighter but needs more hands-on maintenance. Managed cloud options reduce setup work but cost more. Self-hosting gives full control of data and scaling.
Sizing guidance and scaling tips
- Small start: 2 vCPU, 2–4 GB RAM, 20–40 GB disk for stored data and logs.
- Moderate load: 4 vCPU, 8 GB RAM, faster disk (SSD) and daily backups.
- High load: use multiple containers, separate database, and consider horizontal scaling.
Summary
For most beginners, a Docker container on a 2 vCPU, 2–4 GB RAM VPS with persistent storage and backups is the best balance of simplicity, cost and reliability. Adjust CPU, memory and storage as your automations grow and monitor resource use to guide upgrades.