Compare / Cloudflare Workers vs Google Cloud Run
Cloudflare Workers vs Google Cloud Run
Pre-calculated from hand-checked data — Cloudflare checked 2026-08-06, Google Cloud Run checked 2026-08-06.
The short version
Cloudflare Workers wins more of our comparison points, but Google Cloud Run still fits if container apps with spiky or low traffic that want scale-to-zero economics and can manage billing discipline describes you.
Price Cloudflare Workers
Cloudflare Workers is cheaper at most of the stages we model.
Ease Tie
Both take similar effort to get a first deploy live.
Control Cloudflare Workers
Cloudflare Workers gives you more control over the stack — the flip side of the convenience trade.
Features Google Cloud Run
Google Cloud Run comes out ahead on 4 of the 15 features we track, versus 3.
What developers say about this matchup
We couldn't find a substantive first-person discussion comparing this exact pair. We leave the section empty instead of filling it with vendor marketing or generic SEO comparisons.
At a glance
| Cloudflare Workers | Google Cloud Run | |
|---|---|---|
| Best for | Static sites and JS/TS apps where bandwidth costs matter or a global edge is a plus. | Container apps with spiky or low traffic that want scale-to-zero economics and can manage billing discipline. |
| How deploys work | Deploy from Git or with the wrangler CLI; framework adapters handle SSR apps. | Run `gcloud run deploy --source .` — buildpacks containerize the app, or push any Docker image; GitHub continuous deployment is built in. |
| The tradeoff | More platform-specific setup than the git-push hosts — adapters, wrangler config, and Workers-flavored storage. | The best free tier and autoscaling here, attached to a billing system with no hard cap and real horror stories. |
| Free tier | Free: unlimited static requests and bandwidth, 100,000 Worker requests per day, 3,000 build minutes per month. | Always free: 2M requests, 180k vCPU-seconds, 360k GiB-seconds per month, plus a $300/90-day new-customer credit. |
What you'd realistically pay
Cloudflare Workers Google Cloud Run
| Project stage | Cloudflare Workers | Google Cloud Run | Cheaper |
|---|---|---|---|
| Just starting | Free Free — Genuinely free for small sites — bandwidth is never billed. | Free Free tier — A scale-to-zero service with hobby traffic typically rounds to $0 — the always-free tier absorbs it. | ≈ Tie |
| Steady traffic | ≈$5/mo Workers Paid — Includes 10M requests and 30M CPU-milliseconds per month. | ≈$10/mo Pay-as-you-go + 1 warm instance — One min-instance (1 vCPU, 512 MiB at the idle rate) is ~$10/month; request costs on top are usually small. | Cloudflare Workers |
| Growing | ≈$10/mo Workers Paid + usage — Extra requests cost $0.30 per million; bandwidth remains free. | ≈$58/mo Always-on + Cloud SQL — ~$50/month for an always-on 1 vCPU / 1 GiB service (instance-based billing) plus ~$7.67 for a db-f1-micro Cloud SQL instance. | Cloudflare Workers |
Cloudflare Workers pricing notes
- No charges for data transfer or bandwidth on any plan.
- Cloudflare sells its own storage (D1 database, KV, R2 objects) with separate free tiers and pricing.
Google Cloud Run pricing notes
- Egress: first 1 GiB/month free, then $0.12/GiB to NA/EU/Asia.
- Tier 2 regions cost more; committed-use discounts take ~17% off.
- The $300 new-customer credit runs 90 days and cannot produce a bill — the account closes instead of charging you.
Our ratings
Ease of use
Pricing clarity Cloudflare Workers
Free tier
Scaling
Control Cloudflare Workers
Feature by feature
Cloudflare Workers wins 3, Google Cloud Run wins 4, with 8 even.
Deploy workflow
| Cloudflare Workers | Google Cloud Run | |
|---|---|---|
| Deploy from Git push | Yes Workers Builds deploys on push from GitHub or GitLab. | Yes Built-in continuous deployment from GitHub, or deploy from source with gcloud. |
| Preview deploys | Yes Preview URLs per version and non-production branch builds. | Partial Every deploy creates a tagged revision you can hit directly and split traffic to — but no automatic PR previews. |
| Official CLI | Yes wrangler handles dev, deploys, logs, and storage. | Yes `gcloud run` covers deploys, revisions, and traffic splits. |
| Instant rollbacks | Yes Versioned deployments with one-command rollback. | Yes Shift traffic back to any previous revision instantly. |
Platform
| Cloudflare Workers | Google Cloud Run | |
|---|---|---|
| Custom domains + HTTPS | Yes Custom domains with automatic TLS on Cloudflare’s network. | Partial Domain mappings exist but Google steers production setups toward a load balancer, which adds cost and setup. |
| Built-in CDN / edge network | Yes The platform is Cloudflare’s CDN — static assets are free and cached globally. | Partial Cloud CDN is available but requires fronting Cloud Run with a load balancer. |
| Serverless functions | Yes Workers are the compute model, running in 300+ locations. | Yes The whole platform is serverless; Cloud Run functions cover event-driven code. |
| Docker containers | Partial Cloudflare Containers run alongside Workers but are newer and more limited than a real container host. | Yes Runs any container image — that is the product. |
| SSH / shell access | No No servers to shell into. | No No servers to reach. |
| EU hosting region | Partial Code runs everywhere by default; you can restrict data (not compute) to EU jurisdiction. | Yes A dozen-plus EU regions, four of them at Tier 1 pricing. |
Runtime & operations
| Cloudflare Workers | Google Cloud Run | |
|---|---|---|
| Automatic scaling | Yes Scales per request across the whole network with no knobs. | Yes Scales per request from zero to your max-instances setting. |
| Scale to zero | Yes Workers bill per request — idle costs nothing. | Yes Idle services cost nothing unless you set min-instances. |
| Scheduled jobs | Yes Cron Triggers run Workers on a schedule, including on the free plan. | Yes Cloud Scheduler triggers services; Cloud Run jobs handle batch work. |
| Managed database | Partial D1 (SQLite), KV, and R2 are managed but Cloudflare-flavored; classic Postgres means an external provider. | Yes Cloud SQL from ~$7.67/month (no SLA at that size); Firestore and AlloyDB nearby. |
| Logs & metrics built in | Partial Live tail and Workers analytics included; persistent logs need Logpush or a third party. | Yes Cloud Logging, Monitoring, and request traces are built in. |
Watch out for
Cloudflare
- Server-side frameworks (Next.js, Astro SSR, SvelteKit) run through adapters, which have more rough edges than Vercel or Netlify.
- The runtime is Workers-specific: Node.js compatibility is good but not total, and storage means D1, KV, and R2 rather than a classic server.
- The free plan enforces 100,000 Worker requests per day — static requests stay unlimited.
Google Cloud Run
- There is no hard spend cap anywhere in Google Cloud — budgets only send alerts. The community horror stories ($4.6k on an idle setup, $18k against a $7 budget) are real.
- Min-instances are the classic trap: a warm instance bills around $10/month, and old revisions can silently keep their own min-instances.
- Egress costs $0.12/GiB after the first free GiB — heavy traffic gets expensive fast.
- Since March 2026 Google can automatically raise your spending-tier quotas, which amplifies leaked-API-key incidents.
Read the full reviews: Cloudflare and Google Cloud Run. Or answer four questions to see what fits your project.