Skip to main content

Google Cloud Run functions

Runtime Platform · FaaS

Deploy single-purpose HTTP and event-driven functions from source to managed serverless infrastructure.

Cloud Run functions deploys an HTTP or event handler from source. Google builds it into a container, connects the trigger, and runs the result as a managed Cloud Run service. Teams keep a function-style workflow while gaining access to Cloud Run’s service controls. These scaling and release controls apply to current Cloud Run functions deployed as Cloud Run services; first-generation functions differ. Tagged revision previews can share external databases and secrets rather than clone an isolated application stack.
Best for

Event-driven functions, APIs, automation, scheduled processing, and Google Cloud service integrations that do not require managing containers directly.

Watch out for

First-generation and current Cloud Run functions have materially different limits, concurrency, scaling, and regional behavior. Treating them as one execution model can produce incorrect architecture or capacity assumptions.

Workloads
  • APIs
  • Backend Services
  • Background Workers
  • Data Processing
  • Scheduled Jobs
Services
  • Functions
Delivery
  • Managed

Development & Execution

Supported platform capabilities, execution environments, development technologies, deployment models, integrations, and triggers.

Runtimes

  • .NET Runtime
  • JVM
  • Node.js

Languages

  • C#
  • Go
  • Java
  • JavaScript
  • PHP
  • Python
  • Ruby
  • TypeScript

Frameworks

  • Express.js
  • Fastify
  • Spring Boot

Capabilities

  • Compute Autoscaling
  • Scale to Zero
  • Zero-Downtime Application Deployments
  • Deployment Rollbacks
  • Deployment Traffic Splitting
  • Preview Environments

Architecture

  • x64

Deployment & packaging

  • Local Emulator
  • Serverless (Managed Runtime)

Integrations

  • Datadog
  • GitHub
  • GitLab
  • Terraform

Triggers

  • Scheduled Invocation
  • Database Events
  • Publish-Subscribe Topics
  • HTTP Requests
  • Queue Messages
  • Storage Events

Pricing

Published pricing structure, representative costs, and material billing factors.

Starting Price
$0.40 Invocations
Primary Billing
Resource based Cloud Run Functions First-Generation Usage
Free Tier
Recurring free allowances
Commitment
Usage is metered by invocation, provisioned memory and CPU time, and outbound data transfer.

Cloud Run Functions First-Generation Usage

Primary Pricing

Cloud Run functions (1st gen), formerly Cloud Functions (1st gen), uses USD Tier 1 reference rates; Tier 2 regions and other billing currencies have different rates.

ResourceBilling UnitPrice
Invocations Charged after the first 2 million invocations per monthper 1 million invocations$0.40
Memory time Tier 1 active compute rateper GB-second$0.0000025
CPU time Tier 1 active compute rateper GHz-second$0.0000100
Internet data transfer Outbound data after the first 5 GB per monthper GB$0.12

Free Tier

Perpetual monthly allowances for Cloud Run functions (1st gen), measured using Tier 1 pricing equivalents.

  • Invocations: 2,000,000 invocations per month
  • Memory time: 400,000 GB-seconds per month
  • CPU time: 200,000 GHz-seconds per month
  • Internet data transfer: 5 GB per month

Billing Commitment

Usage is metered by invocation, provisioned memory and CPU time, and outbound data transfer.

Infrastructure & Availability

Where workloads run, how deployment is scoped, and what underlying infrastructure the platform depends on.

Cloud Run functions, formerly Cloud Functions 2nd gen, deploy as Cloud Run services and use Cloud Run's current regional footprint. Original Cloud Run functions (1st gen), formerly Cloud Functions 1st gen, have a different regional footprint. GPU, domain mapping, ephemeral disk, and VPC connector availability can be narrower.

Execution

  • Single Region
  • Multi Region

Deployment scope

  • Regional

Infrastructure providers

  • Google Cloud Platform

Available regions (43)

LocationRegion ID
North America 11 regions
Iowa Cloud Run Tier 1 pricing region.us-central1
South Carolina Cloud Run Tier 1 pricing region.us-east1
Northern Virginia Cloud Run Tier 1 pricing region.us-east4
Columbus Cloud Run Tier 1 pricing region.us-east5
Dallas Cloud Run Tier 1 pricing region.us-south1
Oregon Cloud Run Tier 1 pricing region.us-west1
Montreal Cloud Run Tier 2 pricing region.northamerica-northeast1
Toronto Cloud Run Tier 2 pricing region.northamerica-northeast2
Los Angeles Cloud Run Tier 2 pricing region.us-west2
Salt Lake City Cloud Run Tier 2 pricing region.us-west3
Las Vegas Cloud Run Tier 2 pricing region.us-west4
Latin America 3 regions
Mexico Cloud Run Tier 1 pricing region.northamerica-south1
Sao Paulo Cloud Run Tier 2 pricing region.southamerica-east1
Santiago Cloud Run Tier 2 pricing region.southamerica-west1
Europe 13 regions
Finland Cloud Run Tier 1 pricing region.europe-north1
Stockholm Cloud Run Tier 1 pricing region.europe-north2
Madrid Cloud Run Tier 1 pricing region.europe-southwest1
Belgium Cloud Run Tier 1 pricing region.europe-west1
Netherlands Cloud Run Tier 1 pricing region.europe-west4
Milan Cloud Run Tier 1 pricing region.europe-west8
Paris Cloud Run Tier 1 pricing region.europe-west9
Warsaw Cloud Run Tier 2 pricing region.europe-central2
Berlin Cloud Run Tier 2 pricing region.europe-west10
Turin Cloud Run Tier 2 pricing region.europe-west12
London Cloud Run Tier 2 pricing region.europe-west2
Frankfurt Cloud Run Tier 2 pricing region.europe-west3
Zurich Cloud Run Tier 2 pricing region.europe-west6
Asia Pacific 12 regions
Taiwan Cloud Run Tier 1 pricing region.asia-east1
Tokyo Cloud Run Tier 1 pricing region.asia-northeast1
Osaka Cloud Run Tier 1 pricing region.asia-northeast2
Mumbai Cloud Run Tier 1 pricing region.asia-south1
Bangkok Cloud Run Tier 1 pricing region; Serverless VPC Access connectors are not supported.asia-southeast3
Hong Kong Cloud Run Tier 2 pricing region.asia-east2
Seoul Cloud Run Tier 2 pricing region.asia-northeast3
Singapore Cloud Run Tier 2 pricing region.asia-southeast1
Jakarta Cloud Run Tier 2 pricing region.asia-southeast2
Delhi Cloud Run Tier 2 pricing region.asia-south2
Sydney Cloud Run Tier 2 pricing region.australia-southeast1
Melbourne Cloud Run Tier 2 pricing region.australia-southeast2
Middle East & Africa 4 regions
Tel Aviv Cloud Run Tier 1 pricing region.me-west1
Johannesburg Cloud Run Tier 2 pricing region.africa-south1
Doha Cloud Run Tier 2 pricing region.me-central1
Dammam Cloud Run Tier 2 pricing region.me-central2

Availability reviewed · Availability source

Resource & Execution Limits

Memory

32 GiB

2nd gen function

Request payload

32 MB

2nd gen HTTP function

Response payload

32 MB

2nd gen HTTP function

Execution time

60 minutes

2nd gen HTTP function

Scheduled / task-queue execution

30 minutes

Current function

Event-driven execution

540 seconds

Current function

Security & Compliance

Security Controls

Access Control
Function-level IAM and authenticated invocation Role differs for 1st gen and Cloud Run-based functions
Encryption at Rest
Customer-managed encryption keys Supported build and runtime resources; customer configuration
Private Networking
VPC Service Controls perimeter and VPC egress Customer organization and network configuration
Audit Logging
Cloud Audit Logs Management coverage; data-access classes may require configuration

Audits & Certifications

SOC Reports
SOC 2 Type II Cloud Run functions in scope
ISO Certifications
ISO/IEC 27017 and 27018 Cloud Run functions in scope
PCI DSS
Cloud Run functions in scope

Compliance

FedRAMP
FedRAMP High Authorized service and region/configuration scope
HIPAA
HIPAA-eligible use Google Cloud BAA and customer controls required

FAQ

What happened to Google Cloud Functions?
Google renamed Cloud Functions to Cloud Run functions in August 2024. Cloud Functions (2nd gen) became Cloud Run functions, while Cloud Functions (1st gen) became Cloud Run functions (1st gen).
Are Cloud Run functions separate from Cloud Run services?
Not in the current model. A Cloud Run function is source code that Google builds into a container and deploys as a Cloud Run service. The function workflow provides function-oriented source deployment with HTTP or CloudEvents handlers while using Cloud Run infrastructure and configuration.
Is Google Cloud Functions free?
Yes. Google Cloud Functions, now Cloud Run functions, retains recurring monthly usage allowances; the current first-generation allowance includes 2 million invocations plus compute and transfer grants.

Explore

Explore more runtime platforms

FaaS Type Functions Service

Alternatives to Google Cloud Run functions

AWS Lambda Functions Azure Functions DigitalOcean Functions