Best VPS for n8n: How to Pick a Server for Self-Hosting

The top pick for self-hosting n8n is a Hetzner CX22 (or the newer CX22 Gen2) because it offers the best balance of performance, RAM, and price for typical n8n workflows. With 2 vCPU, 4GB RAM, and 40GB NVMe storage, it comfortably runs n8n plus a small database and a few integrations—and it costs only a few dollars per month. For most users, this is the sweet spot where you don’t pay for unused power but have enough headroom for real automation.

What to Look For

Before comparing providers, focus on these five criteria—they matter more than brand names or flashy features:

• RAM (most important): n8n itself is a Node.js app that typically uses 300–600MB idle. But your workflows, the queue mode, and any connected databases (PostgreSQL, Redis) add up. For light use, 2GB is the absolute minimum; 4GB is comfortable; 8GB is for heavy workflows or multiple users.
• CPU: n8n is mostly I/O-bound, not CPU-heavy. A single modern vCPU is fine for most automations. Two vCPUs help when you run parallel executions or use the queue mode with Redis.
• Storage (SSD/NVMe required): n8n writes logs and execution data constantly. A spinning HDD will slow things down and cause timeouts. Always choose NVMe or at least SSD. 20–40GB is enough for most setups.
• Network speed and location: If your workflows call external APIs (Google, Slack, Stripe), latency matters less than bandwidth. But if you’re in Europe and your server is in the US, you’ll feel the difference. Choose a region close to your main services.
• Managed vs unmanaged: You can run n8n on a cheap unmanaged VPS, but you’ll handle OS updates, security patches, and backups yourself. Managed options (like Railway or Render) cost more but remove that overhead.

Hetzner CX22

Strengths: Excellent price-to-performance. The CX22 offers 2 vCPU, 4GB RAM, 40GB NVMe, and 20TB traffic for around €4–5/month. Hetzner’s network is fast and reliable, and their control panel is simple. You can easily snapshot your server for backups.

Trade-offs: Unmanaged—you must configure everything yourself (Ubuntu, Docker, firewall, SSL). Support is ticket-based and not instant. No built-in n8n one-click install, though a simple Docker Compose file works fine.

Who it suits: Anyone comfortable with basic Linux commands and Docker. If you want the lowest cost for a serious n8n instance, this is it.

DigitalOcean Droplet (Basic 4GB)

Strengths: The 4GB/2vCPU/60GB SSD droplet is a reliable middle ground. DigitalOcean has a huge community tutorial library, including a specific guide for n8n. Their UI is beginner-friendly, and you get a floating IP for easy failover. Uptime is excellent.

Trade-offs: Costs more than Hetzner (around $24/month for 4GB). Bandwidth is capped at 4TB. The control panel is nice but not worth the premium for everyone.

Who it suits: Users who want a well-documented path and don’t mind paying a bit more for polish. Good if you plan to scale to multiple droplets later.

Railway (Managed)

Strengths: Railway offers a one-click n8n template. You get automatic HTTPS, simple scaling, and you don’t manage the OS. It’s great for non-technical users who just want n8n running. You can also add a PostgreSQL database with one click.

Trade-offs: Pricing is usage-based and can surprise you. A hobby project might cost $5–10/month, but heavy workflows with lots of executions can push that higher. You have less control over the underlying environment.

Who it suits: If you’re new to self-hosting and want to avoid SSH and Docker, Railway is the fastest way to get n8n live.

Contabo VPS M

Strengths: Contabo offers huge specs for the price—often 4 vCPU, 8GB RAM, and 200GB SSD for around €6–8/month. That’s more RAM than Hetzner at a similar cost. They also have data centers in the US and Europe.

Trade-offs: Performance can be inconsistent; the network is sometimes oversubscribed. Customer support is slower. Setup is unmanaged, and you may need to tune the server yourself.

Who it suits: If you run many workflows or want to run n8n alongside other apps (like a database and a small web server) without paying for a bigger provider.

Oracle Cloud Free Tier (VM.Standard.E2.1.Micro)

Strengths: Free forever—1GB RAM, 1 OCPU, and 10GB storage. That’s enough for a small n8n instance with a few workflows. Oracle’s free tier is genuinely free, no time limit.

Trade-offs: Only 1GB RAM, which n8n will outgrow quickly. Setup is more complex (requires creating an Oracle Cloud account and configuring network rules). Oracle may reclaim idle instances.

Who it suits: Hobbyists who want to experiment with n8n at zero cost and are okay with limited resources.

How to Choose

Budget: If you’re spending under $10/month, Hetzner or Contabo are your best bets. If you want $0, Oracle free tier works for testing. For $20–30, DigitalOcean gives you more hand-holding.

Use case: For a personal automation server with a few daily workflows, 2–4GB RAM is plenty. If you’re building a business-critical system with many scheduled workflows and multiple users, go with 8GB and consider Redis for queue mode—that pushes you toward Contabo or a larger Hetzner instance.

Technical comfort: If you know Docker and Linux, unmanaged VPSes save money. If you’d rather not touch a terminal, Railway or a similar PaaS is worth the premium.

Common trade-off: The biggest mistake is over-provisioning. n8n doesn’t need a lot of CPU. RAM is the limiting factor. Start with 4GB, monitor usage with htop, and upgrade only if you see memory pressure.

Location: Choose a server in the same region as your main API endpoints. For example, if you use European services like Stripe EU or Google Workspace EU, pick a European data center.

Frequently Asked Questions

Can I run n8n on a 1GB RAM VPS?

Yes, but only for very light use. n8n itself uses ~300MB, but workflows with many nodes or large payloads will hit memory limits. You’ll also need to disable execution data storage or prune logs regularly.

Do I need a database for n8n?

n8n uses SQLite by default, which is fine for single-instance setups. For production, PostgreSQL is recommended—it handles concurrent writes better. You can run PostgreSQL on the same VPS if you have 4GB RAM.

Should I use Docker or a native install?

Docker is the easiest way to manage n8n and its dependencies. A simple docker-compose.yml with n8n and PostgreSQL is standard. Native installs are possible but more work to update.

How do I secure my n8n instance?

Put it behind a reverse proxy (Caddy or Nginx) with HTTPS. Set a strong N8N_BASIC_AUTH_ACTIVE=true and a long password. Restrict access by IP if you’re the only user.

What about backups?

Back up your n8n database (SQLite file or PostgreSQL dump) and your .env file. Most VPS providers offer snapshot backups—enable them if you can afford a few cents per GB.

Can I migrate my n8n instance later?

Yes, n8n stores workflows in the database. You can export workflows as JSON files and import them into a new instance. For full migration, back up the entire database and restore it on the new server.

Bottom Line

Start with a Hetzner CX22 if you’re comfortable with the command line—it’s the best value for a reliable n8n server. If you want zero setup hassle and don’t mind a variable bill, use Railway with its one-click template. For a middle ground with good documentation, DigitalOcean is a safe choice. Avoid under-provisioning RAM; 4GB is the sweet spot for most users. Whatever you pick, set up backups and HTTPS from day one—then build your automations without worrying about the server.

Related

• EA Account After Game Shutdown: DLC & Achievements
• Team Goals to Company Strategy: Alignment Guide
• MM2 Aim Trainer 2 Halloween Schedule & Events