Google Cloud Run vs Render
SEPT 2026 auditA comparison of Google Cloud Run and Render built from values read directly from each provider's own documentation, with the source recorded against every figure.
The short answer
Choose Google Cloud Run if…
A container you already build, that should cost nothing when nobody is using it. Scales to zero by default and back up on request volume, with a 60-minute ceiling per request that most request-driven platforms do not offer.
Editorial · Palash Bagchi · approved
Choose Render if…
Workloads that need real background workers and persistent processes alongside web services, deployed from a repository or a Dockerfile. Managed Postgres and static sites run on the same platform.
Editorial · Palash Bagchi · approved
Consider something else if…
- Google Cloud Run: You need a process that stays running between requests, or a disk that survives a deploy.
- Render: Free web services spin down after 15 minutes without traffic, which makes the free tier unsuitable for anything that must answer immediately.
5 sourced criteria separate them — see where, with sources, below.
Pick the criteria you care about. The chart counts how many of them lean toward each provider — the same read as scanning the bars below, just totalled for the ones you chose.
Google Cloud Run 0
Render 0
At a glance.
| Criterion | Google Cloud Run | Render |
|---|---|---|
| Pricing | ||
| Free tier | Yes | Yes |
| Pricing model | Metered by resource, billed in 100 ms increments, with no monthly minimum. Two billing settings change what is counted: request-based charges CPU only while a request is being processed, instance-based charges for the whole instance lifecycle. Prices vary by region — the location list is split into Tier 1 and Tier 2 pricing — and the free tier is applied as a spending-based discount at Tier 1 rates. | The Hobby plan does not have a monthly fee, so you only pay for usage. |
| Deployment | ||
| Git deployment | Supported | Supported |
| Docker deployment | Supported | Supported |
| Containers | Supported | Supported |
| Infrastructure | ||
| Persistent processes | Limited — instance-based billing keeps CPU allocated | Supported |
| Edge network | Limited — deploy per region, add a load balancer | Supported |
| Scales to zero | Supported | Supported |
| Autoscaling | Supported | Limited |
| Regions | 41 regions, counted from Cloud Run's own locations list — Google publishes the list rather than a total. They are split into Tier 1 and Tier 2 pricing, so the region chosen changes the bill as well as the latency. | Oregon, USA; Ohio, USA; Virginia, USA; Frankfurt, Germany; Singapore |
Where they differ.
Pricing model
- Google Cloud Run
- Metered by resource, billed in 100 ms increments, with no monthly minimum. Two billing settings change what is counted: request-based charges CPU only while a request is being processed, instance-based charges for the whole instance lifecycle. Prices vary by region — the location list is split into Tier 1 and Tier 2 pricing — and the free tier is applied as a spending-based discount at Tier 1 rates.
- Render
- The Hobby plan does not have a monthly fee, so you only pay for usage.
Sources (2) →Sources ↓
- Cloud Run pricing — Google Cloud ↗
“Cloud Run charges you only for the resources you use, rounded up to the nearest 100 millisecond. Your total Cloud Run bill will be the sum of the resource usage in the pricing table after the free tier is applied. [...] Cloud Run pricing depends on the selected region. Pricing for Cloud Run services also depends on the billing configuration. [...] The free tier is applied as a spending based discount using Tier 1 pricing.”
Read 2026-09-09 · official pricing
- Platform Features by Plan – Render Docs ↗
“The Hobby plan does not have a monthly fee, so you only pay for usage.”
Read 2026-09-05 · official docs
Persistent processes
- Google Cloud Run
- Limited — instance-based billing keeps CPU allocated
- Render
- Supported
Sources (2) →Sources ↓
- Billing settings for Cloud Run services — Google Cloud Documentation ↗
“With request-based billing, CPU is only allocated during request processing. With instance-based billing, CPU is allocated for the entire container instance lifecycle. [...] Instance-based billing can be useful for running short-lived background tasks and other asynchronous processing tasks. This setting was previously called CPU always allocated.”
Read 2026-09-09 · official docs
- Background Workers – Render Docs ↗
“Background workers are services that run continuously (like a web service or a private service), but they don't receive any incoming network traffic.”
Read 2026-09-05 · official docs
Edge network
- Google Cloud Run
- Limited — deploy per region, add a load balancer
- Render
- Supported
Sources (2) →Sources ↓
- Serve traffic from multiple regions — Cloud Run — Google Cloud Documentation ↗
“Because Cloud Run services deploy into individual regions, you must deploy your service to multiple regions and then configure global load balancing for the service. You can automate cross-regional failover using Cloud Run service health.”
Read 2026-09-09 · official docs
- Static Sites – Render Docs ↗
“Render serves your site over a blazing-fast, reliable, and secure global CDN. We cache your content on network edges around the world, ensuring the fastest possible load times for your users.”
Read 2026-09-05 · official docs
Autoscaling
- Google Cloud Run
- Supported
- Render
- Limited
Sources (2) →Sources ↓
- About instance autoscaling in Cloud Run services — Google Cloud Documentation ↗
“By default, each Cloud Run revision is automatically scaled to the number of instances needed to handle incoming requests, events, or CPU utilization. [...] Cloud Run adjusts instance counts to keep average CPU and concurrency within target thresholds.”
Read 2026-09-09 · official docs
- Scaling – Render Docs ↗
“Render can automatically scale your service up and down based on CPU and/or memory utilization targets that you specify. [...] Autoscaling requires a Pro plan or higher.”
Read 2026-09-05 · official docs
Regions
41 regions, counted from Cloud Run's own locations list — Google publishes the list rather than a total. They are split into Tier 1 and Tier 2 pricing, so the region chosen changes the bill as well as the latency.
Oregon, USA; Ohio, USA; Virginia, USA; Frankfurt, Germany; Singapore
Sources (2) →Sources ↓
- Cloud Run locations — Google Cloud Documentation ↗
“Each Cloud Run resource resides in a region. [...] Subject to Tier 1 pricing asia-east1 (Taiwan) asia-northeast1 (Tokyo) asia-northeast2 (Osaka) asia-south1 (Mumbai, India) asia-southeast1 [...] northamerica-northeast2 (Toronto) southamerica-east1 (Sao Paulo, Brazil) southamerica-west1 (Santiago, Chile) us-west2 (Los Angeles) us-west3 (Salt Lake City) us-west4 (Las Vegas)”
Read 2026-09-09 · official docs
- Regions ↗
“Oregon, USA / Ohio, USA / Virginia, USA / Frankfurt, Germany / Singapore”
Read 2026-09-05 · official docs
When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.
Documented by only one.
These criteria are published by one provider and not the other. An absence here means we have not found a source, not that the feature is missing.
Questions this comparison answers.
Should I choose Google Cloud Run or Render?
Pick Google Cloud Run if A container you already build, that should cost nothing when nobody is using it. Scales to zero by default and back up on request volume, with a 60-minute ceiling per request that most request-driven platforms do not offer.
Pick Render if Workloads that need real background workers and persistent processes alongside web services, deployed from a repository or a Dockerfile. Managed Postgres and static sites run on the same platform.