24/7 Technical Support
Access our dedicated support team around the clock to assist with any n8n VPS issues, ensuring your automation workflows run smoothly and without interruption.
Express Linux VPS
Express Plus Linux VPS
Basic Linux VPS
Basic Plus Linux VPS
Professional Linux VPS
Professional Plus Linux VPS
Advanced Linux VPS
Advanced Plus Linux VPS
| Recommended VPS Plan | n8n Task Load / Workflow Volume | Usage Tips / Notes |
|---|---|---|
| Express Linux VPS | Light – <100 tasks/day | Best for testing and small personal automations. Use SQLite or lightweight PostgreSQL. Schedule non-critical workflows during off-peak hours. |
| Express Plus Linux VPS | Low to Moderate – 100–300 tasks/day | Suitable for small teams. Enable basic logging and modularize workflows to avoid execution bottlenecks. |
| Basic Linux VPS | Moderate – 300–800 tasks/day | Switch fully to PostgreSQL. Enable database indexing and begin using webhook-first trigger design. |
| Basic Plus Linux VPS | Growing Business – 800–1,500 tasks/day | Enable queue mode to prevent overload during traffic spikes. Separate critical workflows from non-critical ones. |
| Professional Linux VPS | High – 1,500–3,000 tasks/day | Implement structured logging and monitoring. Optimize API-heavy workflows with caching strategies. |
| Professional Plus Linux VPS | High Volume – 3,000–5,000 tasks/day | Workflow isolation recommended. Tune execution queue workers for higher concurrency. |
| Advanced (Plus) Linux VPS | Enterprise – 5,000–8,000 tasks/day | Deploy reverse proxy and monitoring stack. Prepare scaling plan for database and execution layers. |
| Express Dedicated Server or Higher | Mission-Critical – >8,000 tasks/day | Deploy multiple n8n instances behind reverse proxy. Separate database server recommended. Ideal for large-scale enterprise automation. |
| Feature | n8n VPS | Dedicated Server | Note |
|---|---|---|---|
| CPU | Virtual CPU (2–16 cores depending on plan) | Full dedicated CPU (4–24+ cores) | CPU cores affect how many workflows and webhook tasks can run concurrently, especially for API-heavy or computation-heavy automations |
| RAM | 2–16 GB | 16–256 GB | More RAM allows larger workflow caching, smoother concurrency, and better handling of multiple parallel executions |
| Storage | SSD 40–400 GB | SSD/NVMe/SATA 1TB–96TB | Storage affects workflow logs, database size, file attachments, and large payload handling |
| I/O Performance | Moderate | High | Dedicated disk I/O reduces latency for database queries, webhook processing, and serving large files |
| n8n Task Load | 50–8,000 tasks/day (depending on plan) | 8,000+ tasks/day | Determines how many workflows or webhook executions can run simultaneously without delays |
| Caching | Redis / Memcached | Redis / Memcached with larger memory allocation | Improves workflow execution speed, reduces database load, and accelerates API-heavy workflows |
| Uptime & Reliability | 99.9% uptime, shared resources | 99.99% uptime, fully dedicated resources | VPS provides stable access for small/medium automation; dedicated ensures highly reliable, mission-critical workflow execution |
| Scalability | CPU up to 16 cores, RAM up to 16GB, SSD up to 400GB | Full hardware control; can add CPU, RAM, storage | Dedicated servers support multiple n8n instances, clustering, and scaling for growing automation needs |
| Cost | Lower | Higher | VPS is cost-efficient for small-to-medium n8n automation workloads; dedicated servers are more expensive but deliver predictable high performance for enterprise-scale or mission-critical workflows |
What is self hosted n8n and why should I use it?
Can I integrate self hosted n8n with other internal services?
Is n8n VPS hosting secure?
How can I scale n8n self hosting as my automation grows?
Can I run multiple self hosted n8n instances on the same VPS?
What happens if my VPS reaches resource limits?