When evaluating the pricing of Cloud Run, consider the following:

• On-demand and pay per use: Cloud Run provides on-demand capacity and automatically scales instances. Cloud Run does not require pre-provisioning infrastructure to accommodate for anticipated peak usage. Container instances billed by Cloud Run are used container instances.
• Total cost of ownership: While Cloud Run charges for compute costs, Cloud Run provides more value. For example, Cloud Run offers zonal redundancy, requires low operations because Site Reliability Engineers do a lot in the background, makes you and your team more productive via its simplicity.
• Committed use discounts: The cost of any continuous use of Cloud Run can be lowered by purchasing Committed use discounts. For example, if your Cloud Run service always has one or more active instances, you can lower its cost by committing to at least this amount. Compute flexible committed use discounts apply across GKE, Compute Engine and Cloud Run.

Read more about cost optimization.

You can use the Google Cloud pricing calculator to estimate the cost of using Cloud Run.

The following pricing tables use the GiB-second unit. A GiB-second means for example running a 1 gibibyte instance for 1 second, or running a 256 mebibyte instance for 4 seconds. The same principle applies for the vCPU-second unit. CUD refers to committed use discounts.

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. The free tier is applied as a spending based discount using Tier 1 pricing.

Cloud Run pricing depends on the selected region. Pricing for Cloud Run services also depends on the billing configuration.

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

• asia-east1 (Taiwan)
• asia-northeast1 (Tokyo)
• asia-northeast2 (Osaka)
• asia-south1 (Mumbai, India)
• europe-north1 (Finland)  Low CO₂
• europe-north2 (Stockholm)  Low CO₂
• europe-southwest1 (Madrid)  Low CO₂
• europe-west1 (Belgium)  Low CO₂
• europe-west4 (Netherlands)  Low CO₂
• europe-west8 (Milan)
• europe-west9 (Paris)  Low CO₂
• me-west1 (Tel Aviv)
• northamerica-south1 (Mexico)
• us-central1 (Iowa)  Low CO₂
• us-east1 (South Carolina)
• us-east4 (Northern Virginia)
• us-east5 (Columbus)
• us-south1 (Dallas)  Low CO₂
• us-west1 (Oregon)  Low CO₂
• us-west8 (Phoenix)

• africa-south1 (Johannesburg)
• asia-east2 (Hong Kong)
• asia-northeast3 (Seoul, South Korea)
• asia-southeast1 (Singapore)
• asia-southeast2 (Jakarta)
• asia-south2 (Delhi, India)
• australia-southeast1 (Sydney)
• australia-southeast2 (Melbourne)
• europe-central2 (Warsaw, Poland)
• europe-west10 (Berlin)  Low CO₂
• europe-west12 (Turin)
• europe-west2 (London, UK)  Low CO₂
• europe-west3 (Frankfurt, Germany)  Low CO₂
• europe-west6 (Zurich, Switzerland)  Low CO₂
• me-central1 (Doha)
• me-central2 (Dammam)
• northamerica-northeast1 (Montreal)  Low CO₂
• northamerica-northeast2 (Toronto)  Low CO₂
• southamerica-east1 (Sao Paulo, Brazil)  Low CO₂
• southamerica-west1 (Santiago, Chile)  Low CO₂
• us-west2 (Los Angeles)
• us-west3 (Salt Lake City)
• us-west4 (Las Vegas)

The billable time aggregated from all Cloud Run instances is exposed as a Cloud Monitoring metric. See container/billable_instance_time metric for more details.

Billable instance time is rounded up to the nearest 100 milliseconds and depends on the billing configuration of your Cloud Run service:

By default, Cloud Run only charges for the CPU and memory allocated to an instance when:

• The instance is starting.
• The instance is gracefully shutting down (handling the SIGTERM signal).
• At least one request is being processed by the instance. Billable instance time begins with the start of the first request and ends at the end of the last request, as shown in the following diagram:

If you set a minimum number of instances, you are also billed at a different "idle" rate when these instances are not processing requests. See the table above.

When you opt-into having Instance-based billing, you are billed for the entire lifetime any Cloud Run container instances: from the time the container is started to when it is terminated, with a minimum of 1 minute.

Cloud Run jobs are billed at the Instance-based billing rate, for the entire lifetime of any instance started, with a minimum of 1 minute.

Let's assume that you deployed a Cloud Run service with request-based billing in europe-west1 (Belgium) to serve websites, web apps, APIs, or mobile backends. Your service receives 10 million requests per month with an average per-request latency of 400 milliseconds. This service is configured with 1 vCPU, 512 MiB of memory and 20 maximum concurrent requests per instance. The traffic pattern follows a 24-hour cycle, with request volume fluctuating over 12 hours in a bell curve distribution.

Your estimated monthly cost for this workload is $13.69. Without the vCPU/Memory free tier, the cost would be $18.91. 

To understand these calculations in detail and to adjust settings and usage estimates, use the Pricing Calculator.

Let's assume that you deployed a Cloud Run service in europe-west1 (Belgium) using request-based billing for a CPU-intensive, non-thread-safe application that processes one request at a time. Your service receives 10 million requests per month with an average per-request latency of 400 milliseconds. This service is configured with 1 vCPU and 512 MiB of memory.

Your estimated monthly cost for this workload is $81.72. Without the vCPU/Memory free tier, the cost would be $86.49. 

To understand these calculations in detail and to adjust settings and usage estimates, use the Pricing Calculator.

Let's assume that you deployed a Cloud Run service in europe-west1 (Belgium) to serve real-time, GPU-accelerated LLM or image generation. This service is configured with 4 vCPU, 16 GiB of memory and NVIDIA-L4 (No zonal redundancy). This service reaches a daily peak of 2 instances and the traffic pattern follows a 24-hour cycle, with request volume fluctuating over 12 hours in a bell curve distribution.

Your estimated monthly cost for this workload is $822.40. Without the vCPU/Memory free tier, the cost would be $827.62. 

To understand these calculations in detail and to adjust settings and usage estimates, use the Pricing Calculator.

Let's assume that you deployed a Cloud Run service with request-based billing in europe-west1 (Belgium) to serve event-triggered code execution (e.g., file upload, HTTP request). Your service receives 10 million requests per month with an average per-request latency of 200 milliseconds. This service is configured with 0.167 vCPU, 256 MiB of memory and 1 maximum concurrent requests per instance. 

Your estimated monthly cost for this workload is $7.25. Without the vCPU/Memory free tier, the cost would be $12.47. 

To understand these calculations in detail and to adjust settings and usage estimates, use the Pricing Calculator.

Let's assume that you deployed a Cloud Run job in europe-west1 (Belgium) to process large-scale, scheduled data transformations (e.g., reports). Your job is launched once per hour (730 per month) with each execution lasting 1 minute. This job is configured with 1 vCPU, 512 MiB of memory and 1 task per execution. 

Your estimated monthly cost for this workload is $0.00. Without the vCPU/Memory free tier, the cost would be $0.45. 

To understand these calculations in detail and to adjust settings and usage estimates, use the Pricing Calculator.

Let's assume that you deployed a Cloud Run worker pool in europe-west1 (Belgium) to offload long-running or heavy tasks (e.g., bulk emails, video processing) to keep the main application responsive. Your worker pool is configured to run a single instance for an entire month. This worker pool is configured with 1 vCPU and 512 MiB of memory. 

Your estimated monthly cost for this workload is $11.61. Without the vCPU/Memory free tier, the cost would be $16.83. 

To understand these calculations in detail and to adjust settings and usage estimates, use the Pricing Calculator.

Cloud Run deployments from source and functions operate as Cloud Run services and are billed accordingly based on the conditions above.

When deploying from source or creating a function, Cloud Run uses Cloud Build to convert your source code or function into an executable image. The images are created in Cloud Build and stored in Artifact Registry. Artifact Registry has its own free tier of storage. If you deploy your source code or function to Artifact Registry and exceed the Artifact Registry free tier usage, you will incur charges for deploying your functions, even when your use of Cloud Run falls within the free tier.

Pricing for Cloud Build and Artifact Registry is not included in Cloud Run pricing. To review pricing for these services, see the Cloud Build Pricing and Artifact Registry Pricing pages.

Cloud Run uses Eventarc for event delivery. Pricing for Eventarc is not included in the Cloud Run pricing above. Review pricing on the Eventarc Pricing page.

Pricing for Cloud Run functions (1st gen) functions is not included in Cloud Run pricing. Review the pricing in Cloud Run functions (1st gen) pricing.