Quick answer: Small n8n workflows can run on a modest VPS. Production n8n needs enough RAM, a real database, backups, and monitoring so workflows do not silently stop.
This guide targets the search intent behind n8n system requirements 2026, n8n self-hosted system requirements 2026, n8n vps requirements, best vps for n8n self-hosted 2026. It is written for buyers who want a real setup decision, not another generic definition page.
Who this guide is for
This guide is for developers, agencies, and small teams self-hosting n8n for webhooks, CRM sync, AI automations, ecommerce tasks, and scheduled jobs.
Recommended baseline
| Scenario | Baseline | Notes |
|---|---|---|
| Testing n8n | 1 to 2 vCPU, 2 GB RAM | SQLite is acceptable for learning |
| Small production | 2 vCPU, 4 GB RAM | Use Postgres and backups |
| Busy automations | 4 vCPU, 8 GB RAM | Consider queue mode |
| Agency workloads | Dedicated database and monitoring | Separate critical clients |
Setup checklist
- Use Docker Compose for repeatable installs.
- Set the encryption key once and keep it safe.
- Back up database and credentials.
- Put n8n behind HTTPS.
- Monitor failed executions and disk usage.
Common mistakes
- Running production workflows on a laptop.
- Forgetting the encryption key.
- Letting execution logs fill disk.
- Using SQLite for busy multi-user automation.
Space-Node recommendation
Use VPS hosting for self-hosted n8n. Start small, then scale CPU and RAM when workflow concurrency grows.
FAQ
Can I start smaller and upgrade later?
Yes. Start with the smallest plan that fits the baseline, monitor CPU, RAM, disk, and network for a few real sessions, then upgrade when the graphs show a bottleneck. Guessing too high wastes money. Guessing too low creates downtime.
Is bandwidth or CPU more important?
It depends on the workload. Video streaming cares about stable outbound bandwidth and encoding headroom. Minecraft, FiveM, Discord bots, and n8n usually hit CPU, RAM, database, or bad configuration first.
Should I use a VPS or a managed product?
Use a managed product when you want speed and support. Use a VPS when you need root access, custom software, Docker, or unusual workflows. If the workload is public or revenue critical, avoid anonymous ultra-cheap hosts with unclear limits.