Running n8n means keeping a workflow service available for webhooks and scheduled jobs, with persistent storage for credentials and execution history. This page requires 2 vCPU, 4 GB RAM and root/SSH access, then ranks eligible plans by long-term cost, deployment features, network quality, reliability and support so you can weigh the hosting bill against the work of operating it.

OVHcloud combines an average $5.08 monthly cost with root access and managed database options for separating workflow storage from your server.
Plan: VPS-1 (2027)Hostinger suits a self-managed n8n deployment with root access and chat support, provided you handle the database yourself.
Plan: KVM 2Akamai Cloud offers managed databases and ticket, email, phone and chat support, giving your team several ways to raise infrastructure issues.
Plan: Linode 4 GBVultr pairs root access with managed database options, with ticket and email support for infrastructure questions.
Plan: vc2-2c-4gbContabo keeps the average hosting bill at $4.93 monthly while giving you root access to operate your n8n stack.
Plan: Cloud VPS 4DigitalOcean offers managed databases alongside root-access servers, with ticket and chat support for teams that prefer written troubleshooting.
Plan: Basic Regular 4 GiBHetzner suits teams comfortable managing their own database, with root access and ticket, email and phone support for hosting issues.
Plan: CPX22Providers change prices often, and we regularly verify prices against their own pricing pages, though small differences from current prices are possible. Prices checked 27 Sept 2026. Ranking uses US dollars at a fixed exchange rate; see the methodology.
Treat 2 vCPU and 4 GB RAM as this ranking’s entry requirement, then size for your workflows. Concurrent executions, large JSON payloads, file processing and Code nodes can raise memory use. Data transformations and overlapping jobs consume CPU, while a database on the same server also needs resources. Watch memory pressure, swap activity, CPU saturation and execution delays during busy periods. Move up a plan when normal workloads repeatedly exhaust available capacity. Before upgrading, check whether smaller batches, reduced concurrency or execution-history pruning would address the bottleneck.
Only if the plan supports a persistent application process, the required runtime and adequate control over storage and networking. SSH access alone does not establish that, so a VPS with root access is the clearer fit for a self-managed deployment.
This ranking requires 4 GB RAM, which is a selection threshold rather than a guarantee for every workload. Your memory needs depend on concurrent executions, payload sizes and whether the database shares the server.
No, you can operate the database yourself. A managed database can reduce database administration work, but check compatibility, connection requirements, backup coverage and additional charges before choosing it.
Back up the database, encryption key, deployment configuration and any persistent files your workflows depend on. Keep a recoverable copy away from the server and test restoration, since database contents alone cannot recover encrypted credentials without the matching key.
Ranked with each host's cheapest plan that meets the minimum above, weighted for this job. How we score hosting.
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.