n8n
Compare VPS plans to self-host n8n. providers advertising 1GB+ RAM from $2/mo. n8n server hosting comparison.
Find the best and cheapest VPS plans to self-host n8n.
Minimum Requirements
These VPS plans meet the minimum requirements to run n8n. Suitable for testing or light usage.
Recommended Requirements
For optimal performance, we recommend these VPS plans that exceed the minimum requirements.
Source: self-hosted-tools.json
n8n VPS Sizing: Storage, Sync, and Scale
n8n is a workflow automation platform that connects APIs, webhooks, schedules, databases, and third-party services. Hosting choice affects whether workflows execute on time, whether webhook responses stay fast, and whether execution history writes or external calls create backlogs.
Resource Profile Classification
The primary resource profile is Mixed. self-hosted-tools.json moves from 1 GB minimum RAM to a 4 GB production baseline, while the workload itself is I/O-bound and network-sensitive: workflows wait on external APIs, write execution state, process payloads, and may hold memory during long runs. Many workflows turn RAM pressure into the visible failure mode, but I/O and outbound reliability are the sizing logic.
n8n starts as an I/O-bound and network-sensitive automation service because every workflow depends on external APIs, database writes, webhook traffic, and execution history; RAM becomes visible when many or large workflows run at the same time.
Storage and Network Interpretation
n8n storage needs depend on workflow definitions, credentials metadata, logs, execution history, and database choice. SQLite can be acceptable for a small personal setup, but production should use PostgreSQL so writes and backups are predictable. Outbound API calls, webhook ingress, polling intervals, and alert fan-out make network behavior part of the plan; We recommend verifying the latest uplink specs directly on the provider's SLA due to regional variation.
Minimum vs Production vs Scale
| Stage | Source | CPU | RAM | Storage | Interpretation |
|---|---|---|---|---|---|
| Minimum | requirements.minimum |
1 Core | 1 GB | 5 GB | The 1 GB and 1-core floor is enough for personal experiments, a few light schedules, or simple webhook flows. It is not a safe baseline for business automation. |
| Production | requirements.recommended |
2 Cores | 4 GB | 20 GB | The 4 GB and 2-core production tier is the default baseline for a small live n8n deployment with PostgreSQL, execution history, webhooks, and several active workflows. |
| Scale | editorial interpretation |
Add CPU for concurrent data transformations, encryption work, webhook bursts, and multiple worker processes. | Add RAM as workflow count, payload size, execution history, and concurrent runs increase; long workflows keep more data resident. | Move execution state to PostgreSQL, manage retention, and keep backups separate from the application root disk. | At scale, enable Queue Mode: keep the main n8n process focused on the editor and orchestration, use Redis as the queue broker, and run separate workers to process executions horizontally. This changes n8n from one overloaded VPS process into a worker pool where API waits, retries, and long-running workflows stop blocking the whole service. |
Anti-Patterns
- Do not size n8n only by whether the editor opens; workflow executions, database writes, and external API calls are the production workload.
- Do not run many frequent workflows on a tiny single-process setup and expect schedules, webhooks, and retries to stay reliable.
- Do not ignore execution history retention, database backups, credential safety, outbound rate limits, or renewal pricing.
- Do not scale by adding only cheap CPU cores; Queue Mode with separate workers and Redis is the correct architecture step when concurrency grows.
Who It Fits
For: Good fit for users who need self-hosted automation and can budget for the 4 GB production baseline, PostgreSQL, backups, and network reliability for webhooks and outbound API calls.
Not for: Avoid a low-end VPS if workflows run constantly, process large payloads, fan out to many APIs, require reliable webhook latency, or need concurrent business-critical executions.
FAQ
When should n8n use Queue Mode?
Use Queue Mode when concurrent workflows, webhook bursts, retries, or long-running jobs make a single n8n process unreliable. Redis queues work and separate workers process executions.
Is n8n CPU-bound or I/O-bound?
It is Mixed, with an I/O-bound and network-sensitive base. External API calls, database writes, and webhook traffic dominate many setups, while RAM and CPU rise with workflow concurrency and payload size.
What should I check before buying?
Check RAM, PostgreSQL storage behavior, backup options, renewal pricing, outbound API reliability, and webhook latency. If uplink specs are not listed locally, use the provider SLA as the source of truth.
Quality Checks
- Engineering-Check: Yes, the page names the first bottleneck and its failure mode.
- Trade-off-Check: Yes, it states who should avoid an entry-level VPS.
- Renewal-Price-Check: Yes, buyers are warned that low first-term prices can distort VPS selection.
- Keyword-Anchor-Check: Yes, internal anchors on the page use VPS and self-hosting terms instead of generic labels.
- Data-Link-Check: Yes, Minimum and Production values map to
self-hosted-tools.json. - Uniqueness-Check: Yes, the analysis is tied to n8n bottlenecks rather than a name-swap template.
What is n8n?
n8n is a powerful workflow automation platform that connects your apps and services with a visual, node-based interface. It's a self-hosted alternative to Zapier and Make (Integromat) with over 400 built-in integrations including Slack, Google Sheets, GitHub, databases, and APIs. n8n supports complex multi-step workflows with conditional logic, loops, error handling, and data processing. The fair-code license allows free self-hosting while maintaining an active open-source community.
Why Server Specs Matter
n8n's resource requirements scale dramatically with workflow complexity and execution frequency. Simple workflows with occasional triggers need minimal resources. However, workflows processing large datasets, making many HTTP requests, or running frequently can become CPU and memory intensive. Each workflow execution consumes memory for data processing. Long-running workflows with many steps keep connections open and accumulate memory usage. Webhooks require the server to handle incoming requests continuously.
Problems with Undersized Servers
Insufficient resources cause workflow executions to fail or timeout mid-processing. Large data processing operations run out of memory and crash. Webhook endpoints become slow to respond or drop requests. The visual workflow editor becomes laggy with complex automations. Scheduled workflows miss their triggers. Database queries pile up, causing delays across all workflows. Error handling becomes unreliable, making debugging difficult.
Our Recommendation
For simple personal automations, 1GB RAM and 1 CPU core work adequately. Business automations with multiple concurrent workflows should use 2-4GB RAM. Complex data processing workflows may need 4-8GB RAM. CPU becomes important when executing many workflows simultaneously. Use SQLite for simple setups, PostgreSQL for production. Plan 5-20GB storage for workflow data and logs. Consider worker mode for high-throughput scenarios.
Minimum Requirements - VPS Plans
These VPS plans meet the minimum requirements to run n8n. Suitable for testing or light usage.
| Provider | Plan | CPU | RAM | Storage | Features | Price/mo | Actions |
|---|
Recommended Requirements - VPS Plans
For optimal performance, we recommend these VPS plans that exceed the minimum requirements.
| Provider | Plan | CPU | RAM | Storage | Features | Price/mo | Actions |
|---|
Some links on this page are affiliate links. If you make a purchase through these links, we may earn a small commission at no extra cost to you. This helps us keep the site running and provide free comparison tools.