Cloud Run pricing

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.

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

Outbound internet data transfer uses the Premium Network Service Tier and is charged at Google Cloud networking pricing with a free tier of 1GiB free data transfer within North America per month.

Data transfer to Virtual Private Cloud networks is billed as Data transfer from a VM and charged at Virtual Private Cloud data transfer rates. Serverless VPC Access connectors also charge for the compute required to run them. See Serverless VPC Access pricing.

There is no charge for data transfer to Google Cloud resources in the same region (for example for traffic from one Cloud Run service to another Cloud Run service). There is no charge for data transfer to Media CDN, Cloud CDN and Cloud Load Balancing.

Pricing considerations

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. Cloud Run automatically creates Committed use discount recommendations based on your historical usage.

Read more about cost optimization for Cloud Run

Pricing calculator

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

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. 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 CPU allocation configuration.

Pricing for regions in Tier 1

Resources CPU Memory Requests
Services
with CPU always allocated

Jobs
$0.00001800 / vCPU-second beyond free tier

Free: First 240,000 vCPU-seconds free per month

CUD1: $0.00001494
$0.00000200 / GiB-second beyond free tier

Free: First 450,000 GiB-seconds free per month

CUD1: $0.00000166
$0
Services
with CPU only allocated during request for charged instance time
$0.00002400 / vCPU-second beyond free tier

Free: First 180,000 vCPU-seconds free per month

CUD1: $0.00001992

If idle min instance2: $0.00000250
$0.00000250 / GiB-second beyond free tier

Free: First 360,000 GiB-seconds free per month

CUD1: $0.000002075

If idle min instance2: $0.00000250
$0.40 / million requests beyond free tier3

Free: 2 million requests free per month

CUD1: $0.332

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

1 CUD refers to committed use discounts.

2 idle min instance refers to idle billable time for instances kept warm using minimum instances. Idle instances that are not minimum instances are not charged.

3 Requests are only billed when they reach the container after successfully being authenticated, requests denied by IAM policy are not billed.

Pricing for regions in Tier 2

Resources CPU Memory Requests
Services
with CPU always allocated

Jobs
$0.00002160 / vCPU-second beyond free tier

Free: First 200,000 vCPU-seconds free per month

CUD1: $0.000017928
$0.00000240 / GiB-second beyond free tier

Free: First 375,000 GiB-seconds free per month

CUD1: $0.000001992
$0
Services
with CPU only allocated during request for charged instance time
$0.00003360 / vCPU-second beyond free tier

Free: First 128,571 vCPU-seconds free per month

CUD1: $0.000027888

If idle min instance2: $0.00000350
$0.00000350 / GiB-second beyond free tier

Free: First 257,142 GiB-seconds free per month

CUD1: $0.000002905

If idle min instance2: $0.00000350
$0.40 / million requests beyond free tier3

Free: 2 million requests free per month

CUD1: $0.332

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

1 CUD refers to committed use discounts.

2 idle min instance refers to idle billable time for instances kept warm using minimum instances. Idle instances that are not minimum instances are not charged.

3 Requests are only billed when they reach the container after successfully being authenticated, requests denied by IAM policy are not billed.

Regional price tiers

Subject to Tier 1 pricing

  • asia-east1 (Taiwan)
  • asia-northeast1 (Tokyo)
  • asia-northeast2 (Osaka)
  • europe-north1 (Finland) leaf icon Low CO2
  • europe-southwest1 (Madrid)
  • europe-west1 (Belgium) leaf icon Low CO2
  • europe-west4 (Netherlands)
  • europe-west8 (Milan)
  • europe-west9 (Paris) leaf icon Low CO2
  • me-west1 (Tel Aviv)
  • us-central1 (Iowa) leaf icon Low CO2
  • us-east1 (South Carolina)
  • us-east4 (Northern Virginia)
  • us-east5 (Columbus)
  • us-south1 (Dallas)
  • us-west1 (Oregon) leaf icon Low CO2

Subject to Tier 2 pricing

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

Billable instance time

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 CPU allocation configuration of your Cloud Run service:

Billable instance time

Billable instance time for services with CPU allocated only during request processing

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.

Billable instance time for services with CPU always allocated

When you opt-into having CPU always allocated, 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.

Billable instance time for Cloud Run jobs

Cloud Run jobs are billed at the CPU always allocated rate, for the entire lifetime of any instance started, with a minimum of 1 minute.

What's next

Request a custom quote

With Google Cloud's pay-as-you-go pricing, you only pay for the services you use. Connect with our sales team to get a custom quote for your organization.
Contact sales