Google Cloud Run
Google Cloud service that runs container images as request-driven services, scaling instances automatically and down to zero between requests.
- Application platforms
- Yes
- Not documented
- 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.
Who it suits.
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.
Consider something else if…
You need a process that stays running between requests, or a disk that survives a deploy.
Editorial · Palash Bagchi · approved
What the documentation says.
Each value below links to the page it was read from, with the sentence it came from. Criteria Google Cloud Run does not publish are not listed.
Pricing
Free tier
Yes
Sources (1) →Sources ↓
- Cloud Run pricing — Google Cloud ↗
“Services with instance-based billing Free tier (based on us-central1 pricing): CPU - First 240,000 vCPU-seconds free per month RAM - First 450,000 GiB-seconds free per month [...] The free tier usage is aggregated across projects by billing account and resets every month; you are billed only for usage past the free tier.”
Read 2026-09-09 · official pricing
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.
Sources (1) →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
Limits
Max request duration
5 minutes by default, extendable to 60 minutes per request.
Sources (1) →Sources ↓
- Configure request timeout for services — Google Cloud Documentation ↗
“The timeout is set by default to 5 minutes (300 seconds) and can be extended up to 60 minutes (3600 seconds).”
Read 2026-09-09 · official docs
Deployment
Git deployment
Supported
Sources (1) →Sources ↓
- Continuously deploy from a repository — Cloud Run — Google Cloud Documentation ↗
“If you have source code or functions in a Git repository and want to automate builds and set up continuous deployments from a repository, you can use either Cloud Build or Developer Connect in the Cloud Run console.”
Read 2026-09-09 · official docs
Docker deployment
Supported
Sources (1) →Sources ↓
- Deploy container images to Cloud Run services — Google Cloud Documentation ↗
“You can directly use container images stored in Artifact Registry, or public images from Docker Hub or GitHub Container Registry.”
Read 2026-09-09 · official docs
Containers
Supported
Sources (1) →Sources ↓
- Deploy container images to Cloud Run services — Google Cloud Documentation ↗
“This page describes how to deploy container images to a new Cloud Run service or to a new revision of an existing Cloud Run service.”
Read 2026-09-09 · official docs
Infrastructure
Persistent processes
Limited — instance-based billing keeps CPU allocated
Sources (1) →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
Edge network
Limited — deploy per region, add a load balancer
Sources (1) →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
Scales to zero
Supported
Sources (1) →Sources ↓
- About instance autoscaling in Cloud Run services — Google Cloud Documentation ↗
“When a revision does not receive any traffic, by default, it is scaled to zero instances.”
Read 2026-09-09 · official docs
Autoscaling
Supported
Sources (1) →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
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.
Sources (1) →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
When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.