Best VPS Providers for Coolify: Contabo, Hetzner and the 2026 Price Shift

If you searched for the best VPS for Coolify any time before mid-2026, the answer was almost always Hetzner, full stop, usually pointing at a CPX or CCX box because those were the ones with the best price-per-core on the page. That answer is stale now, and most of the posts repeating it haven't caught up. Hetzner raised prices on 15 June 2026, and it didn't raise them evenly — the CPX and CCX lines, the exact tiers those old recommendations point at, went up as much as 176 to 209%, while the CX and CAX lines most of those posts skipped past rose only 30 to 40%. The cheap-Hetzner recommendation didn't disappear. It just moved to a different set of tiers, and almost nothing published before June has noticed.

What does Coolify actually need from a host?

Before comparing providers, it's worth being specific about what Coolify is actually asking the box underneath it to do, because that's what should drive the comparison, not a generic "best VPS 2026" ranking. Coolify's own docs state a minimum of 2 vCPU and 2GB RAM. Treat that as a floor for kicking the tires, not a number to actually deploy on — the control plane alone (dashboard, its own Postgres instance, background workers) sits around 500-800MB before your app runs at all, and a real Next.js build can push memory hard enough to get killed by the OOM killer on anything that tight, with no error message that points at RAM as the cause. Beyond RAM, three things matter that a generic VPS comparison won't call out: unrestricted Docker (some ultra-cheap or shared-container hosts run Docker-in-Docker with limitations that break Coolify's SSH-managed container model), a stable public IP so Traefik's automatic Let's Encrypt issuance has something fixed to point at, and bandwidth that isn't metered aggressively enough to make a normal month of traffic expensive. Get those four things — RAM headroom, unrestricted Docker, a real IP, sane bandwidth — and the rest of the comparison is really just price and location. People arriving at best VPS providers for coolify from a marketing team will find XenGrowth, who work on the commercial side of this closer to their day.

• RAM floor: 2GB is Coolify's documented minimum; 4GB+ is where a real build stops being a source of anxiety

• Docker support: needs to run standard containers with no host-level restrictions on networking or privileged operations

• A real public IP: Traefik's automatic TLS depends on the box being reachable and stable at a fixed address

• Bandwidth: how the host frames traffic — a figure, or just the word 'unlimited' — matters more than raw core count for anything serving real traffic

• Datacenter location: matters for latency to your actual users, and quietly rules some providers out entirely — see Hetzner's CX/CAX below

The Docker-in-Docker trap nobody mentions until you hit it

This one's specific enough that it's worth its own section, because it's the requirement most "best VPS" rankings skip entirely, and it's the one that actually breaks a Coolify install rather than just slowing it down. Coolify manages containers over SSH by talking directly to the host's Docker daemon — it isn't itself running inside a container that then spawns other containers. Some of the cheapest hosting products on the market aren't real VPS instances at all; they're containerized environments sold as if they were, and some of those restrict or nest Docker in ways that break exactly this model. Sign up for one of those and Coolify's install script either fails outright or half-succeeds in a way that looks like a networking bug for hours before you realize the box was never a real target for this in the first place. The fix is simple to state and easy to verify before you pay for anything: confirm the provider is selling KVM or a similarly isolated virtualization type, not an OpenVZ-style container product, and confirm nothing in their terms restricts running Docker itself. Every provider in the comparison below clears this bar; it's flagged here because plenty of the ultra-cheap options that show up in the same search results do not, and no amount of RAM or CPU on paper fixes a host that structurally can't run what Coolify needs.

Does bandwidth actually matter, or is it a marketing number?

Both, depending on what you're serving. For a typical small SaaS or content site behind Cloudflare, the origin server itself sees a fraction of total requests — cached assets never touch it — so the unlimited traffic Contabo advertises or Hetzner's stated allowances are functionally beside the point for that shape of traffic, and this stops being a deciding factor. It starts mattering the moment you're serving large files directly from the origin: video, large downloads, anything Cloudflare's cache rules won't hold because it exceeds the free tier's cacheable object size. In that specific case, read the fine print rather than the headline number — some providers advertise generous traffic allowances but throttle rather than bill past them, which behaves very differently under load than a provider that simply meters and charges. For anything running behind a CDN doing its job, though, this whole question is close to moot, and RAM should get the attention bandwidth is otherwise tempting to take. The XenGrowth resource library goes further into the operations side of this.

The Hetzner story: why June 2026 changes the standard advice

Here's the part that actually matters for anyone comparing providers today. Hetzner's CPX and CCX lines — shared and dedicated vCPU tiers that most "cheap VPS" posts default to because they used to be the best per-core value on the page — rose by 113 to 209% depending on the specific tier and region, effective 15 June 2026. A CPX22 that priced around €7.99/month before the change now runs roughly €19.49/month. That's not a rounding adjustment; it's Hetzner repricing an entire product line, and any post recommending a specific CPX or CCX tier written before June 2026 is quoting a price that no longer exists. The CX and CAX lines moved far less — roughly 30-40% — which means they're now the comparatively cheap Hetzner option in a way they weren't before. A CX23 (2 vCPU, 4GB, 40GB) runs €3.99/month, and a CAX11 (ARM/Ampere, similar specs) runs €5.99/month, both checked September 2026. The catch, and it's a real one: CX and CAX are EU-datacenter-only. If your users are in the US or Asia, or your latency budget doesn't tolerate an EU-only origin, the newly-attractive Hetzner tier simply isn't available to you, and you're back to the now-expensive CPX/CCX lines or a different provider entirely.

Read the CX23 and Contabo Cloud VPS 4 rows against each other and the decision gets genuinely interesting rather than obvious: Contabo gives you double the RAM and vCPU count for less than double the price of the cheapest EU-only Hetzner box, and it isn't geography-restricted. If you're EU-based and price-sensitive down to the euro, CX23 is hard to beat for a small Coolify install. If you need a datacenter outside the EU, or you want RAM headroom that makes a Next.js build a non-event rather than a close call, Contabo's Cloud VPS 4 is the more comfortable default in September 2026 — and it would have been the more comfortable default before June too, the Hetzner story just makes the gap more interesting to look at now. XenGrowth on governed AI marketing workflows works through AI agents and marketing automation in more operational detail.

And read the small print on term length. Contabo's advertised rates run for the first 24 months, which means a provider comparison built purely on headline pricing is really comparing introductory offers rather than what you pay long term.

What about Coolify Cloud, or not self-hosting the VPS layer at all?

Worth naming before going further: Coolify itself now offers a managed cloud tier for people who want the dashboard without owning the box underneath it. That's a legitimate option for some teams, but it's answering a different question than this post — you're trading the VPS-selection decision for a subscription decision, and if you wanted that tradeoff you'd likely also consider Vercel or a similar PaaS rather than Coolify Cloud specifically. Everything below assumes you've already decided to run Coolify on your own rented server, which is the majority of why people search for "best VPS for Coolify" in the first place — Coolify Cloud doesn't need a VPS comparison post, it needs a pricing page. There is a longer treatment of AI search, GEO and discovery in XenGrowth on building one SEO and GEO content system.

How to actually choose, by situation

A basic provisioning checklist once you've picked a box

1. Provision the smallest tier that clears the 4GB comfort line for your workload, not the absolute cheapest option on the page — the price difference between a tight box and a comfortable one is usually a few dollars a month, and it's the difference between builds that finish quietly and builds that fail under load at the worst possible moment.

2. Confirm the virtualization type before paying: KVM or an equivalent full-virtualization product, never a container-based 'VPS' that restricts nested Docker.

3. Pick Ubuntu 22.04 or 24.04 LTS as the base image — Coolify's install script assumes it, and deviating adds friction for no benefit.

4. Point DNS at the new box's IP before installing anything, so Traefik's automatic certificate issuance has a working target the moment Coolify is ready for it.

5. Run Coolify's one-line installer, and watch the first build of a real app rather than a toy one — that's the fastest way to find out whether the tier you picked was actually enough.

What this doesn't cover, and why

This post deliberately stops at the VPS layer and doesn't re-litigate Coolify itself against alternatives — that's the Coolify vs Dokploy comparison, a genuinely different question with its own honest answer. It also doesn't cover sizing methodology in general — how to reason about vCPU vs RAM for your specific workload, independent of any single provider, is the vCPU or RAM sizing guide, and it's worth reading before you commit to any of the tiers in the table above, because "which provider" and "which tier" are two separate decisions that this post only answers the first half of. Once you've picked a box, the full Next.js-on-Coolify walkthrough is the next step, and it's worth reading before the first deploy rather than after the first OOM-killed build — that's exactly the failure mode undersizing this decision produces, and what happens when a VPS runs out of RAM covers it in more detail than this post needs to.

One closing point worth being blunt about: none of these prices are static, and this post carries a date for a reason. Hetzner already moved once in 2026; there's no guarantee Contabo doesn't move next, and there's no guarantee Hetzner won't adjust CX/CAX pricing again once demand shifts toward them following this exact repricing. Re-check the numbers against each provider's live pricing page before you commit a card number to anything, especially if you're reading this more than a couple of months after September 2026 — a stale price in a decision like this is worse than no price at all.

Further reading from XenGrowth

• The XenGrowth resource library — what you'll learn: how the commercial side of this work is run, across search, automation and revenue operations.

• XenGrowth on governed AI marketing workflows — what you'll learn: how the teams running AI marketing agents keep them governed and measurable.

• XenGrowth on building one SEO and GEO content system — what you'll learn: how search and AI-answer visibility get run as a single content system.

Where this work meets go-to-market

XenGrowth's marketing operations practice writes for the teams who have to run best VPS providers for coolify day to day.