# Google Cloud Run

Canonical: https://inetgeek.com/hosting/google-cloud-run/

Google Cloud service that runs container images as request-driven services, scaling instances automatically and down to zero between requests.

## 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.

## iScore

71 / 100 (80% interval 65–76), rank 2 of 11 in hosting — interval overlaps the next rank, so this is an ordering, not a finding.

inetGeek's own reading, computed from sourced facts against category peers by disclosed rules. Not a provider claim. Intervals are 80%; a provider with few documented facts is pulled toward the category middle rather than scored on what little is known.
Read this score with care:
- Price is thin: 2 of 5 criteria are scored, so it sits near the category middle with a wide interval (70–82). Read the interval, not the point.
- Capacity and limits is thin: 2 of 6 criteria are scored, so it sits near the category middle with a wide interval (45–69). Read the interval, not the point.
- Adoption is thin: 0 of 2 criteria are scored, so it sits near the category middle with a wide interval (11–89). Read the interval, not the point.
- Documented but not scored, because the page states it as text with no comparable number or a yes/limited/no (a one-time, usage-based or other-vendor price, or a per-site choice): egress_overage_price, minimum_paid_price. Read them on the provider page; the score neither rewards nor penalises what it could not compare.

Method: https://inetgeek.com/iscore/. Full output with every criterion's basis: https://inetgeek.com/scores.json. Every hosting peer ranked: https://inetgeek.com/hosting/google-cloud-run/alternatives/

- Price: 76 (70–82), weight 25%, 2 of 5 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: egress_overage_price, free_card_required, minimum_paid_price
- Capacity and limits: 57 (45–69), weight 20%, 2 of 6 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: bandwidth_included, concurrent_builds, entry_plan_memory, sites_included
- Capabilities: 83 (71–94), weight 20%, 7 of 12 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: connection_pooling, managed_databases, persistent_storage, scheduled_jobs, streaming_response_limit
- Trust and compliance: 66 (60–72), weight 15%, 6 of 11 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: audit_logs, encryption_at_rest, private_networking, support_included, support_response_time
- Evidence: 88 (88–88), weight 10%, 4 of 4 criteria scored
- Adoption: 50 (11–89), weight 10%, 0 of 2 criteria scored

## What the documentation says

### Pricing

- Free tier: Yes ([source](https://cloud.google.com/run/pricing?hl=en), read 2026-09-09)
- Kind of free offer: Free tier ([source](https://cloud.google.com/run/pricing?hl=en), read 2026-09-09)
- What the free plan includes: Per month, for services on the default request-based billing, in us-central1: 180,000 vCPU-seconds, 360,000 GiB-seconds of memory and 2 million requests. Instance-based billing, jobs and worker pools each publish a different allowance on the same page. ([source](https://cloud.google.com/run/pricing), read 2026-09-16)
- Entry paid plan: No plan fee and no minimum commitment. Cloud Run bills per vCPU-second, GiB-second and request once the monthly free allowance is used, so there is no entry price to compare, only a rate card. Recorded without a magnitude for that reason. ([source](https://cloud.google.com/run/pricing), read 2026-09-16)
- 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. ([source](https://cloud.google.com/run/pricing?hl=en), read 2026-09-09)
- Egress over allowance: 1 GiB of data transfer within North America free per month, after which Google Cloud networking rates apply. Transfer into a VPC network is billed at Virtual Private Cloud rates instead. ([source](https://cloud.google.com/run/pricing), read 2026-09-16)

### Metered rates

- CPU, per vCPU-second: $0.000024 per vCPU-second of ACTIVE time under request-based billing, in the us-central1 pricing tier. Idle time on a warm minimum instance is $0.0000025. Instance-based billing is a separate table on the same page at $0.000018, and committed-use discounts take the active rate to $0.00001992. ([source](https://cloud.google.com/run/pricing), read 2026-09-17)
- Memory, per GiB-second: $0.0000025 per GiB-second of active time under request-based billing, in the us-central1 pricing tier — the same rate Cloud Run charges for idle time on a warm instance. Committed-use discounts take it to $0.000002075. ([source](https://cloud.google.com/run/pricing), read 2026-09-17)
- Requests, per million: $0.40 per million requests under request-based billing. Committed-use discounts take it to $0.332. Instance-based billing does not meter requests at all, which is the trade for paying by the instance-second instead. ([source](https://cloud.google.com/run/pricing), read 2026-09-17)

### Limits

- Max request duration: 5 minutes by default, extendable to 60 minutes per request. ([source](https://docs.cloud.google.com/run/docs/configuring/request-timeout?hl=en), read 2026-09-09)

### Deployment

- Git deployment: Supported ([source](https://docs.cloud.google.com/run/docs/continuous-deployment-with-cloud-build?hl=en), read 2026-09-09)
- Docker deployment: Supported ([source](https://docs.cloud.google.com/run/docs/deploying?hl=en), read 2026-09-09)
- Containers: Supported ([source](https://docs.cloud.google.com/run/docs/deploying?hl=en), read 2026-09-09)

### Infrastructure

- Persistent processes: Limited — instance-based billing keeps CPU allocated ([source](https://docs.cloud.google.com/run/docs/configuring/billing-settings?hl=en), read 2026-09-09)
- Edge network: Limited — deploy per region, add a load balancer ([source](https://docs.cloud.google.com/run/docs/multiple-regions?hl=en), read 2026-09-09)
- Scales to zero: Supported ([source](https://docs.cloud.google.com/run/docs/about-instance-autoscaling?hl=en), read 2026-09-09)
- Autoscaling: Supported ([source](https://docs.cloud.google.com/run/docs/about-instance-autoscaling?hl=en), read 2026-09-09)
- Regions: 43 regions, counted from Cloud Run's own locations list — Google publishes the list rather than a total. 20 are Tier 1 and 23 Tier 2, so the region chosen changes the bill as well as the latency. ([source](https://docs.cloud.google.com/run/docs/locations?hl=en), read 2026-09-13)
- Uptime SLA: 99.95% for a non-GPU service and for GPU services with zonal redundancy; 99.5% for GPU services without it. Published as an SLO, outside Mexico and Stockholm. ([source](https://cloud.google.com/run/sla), read 2026-09-14)

### Compliance

- SOC 2: Covered under Google Cloud's core SOC 2 Type II reports, issued quarterly for Google Cloud and Google Workspace products generally. ([source](https://cloud.google.com/security/compliance/soc-2?hl=en), read 2026-09-13)
- ISO 27001: The Google Cloud Services ISMS holds an accredited ISO/IEC 27001 certification, audited by an independent third party. ([source](https://cloud.google.com/security/compliance/iso-27001?hl=en), read 2026-09-12)
- HIPAA: Cloud Run is listed as a Covered Product under Google Cloud's HIPAA Business Associate Agreement. ([source](https://cloud.google.com/security/compliance/hipaa?hl=en), read 2026-09-12)
- PCI DSS: Cloud Run is listed among the individual Google Cloud products certified against PCI DSS via annual third-party audit. ([source](https://cloud.google.com/security/compliance/pci-dss?hl=en), read 2026-09-12)

## Compared with

- [Google Cloud Run vs Azure Container Apps](https://inetgeek.com/compare/azure-container-apps-vs-google-cloud-run/)
- [Google Cloud Run vs Fly.io](https://inetgeek.com/compare/fly-io-vs-google-cloud-run/)
- [Google Cloud Run vs Heroku](https://inetgeek.com/compare/google-cloud-run-vs-heroku/)
- [Google Cloud Run vs Railway](https://inetgeek.com/compare/google-cloud-run-vs-railway/)
- [Google Cloud Run vs Render](https://inetgeek.com/compare/google-cloud-run-vs-render/)