Contabo vs Hetzner for a Small Automation VPS

What the automation box actually needs

I would write down six requirements before comparing plan cards:

• Always-on or intermittent. A webhook receiver that must answer at 3 a.m. is an always-on purchase. A one-off migration job is an hourly purchase.
• Region. The webhook sender and the people waiting for the result both care about network distance.
• RAM and disk. n8n is modest, but binary data, execution history, Docker images, and a database grow.
• CPU. Most webhook work waits on APIs; image, video, and PDF work can make CPU the limit.
• Port and transfer. Media jobs and large payloads care about the pipe.
• Recovery. Snapshots, backups, and the ability to rebuild the box matter more than a benchmark.

Those requirements are the same on both providers. The difference is how each one prices and delivers them.

The comparison, with its limits

The Contabo column uses the listed Cloud VPS 4 shape. The Hetzner column uses the public starting-price bands, not a matched plan. I am not pretending the two columns are the same server; the point is the buying model and the visible price shape.

*Contabo's page uses "unlimited traffic" with a port speed and fair-use terms. Read the current terms.

The Hetzner figures are starting prices for categories, not a quote for a specific plan. The page describes cost-optimized shared plans from €5.99/month excl. VAT, regular-performance shared plans from €5.49/month excl. VAT, and general-purpose dedicated-vCPU plans from €36.99/month excl. VAT. A real comparison needs the configurator's exact plan, RAM, disk, port, and term.

Where Contabo wins

RAM and disk per euro. Cloud VPS 4 gives 8 GB and 100 GB SSD at a 24-month price below many entry cloud plans, before VAT. For a single always-on n8n box with a database and a few containers, that headroom is useful.

A predictable bill within the term. If the workload is stable and the term fits, the Contabo term price is easy to budget. The catch is the term: the low figure is for the first 24 months, and the renewal or monthly price can differ.

A larger box for media work. Contabo's higher Core and Performance plans scale RAM and disk aggressively. A media pipeline that needs local scratch space may fit Contabo's shape better than a small entry cloud plan.

Where Hetzner wins

Hourly billing and a short commitment. A migration, a campaign, or a test that runs for a week is a poor fit for a 24-month term price. Hetzner's cloud model lets the box disappear when the job ends.

A cloud control plane and API. If the automation creates and destroys servers, Hetzner's cloud API and provisioning model are built for that. Contabo has an API and CLI, but its center of gravity is the bundled VPS.

European cloud positioning. Hetzner markets its cloud with European data-sovereignty language. If that is a requirement, it belongs in the decision even when the plan card is not the cheapest.

A broader entry range. The Hetzner page exposes several categories, from cost-optimized shared to dedicated-vCPU general purpose. The exact fit still needs the configurator.

The hidden lines

The plan card is not the bill. On Contabo, I would check the term, the setup fee on a monthly Cloud VPS 4 order, VAT, the renewal price, snapshots, Auto Backup, and any extra IP or storage. On Hetzner, I would check the plan's traffic allowance, backups and snapshots, IPv4/IPv6, the hourly rate, and the location.

The currencies and tax treatment differ. A €4.40 Contabo 24-month price, excluding VAT, and a €5.49 Hetzner starting price, excluding VAT, are not directly comparable without a plan and term assumption. I would compare each provider in its own checkout currency and keep the assumptions in the note.

What I would choose for three cases

An always-on single-region n8n box. Contabo Cloud VPS 4 is the first candidate. The 8 GB RAM and 100 GB disk give room for n8n, a small database, and Docker images. I would use external object storage for binary data, keep one snapshot, and add an off-server backup. If the box is media-heavy, I would compare Cloud VPS Plus 4 for the NVMe and 500 Mbit/s port.

A short campaign or a migration. Hetzner's hourly model is the better shape. The job has an end date; paying for a 24-month bundle is the wrong contract.

A multi-region webhook receiver. Hetzner's cloud model and location list are the more natural starting point. Contabo can host the central worker, but I would not force a single-region box to serve a global webhook path without measuring the latency.

What I would measure before choosing

I would run a representative workflow on the candidate box and record:

• Webhook response time from the real sender region.
• Time to first byte and total time for the workflow's own API calls.
• Peak RAM, disk wait, and port throughput during a media job.
• Queue wait at the expected concurrency.
• The first-year cart total, including setup, tax, backups, and renewal.

A plan card cannot answer those. The measurement decides whether the cheap bundle is enough or the flexible cloud is worth the premium.

What the first month looks like

A provider comparison is not an operations plan. For the first month on either box, I would use the same routine:

• Provisioning: a documented image, SSH keys, a non-root user, and a firewall. The provider's console is not the app's security boundary.
• DNS and TLS: a hostname, a certificate, a renewal path, and a rollback record. The Contabo setup guide covers the Contabo side; the Hetzner configurator covers the Hetzner side.
• Snapshots and backups: one pre-change snapshot, one scheduled off-server copy, and one restore test. A snapshot on the same provider is not an off-site backup.
• Monitoring: uptime, disk, memory, and failed executions. The automation should fail loudly.
• Transfer: a weekly read of the bandwidth graph. A media workflow can use a monthly allowance faster than a text workflow.
• Cost: the first invoice compared with the cart, including tax and add-ons.

The first month is when I would learn whether the box is overprovisioned. If CPU stays below the plan's headroom and disk is stable, a smaller renewal may be the better buy. If the box is already near a limit, the next plan is a measured decision.

The configurator steps I would record

Because the Hetzner public page shows starting-price bands rather than a clean plan-name/spec table, I would not compare a Contabo plan with a Hetzner "from" price. I would open both configurators on the same day and record:

• The exact plan name, vCPU, RAM, disk, and port.
• The monthly and hourly price in the same currency, with or without tax.
• The traffic allowance, backup and snapshot charges, and IPv4/IPv6 treatment.
• The term, notice period, and renewal price.
• The location I would actually use, not the cheapest location on the page.
• The migration and exit path, including data transfer and DNS.

That record is the comparison. A starting price without the plan shape is a headline, not a matched quote.

When neither is the right answer

A small automation box is not always a VPS purchase. If the workflow is a few scheduled API calls, a serverless function or a managed automation platform may be cheaper than maintaining an operating system, a reverse proxy, TLS, and backups. If the workload is a single webhook, a small managed container or a platform's built-in scheduler may be enough.

The VPS route fits when the workflow needs a persistent process, local files, Docker, a database, or control over the network and the OS. It fits less well when the team does not want to patch a server or when the job can run inside a managed platform. The provider comparison only matters after that route decision.

What a matched comparison would need

The public Hetzner page exposes category starting prices, not a plan-name/spec pairing. I would not treat €5.49–5.99/month as the price of a specific plan, and I would not compare it with Contabo's Cloud VPS 4 as if the two were matched. A matched comparison needs the exact Hetzner plan name, vCPU, RAM, disk, port, term, VAT treatment, and renewal, read from the configurator on the same day as the Contabo cart.

This article is therefore a buying-model comparison, not a matched-cost or performance comparison. Contabo's 8 GB and 100 GB at the entry price may be the better shape for a single n8n box; Hetzner's hourly model and cloud control plane may be the better shape for a job that moves. The plan shape and term still have to match the job, and the configurator is where that comparison is finished.

What this does not decide

This article does not benchmark Contabo or Hetzner, does not measure network latency, and does not pair a specific Hetzner plan with the Contabo plan. It gives the buying-model comparison and the lines to verify. For a matched spec comparison, read both configurators on the same day.

Sources

• Contabo Core VPS plans: https://contabo.com/en/vps/
• Contabo Performance VPS plans: https://contabo.com/en-us/vps-performance
• Hetzner Cloud: https://www.hetzner.com/cloud/
• AiXVPS Contabo review: /providers/contabo/
• AiXVPS Contabo automation: /providers/contabo/ai-automation/
• AiXVPS n8n VPS hub: /use-cases/n8n-vps/