Managed application container platform

Google Cloud Run

A managed Google Cloud platform for containerized services, source-built functions, jobs, and worker pools.

Editorial verdict

Choose Cloud Run when a containerized service or function benefits from managed scaling and Google Cloud integration without requiring Kubernetes APIs.12

Best for

  • Request-driven container services
  • Teams wanting containers without cluster operations
  • Source/function deployments that fit the service model
12

Not ideal for

  • Workloads requiring Kubernetes APIs or node-level control
  • Applications outside Cloud Run instance, timeout, network, or resource limits
  • Unmodeled build, registry, event, logging, and egress costs
12
Main trade-off

Managed containers without cluster ownership are gained with Cloud Run-specific scaling, instance, networking, billing, and Google Cloud boundaries.12

Product boundary

Whether Cloud Run's managed container resource model is sufficient without adopting a cluster.

One canonical Cloud Run Tool covers distinct services, jobs, and worker pools; Serverless and Container Task relationships must use resource-specific Claims, and Cloud Run is not Kubernetes.12

For: Google Cloud teams deploying request services, source-built functions, or managed application containers

  • Kubernetes APIs are required.
  • The workload does not fit Cloud Run's instance or network model.
  • Adjacent build, registry, event, and logging costs change economics.

Why teams consider Google Cloud Run

  • Container contractApplications deploy through a documented container contract.12
  • Managed servicesRequest services scale through a managed resource model.12
  • Multiple resourcesServices, jobs, and worker pools are distinct platform resources.12

Pricing

Request-based or instance-based service billing plus compute and adjacent Google Cloud products; jobs have a separate instance-based model.3

Managed service or function

Selected service billing mode

Model resource type, region, CPU, memory, requests, concurrency, minimum instances, build, registry, logs, network, and events.3

Billing unit
CPU and memory rounded to 100 ms at verification3
Resource separation
Services, jobs, and worker pools have different execution semantics3
Pricing checked View official pricing

Google Cloud Run vs alternatives

AWS Lambda Functions

Choose when
Choose AWS-native event functions.
Compared with Google Cloud Run
A function package and AWS integration replace the broader container service contract.45

Cloudflare Workers

Choose when
Choose a web-platform isolate runtime.
Compared with Google Cloud Run
Workers compatibility and bindings differ from a conventional container.67

Amazon ECS

Choose when
Choose AWS-native orchestration and capacity providers.
Compared with Google Cloud Run
Capacity and service operations are broader.89

Google Kubernetes Engine

Choose when
Choose Kubernetes APIs and ecosystem on Google Cloud.
Compared with Google Cloud Run
Kubernetes adds cluster and workload complexity.1011

Resources and sources

Official product, policy, and pricing

  • What is Cloud Run
    Open
  • Cloud Run resource model
    Open
  • Cloud Run pricing
    Open
  1. 1
    What is Cloud Run

    Google Cloud · Accessed Official

  2. 2
    Cloud Run resource model

    Google Cloud · Accessed Official

  3. 3
    Cloud Run pricing

    Google Cloud · Accessed Official

  4. 4
    AWS Lambda Functions overview

    Amazon Web Services · Accessed Official

  5. 5
    AWS Lambda pricing

    Amazon Web Services · Accessed Official

  6. 6
    Cloudflare Workers documentation

    Cloudflare · Accessed Official

  7. 7
    Workers Node.js compatibility

    Cloudflare · Accessed Official

  8. 8
    Amazon ECS overview

    Amazon Web Services · Accessed Official

  9. 9
    ECS capacity option comparison

    Amazon Web Services · Accessed Official

  10. 10
    Google Kubernetes Engine overview

    Google Cloud · Accessed Official

  11. 11
    Choose a GKE mode

    Google Cloud · Accessed Official