Cloudflare Pages vs Netlify
Cloudflare Pages vs Netlify compared for European indie developers and small startups. Pricing, EU jurisdiction, GDPR posture, and why Runsite (an EU-registered PaaS in Frankfurt) is worth a look.
Cloudflare Pages vs Netlify: quick answer
Cloudflare Pages and Netlify both offer Git-push deploy workflows, but they differ where it counts. Cloudflare Pages and Netlify are both US-headquartered, so neither escapes US jurisdiction or the CLOUD Act, and neither runs EU-native infrastructure or offers hard spending caps. For European teams that need GDPR-compliant hosting in Frankfurt with predictable EUR billing and a permanent free tier, Runsite is the EU-native alternative to both.
// cloudflare pages problems → runsite solutions
Common Cloudflare Pages frustrations. Sound familiar?
Every Cloudflare Pages frustration, solved.
Cloudflare Pages problem
"Pages Functions can't run my backend"
Cloudflare's edge functions have CPU time limits and no native Node.js modules. Complex backends don't fit.
Runsite solution
Full Docker containers
Run any framework in persistent containers. No CPU time limits, no V8 isolate restrictions.
Cloudflare Pages problem
"I need PostgreSQL, not D1"
Cloudflare's D1 is SQLite-based with size limits. Production apps need a real relational database.
Runsite solution
Managed PostgreSQL from €5/mo
Standard PostgreSQL with auto-backups, point-in-time recovery, and no vendor lock-in.
Cloudflare Pages problem
"Cloudflare is a US company"
Even with EU data centers, Cloudflare is subject to US jurisdiction and the CLOUD Act.
Runsite solution
EU entity, full sovereignty
Runsite is registered in the EU. Your data is governed by European law with no US jurisdictional exposure.
// comparison
Runsite vs Cloudflare Pages
Side-by-side. No marketing fluff, just facts.
| Feature | Runsite | Cloudflare Pages |
|---|---|---|
| Backend Hosting | ✓ Full containers, any stack | Edge Functions only (V8 isolates) |
| Docker Support | ✓ Any Dockerfile | ✗ Not supported |
| Managed PostgreSQL | ✓ From €5/mo | ✗ Not available (use D1/KV) |
| Long-Running Processes | ✓ Persistent containers | ✗ Edge functions have CPU time limits |
| GDPR Compliance | ✓ EU entity | ✗ US company (San Francisco) |
| Static Site Hosting | Via S3 + CDN | ✓ Unlimited bandwidth, global CDN |
| Bandwidth Cost | Included in plan | ✓ Free, unlimited |
| Edge Network | EU-focused | ✓ 300+ global PoPs |
// the other side
What about Netlify?
Netlify excels at static sites. Runsite handles everything else: backend, databases, and full-stack apps on EU servers.
// netlify problems → runsite solutions
Common Netlify frustrations. Sound familiar?
Every Netlify frustration, solved.
Netlify problem
"Netlify can't host my backend"
Netlify Functions are limited to 10-second execution. Long-running APIs need a separate hosting provider.
Runsite solution
Persistent containers for any backend
Run long-lived processes, WebSocket servers, background workers: anything Docker can run.
Netlify problem
"No managed databases"
Netlify doesn't offer databases. You need PlanetScale, Supabase, or AWS RDS on top.
Runsite solution
PostgreSQL + Redis included
Managed databases on the same platform. One bill, one dashboard, one support channel.
Netlify problem
"Compute runs in the US"
Netlify Functions run in US regions by default. EU users get higher latency.
Runsite solution
EU-only compute and storage
Everything runs in our Frankfurt (eu-central) region. Sub-20ms for users in DACH and Benelux, single-digit ms within Germany.
// comparison
Runsite vs Netlify
Side-by-side. No marketing fluff, just facts.
| Feature | Runsite | Netlify |
|---|---|---|
| Backend Hosting | ✓ Full containers, any stack | Serverless functions only |
| EU Data Centers | ✓ Frankfurt (eu-central) | ✗ CDN edge only |
| GDPR Compliance | ✓ EU entity, full compliance | ✗ US company |
| Docker Support | ✓ Any Dockerfile | ✗ Not supported |
| Managed Database | ✓ PostgreSQL from €5/mo | ✗ Not available |
| Static Hosting | Via S3 + CDN | ✓ Excellent |
| Free Tier | ✓ Permanent | ✓ Generous for static |
// in-depth comparison
How Cloudflare Pages and Netlify each compare to Runsite
Cloudflare Pages vs Runsite
You reached for Cloudflare Pages because it is one of the fastest static site hosts around, riding Cloudflare's 300+ point-of-presence global network. The free tier is genuinely generous with unlimited bandwidth, and Pages Functions, powered by Cloudflare Workers, push server-side logic to the edge with impressive cold-start performance. For a static site or a lightweight API, you made a good call.
The friction shows up the moment you go full-stack. Pages Functions run in V8 isolates with CPU time limits and no native Node.js module support, so a complex backend simply does not fit. Your storage is capped to D1 (SQLite-based, with size limits) and KV (eventually consistent key-value). And because Cloudflare is a US company subject to the CLOUD Act, EU data centers exist but you do not control where compute runs.
If you now need persistent server-side processes, a real relational database, or guaranteed EU data residency from an EU entity, Runsite runs full Docker containers with managed PostgreSQL in EU-only data centers under EU legal jurisdiction, covering what the edge-first model leaves out.
Netlify vs Runsite
Your side project began as a static Astro site, then someone asked for a contact form, and now you need a backend. That is where many teams hit the edge of what Netlify does well. Netlify essentially created the Jamstack deployment category, and for static sites, SPAs, and projects built with Gatsby, Hugo, or Astro, its build pipeline and global CDN are excellent. The free tier for static hosting is genuinely generous, and deploy previews and split testing are well-implemented.
Backends are the sore spot. Netlify Functions are serverless with a 10-second execution limit, there are no managed databases, and compute runs on US-based infrastructure. Grow past static content and you stitch together Netlify for frontend, a separate provider for your API, and another for your database. Runsite hosts full-stack applications on one platform: Docker containers for any backend, managed PostgreSQL, and S3 storage, all in EU data centers.
If your project has outgrown Jamstack constraints and you want one platform for frontend, backend, and database with GDPR compliance built in, Runsite consolidates what would be three separate services.
// why consider runsite
Beyond Cloudflare Pages and Netlify
EU PaaS for indie developers and small European startups. One region: Frankfurt.
EU-First Infrastructure
While Cloudflare Pages and Netlify default to US markets, Runsite is built exclusively for European developers. Frankfurt (eu-central) region, EU entity, EU jurisdiction, with no transatlantic transfers.
Real GDPR Compliance
EU-registered entity. Your data is governed by European law. No US jurisdiction, no CLOUD Act.
Predictable Pricing
No per-invocation charges, no surprise bills. Fixed plans with hard spending caps and Telegram alerts.
Common Questions
FAQ
Which is better for EU hosting, Cloudflare Pages or Netlify?
Neither Cloudflare Pages nor Netlify is EU-native. Both are US-based (Cloudflare Pages: US-headquartered (Cloudflare); Netlify: US-headquartered) and route most traffic through US regions, with EU availability that is usually limited or gated behind higher tiers. Even when you can select a European region, the parent company stays subject to the US CLOUD Act, which can compel disclosure of EU customer data. For genuine EU data residency, an EU-registered platform is the safer choice: Runsite runs exclusively in Frankfurt (eu-central) under EU jurisdiction, with no transatlantic transfers and no CLOUD Act exposure — the kind of guarantee neither US provider can make.
Which has the better free tier, Cloudflare Pages or Netlify?
Free tiers on both Cloudflare Pages and Netlify change frequently and tend to share the same catch: compute that sleeps after inactivity, bandwidth or build-minute caps, or trial credits that expire after a fixed window. They are fine for quick experiments but rarely sustainable for an always-on hobby project. If a permanent free tier matters, read the current terms carefully. Limits are often buried in the pricing footnotes. Runsite takes the opposite approach: a free tier with no credit card and no expiry, designed to keep small projects online indefinitely rather than nudging you onto a paid plan.
Is Cloudflare Pages or Netlify GDPR-compliant?
Both Cloudflare Pages and Netlify can be configured to support GDPR-compliant workloads through a signed Data Processing Agreement (DPA) and EU region selection where available. However, as US-incorporated entities they remain subject to the US CLOUD Act regardless of where the data physically sits, which is a documented sticking point for European compliance and DPO review. For workloads where US jurisdiction is a hard blocker (public-sector, healthcare, or privacy-sensitive consumer apps), an EU-headquartered provider removes the ambiguity entirely. Runsite is EU-registered with data kept inside the EU, so GDPR posture is the default rather than a configuration exercise.
What is the cheapest way to deploy a side project, Cloudflare Pages or Netlify?
For a single small service, both Cloudflare Pages and Netlify can look inexpensive on paper. The headline price rarely matches the real bill. Per-service billing, metered bandwidth, build minutes, and add-ons for databases or key-value stores stack up quickly, and neither platform offers a hard spending cap to stop a surprise invoice. The cheapest predictable option is one with fixed monthly pricing and an enforced ceiling. Runsite bills in EUR from €5/month with hard spending caps and Telegram alerts, plus a permanent free tier, so a side project stays cheap by design, not by careful monitoring.
// explore alternatives
Try the European Alternative
Skip the Cloudflare Pages vs Netlify debate. Deploy on Runsite.
Start Free on Runsite →