Pricing

With regard to deploying container images from Container Registry, as documented in Cloud Storage network pricing, you are not charged if you deploy to a region located on the same continent as your container image. For example, deployments to a Cloud Run (fully managed) service in us-central1 or us-east1 from us.gcr.io or gcr.io are free of charge.

Cloud Run (fully managed) charges you only for the resources you use, rounded up to the nearest 100 millisecond. Note that each of these resources have free quota. Your total Cloud Run (fully managed) bill will be the sum of the resources in the pricing table.

When setting concurrency higher than one request at a time, multiple requests can share the allocated CPU and memory.

Pricing calculator

You can use the Google Cloud Platform Pricing Calculator to estimate the cost of using Cloud Run (fully managed).

Pricing tables

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.

Tier CPU Memory Requests Networking
Free First 180,000 vCPU-seconds free per month First 360,000 GiB-seconds free per month 2 million requests free per month 1 GiB free egress within North America per month
1 $0.00002400 / vCPU-second beyond free quota
($0.00000250 if idle*)		 $0.00000250 / GiB-second beyond free quota
($0.00000250 if idle*)		 $0.40 / million requests beyond free quota Google Cloud Network Premium tier pricing beyond free quota.
2 $0.00003360 / vCPU-second beyond free quota
($0.00000350 if idle*)		 $0.00000350 / GiB-second beyond free quota
($0.00000350 if idle*)		 $0.40 / million requests beyond free quota Google Cloud Network Premium tier pricing beyond free quota.

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

* idle refers to inactive billable time of instances kept warm using minimum instances.

Subject to Tier 1 pricing

  • asia-east1 (Taiwan)
  • asia-northeast1 (Tokyo)
  • asia-northeast2 (Osaka)
  • europe-north1 (Finland)
  • europe-west1 (Belgium)
  • europe-west4 (Netherlands)
  • us-central1 (Iowa)
  • us-east1 (South Carolina)
  • us-east4 (Northern Virginia)
  • us-west1 (Oregon)

Subject to Tier 2 pricing

  • asia-east2 (Hong Kong)
  • asia-northeast3 (Seoul, South Korea)
  • asia-southeast1 (Singapore)
  • asia-southeast2 (Jakarta)
  • asia-south1 (Mumbai, India)
  • australia-southeast1 (Sydney)
  • europe-west2 (London, UK)
  • europe-west3 (Frankfurt, Germany)
  • europe-west6 (Zurich, Switzerland)
  • northamerica-northeast1 (Montreal)
  • southamerica-east1 (Sao Paulo, Brazil)
  • us-west2 (Los Angeles)
  • us-west3 (Las Vegas)
  • us-west4 (Salt Lake City)

The free quota is aggregated across projects by billing account and resets every month; you are billed only for usage past the free quota. The free tier is applied as a spending based discount using Tier 1 pricing.

Billable time

You are billed only for the CPU and memory allocated during billable time, rounded up to the nearest 100 milliseconds.

For a given container instance, active billable time occurs when:

  • The container instance is starting
  • The container instance is shut down and the SIGTERM signal is handled.

  • At least one request is being processed by the container instance. Active billable time begins with the start of the first request and ends at the end of the last request, as shown in the following diagram:

    Billable time

If you set a minimum number of container instances, you are also billed for the time these instances are not active (idle billable time).

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