USE CASE SHORTLIST · SELF-HOSTED AUTOMATION
Which VPS should you choose for n8n?
For a US deployment, start by comparing an appropriately sized DigitalOcean Droplet with the full US Hetzner quote. For a European deployment, Hetzner’s CX23 is a reasonable entry candidate when its available resources fit your stack. If nobody can administer the server, compare n8n Cloud before buying a VPS.
This is a focused, official-source shortlist of two providers, not an exhaustive market ranking or hands-on benchmark. We have not purchased or tested these plans. Fit depends on workflow data, concurrency, database, task runners and optional Assistant components.
Quick picks
- Regional choice for US / UK / Canada / Australia: investigate DigitalOcean when an available local region is a requirement.
- European entry candidate: investigate Hetzner CX23 for a compatible workload with an experienced operator.
- No server operator: consider n8n Cloud. Self-hosting transfers maintenance work to you.
Comparison table
| Candidate | Compute / memory | Storage | Compute price | Best fit |
|---|---|---|---|---|
| DigitalOcean Basic Regular bundled | 2 shared vCPU / 4 GiB | 80 GiB SSD | $24/month, before extras and tax | A supported region and cloud tooling |
| Hetzner CX23 · Germany / Finland | 2 shared vCPU / 4 GB | 40 GB | €5.49 or $6.49/month, before IPv4, extras and tax | European entry workload |
The units and CPU families differ. This table cannot establish which runs your workflows faster. Europe pricing must not be applied to Hetzner US locations. For the current US price distinction, read the Hetzner overview.
Size the stack before selecting a plan
The current official Docker Compose guide that includes the Assistant sandbox specifies at least 4 GB RAM and 2 vCPUs. That is a requirement for that documented stack, not a universal minimum for every n8n deployment. Its bundled sandbox is oriented toward local development and testing; follow n8n’s current production sandbox guidance if you enable Assistant.
List n8n, the database, reverse proxy, runners and optional services. Leave headroom for bursts, upgrades and backup operations. Check actual memory pressure during representative runs before reducing the plan. A workflow processing a large payload can exhaust memory even when execution count looks modest.
For higher concurrency, n8n queue mode separates a main instance and workers with Redis and a shared database. Account for those components and their network paths. Queue mode is an architecture decision, not an automatic benefit from purchasing more vCPUs.
DigitalOcean: when regional coverage matters
Choose an available nearby region when your automation interacts with local applications or a region-specific database. DigitalOcean’s documented tooling and adjacent services can help a team that already operates cloud infrastructure.
Pros: relevant regional options, documented APIs, multiple resource families. Cons: paid recovery options and other services increase the bill; you still manage n8n and the host. On the $24 reference plan, percentage-based weekly backups add $4.80. This is not a guarantee that all application data is covered.
It suits an operator who values that ecosystem and accepts its total cost. Read the DigitalOcean overview.
View Current PlansHetzner: when a European entry plan fits
The CX23 candidate is worth considering when your deployment belongs in Germany or Finland and its shared CPU resources suit the workload. Validate image architecture, available stock and the complete configuration before paying.
Pros: an identifiable European entry resource bundle and infrastructure tooling. Cons: geography and regional price differences constrain the recommendation; IPv4 and backups are separate. Do not extrapolate this plan to a local Canadian or Australian deployment.
It suits an experienced operator with a suitable European workload. The side-by-side comparison explains the decision dimensions.
Check Latest PricingBefore production: recovery and operations
- Store credentials and encryption material securely and include them in your recovery design.
- Keep database and persistent data backups; rehearse restoring the application.
- Restrict access, configure HTTPS and assign responsibility for security updates.
- Limit retained execution data to what your operational needs require.
- Test representative workflows and define a resource-upgrade trigger.
Use the cost calculator for compute, backup, IP, storage, transfer and operator costs. See How to Choose a VPS for the broader buying checklist.
FAQ
Can I use the cheapest VPS?
Choose a configuration that fits your actual stack. The current Assistant Compose guide has a specific resource requirement; other deployment modes require their own sizing evidence.
Should I use shared or dedicated CPU?
Shared CPU is a candidate for intermittent work. For sustained execution or tighter predictability requirements, compare dedicated CPU and test your workload.
Is a VPS less work than n8n Cloud?
A VPS gives infrastructure control and adds operating responsibilities. Compare total time and recovery obligations, not only server cost.
Are discounts guaranteed?
No. These buttons currently lead to official provider pages. Verify any offer and eligibility at the provider.
Sources
Checked October 1, 2026 (UTC): n8n current Compose guide; queue mode; memory issues; DigitalOcean prices; DigitalOcean backup prices; Hetzner current prices; CX23 specifications (historical price). Our evaluation policy explains evidence requirements.