/ tool-comparisons / Hetzner vs Cloudflare Pages for Solo Developers
tool-comparisons 10 min read

Hetzner vs Cloudflare Pages for Solo Developers

Comparing Hetzner and Cloudflare Pages for solo developers. Features, pricing, pros and cons, and which one to pick for your next project.

Hero image for Hetzner vs Cloudflare Pages for Solo Developers

Quick Comparison

Feature Hetzner Cloudflare Pages
Type Cloud/VPS provider Static site + edge functions platform
Entry pricing CX22 from about EUR 3.79 to 3.99/mo (2 vCPU, 4 GiB, 40 GB SSD, 20 TB traffic) Free plan, then Workers Paid from $5/mo
Free tier None (servers are paid) 500 builds/mo, unlimited bandwidth, unlimited sites
Network footprint 5 regions (Nuremberg, Falkenstein, Helsinki, Ashburn, Hillsboro) 330+ cities across 125+ countries
Learning Curve Moderate (server admin) Easy (Git-connected)
Best For Full-stack apps on affordable servers Static sites, JAMstack, and edge-rendered apps
Solo Dev Rating 8/10 9/10

Hetzner Overview

Hetzner keeps things simple, with affordable servers, reliable infrastructure, and no frills. Their entry-level CX22 cloud server packs 2 vCPUs (Intel Xeon), 4 GiB RAM, 40 GB SSD, and 20 TB of included traffic for roughly EUR 3.79 to 3.99 per month after the price adjustment that took effect on April 1, 2026. If you prefer ARM, the CAX11 (2 Ampere vCPUs, 4 GB, 40 GB) sits at EUR 4.49 per month, and the AMD-based CPX22 (2 vCPUs, 4 GB, 80 GB) is EUR 7.99. These are real machines in well-maintained data centers across Nuremberg and Falkenstein in Germany, Helsinki in Finland, and Ashburn and Hillsboro in the United States.

You get full root access, pick your OS, and run whatever you want. Django, Rails, Go services, Docker containers, databases, the works. Hetzner doesn't care what you deploy. They care about keeping the hardware running, and they do that very well.

The limitation is clear. Hetzner is infrastructure only. No CDN, no edge functions, no automatic deployments. Every layer above the bare server is your responsibility. For solo developers who know their way around a Linux box, this is freedom. For everyone else, it's a to-do list.

Cloudflare Pages Overview

Cloudflare Pages is a deployment platform for frontend applications and full-stack frameworks that uses Cloudflare's global edge network. Connect your GitHub or GitLab repository, and every push triggers an automatic build and deployment to a network that spans 330+ cities across more than 125 countries. Your site is fast everywhere because it runs everywhere.

The free tier is exceptionally generous, with unlimited bandwidth, 500 builds per month, one concurrent build, up to 100 custom domains, and unlimited sites. There are no surprise bills and no bandwidth caps you will actually hit. For static sites and JAMstack applications, it is legitimately free hosting with global CDN performance. The practical ceilings on the free plan are the file count (20,000 files per site), the per-asset size (25 MiB), and the single concurrent build, which only bites if you push to several projects at once.

Cloudflare Pages also supports server-side rendering through Cloudflare Workers (edge functions). Frameworks like Next.js, Astro, Nuxt, SvelteKit, and Remix can run on the edge with Pages Functions. You get dynamic capabilities without managing a server, though with the constraints of an edge runtime (no native Node.js modules, execution time limits).

Key Differences

Hosting model. Hetzner gives you a single server in one location. Cloudflare Pages distributes your site across 300+ locations globally. For static content and edge-rendered pages, Cloudflare Pages is faster for users everywhere. For server-side applications with database connections, Hetzner's single location with direct database access is simpler.

What you can run. Hetzner runs anything. Python, Ruby, Go, Java, PHP, whatever you want. Cloudflare Pages runs static files and JavaScript/TypeScript edge functions. If your application needs Python backend processing, a PostgreSQL database, or long-running background jobs, Cloudflare Pages can't do it alone. You'd need separate backend hosting.

Operational burden. Cloudflare Pages requires zero server management. No OS updates, no security patches, no SSL configuration, no monitoring. Hetzner requires all of that. For a solo developer, the hours saved on infrastructure management with Cloudflare Pages are hours gained for building features.

Cost analysis. Cloudflare Pages is free for most solo developer use cases. The free plan ships 500 builds per month and genuinely unlimited bandwidth, so a static site never sends you a bill. Hetzner's cheapest cloud server, the CX22, runs about EUR 3.79 to 3.99 per month after the April 2026 price adjustment. The real cost comparison matters when you need a backend too. If you use Cloudflare Pages for your frontend but need a separate database and API server, you might end up spending more total than running everything on one Hetzner VPS. The "Real Cost at Solo-Dev Scale" section below works that math out in numbers.

Preview deployments. Cloudflare Pages automatically creates preview URLs for every pull request. You can share staging links with testers before merging. Hetzner has no built-in preview deployment system. You'd need to set that up yourself.

Build system. Cloudflare Pages builds your project automatically on each push. It supports all major frameworks and custom build commands. With Hetzner, you build and deploy manually or set up your own CI/CD pipeline.

When to Choose Hetzner

  • You need a backend server with databases, queues, and background processing
  • You're running a full-stack application that needs persistent server-side state
  • Your tech stack isn't JavaScript/TypeScript
  • You want all services (app, database, cache) on one machine for simplicity
  • You need long-running processes or WebSocket connections

When to Choose Cloudflare Pages

  • You're building a static site, blog, or documentation site
  • You're using a JAMstack framework (Astro, Next.js, Nuxt, SvelteKit)
  • You want free global CDN hosting with unlimited bandwidth
  • You want automatic Git-connected deployments with preview URLs
  • You don't need server-side databases or background processing

By the Numbers (2026)

Specs and prices drift, so here is the verified state of both platforms as of late May 2026.

Hetzner Cloud (prices reflect the April 1, 2026 adjustment)

  • CX22 (Intel Xeon): 2 vCPUs, 4 GiB RAM, 40 GB SSD, 20 TB included traffic, about EUR 3.79 to 3.99/mo. Sources differ slightly on the exact figure after the adjustment, so budget for the upper end.
  • CAX11 (Ampere ARM): 2 vCPUs, 4 GB RAM, 40 GB SSD, 20 TB traffic, EUR 4.49/mo (up from EUR 3.29 before the adjustment).
  • CPX22 (AMD): 2 vCPUs, 4 GB RAM, 80 GB SSD, EUR 7.99/mo (up from EUR 5.99).
  • Regions: Nuremberg and Falkenstein (Germany), Helsinki (Finland), Ashburn (US East), Hillsboro (US West).
  • There is no free tier. Every Hetzner server is billed, hourly with a monthly cap.

Cloudflare Pages

  • Free plan: 500 builds per month, 1 concurrent build, up to 100 custom domains, 20,000 files per site, 25 MiB max asset size, 20-minute build timeout, and unlimited bandwidth.
  • Paid tier: Pages rides on the Workers Paid plan, which starts at a $5/mo minimum. That lifts you to 5,000 builds per month, 5 concurrent builds, and up to 250 custom domains.
  • Pages Functions are billed as Workers. The free plan covers 100,000 requests per day. Workers Paid includes 10 million requests and 30 million CPU-milliseconds per month before metered overage.
  • Network: 330+ cities across more than 125 countries.
  • Bandwidth is uncapped on every tier, which is the headline reason solo developers reach for it.

Neither product is open source, so there are no GitHub stars or npm download counts to report. These are both hosted services rather than packages you install.

Real Cost at Solo-Dev Scale

Here is a concrete workload, the kind a solo developer actually ships, costed with the real per-unit rates above.

Assume a small SaaS side project: a marketing site plus app frontend on Cloudflare Pages, a Postgres database, a small API, a background worker, and a Redis cache. Traffic is modest, say a few hundred thousand requests a month, well inside everyone's free allowances.

Option A, all on Hetzner. Run the frontend, API, worker, database, and Redis on a single CX22 at roughly EUR 3.79 to 3.99 per month. Everything talks over localhost, the database has direct access with no egress fees, and 20 TB of included traffic means bandwidth is a non-issue at this scale. Total: about EUR 4 per month, one machine to patch.

Option B, split stack. Frontend on Cloudflare Pages (free, since you are nowhere near 500 builds or the file ceiling), API and worker as Pages Functions on Workers (free up to 100,000 requests per day, which a few hundred thousand requests a month sits comfortably under), and the database plus Redis still need a home. Cloudflare has D1 and KV, but a standard Postgres still wants a server, so you put it on the same CX22 for about EUR 4 per month. Total: still about EUR 4 per month, but now spread across two providers and two deploy stories.

The honest read. At true solo-dev scale, the monthly cost is nearly identical, roughly EUR 4 either way, because the Cloudflare half is free and the database forces a server regardless. The decision is not about dollars at this size. It is about operational shape. Hetzner gives you one box and one bill, which is the lowest cognitive overhead until the day you need global edge latency. The split stack gives you instant worldwide frontend delivery and zero-maintenance preview deployments, at the cost of juggling two control planes.

Cost only diverges later. If your frontend ever serves serious bandwidth, Cloudflare's uncapped free egress saves you real money against a VPS where heavy outbound traffic could push you past the 20 TB allowance. If your backend grows into multiple services or larger databases, a single bigger Hetzner box (CX33 at EUR 6.49, or vertical jumps from there) stays far cheaper than stitching together managed equivalents. Pick the shape that matches where the project is heading, not the cent difference today.

The Verdict

For static sites, blogs, marketing pages, and frontend applications, Cloudflare Pages is the obvious winner. Free hosting, global CDN, automatic deployments, and zero maintenance. There is no reason to manage a Hetzner server for a static site.

For full-stack applications that need databases, background processing, or non-JavaScript backends, Hetzner is the better foundation. You can run your entire stack on one server at a predictable low cost.

The smart move for many solo developers is to use both. Put your frontend on Cloudflare Pages for free global distribution, and run your API and database on a Hetzner VPS. Your frontend loads instantly from the nearest edge location, your API runs on affordable infrastructure, and your total monthly cost stays around EUR 4. That combination is hard to argue against.

Sources

All figures checked on 2026-05-28.

Built by Kevin

Like this? You'll like what I'm building too.

Two ways to support and get more of this work.

Desktop App

HEARTH

A privacy-first Life OS for your desktop. Journal, tasks, and notes that stay on your machine. Coming soon, direct download from this site.

Read more
Digital Products

MY TOOLKITS

Receipts-first toolkits for shipping after hours, building Claude agents, publishing on Amazon, and more. The exact methods I used, not theory.

Browse on Whop

Need This Built?

Kevin builds products solo, from first version to live. If you want something like this made, work with him.