Cloud Run

Name: Cloud Run
Brand: Google
Rating: 4.6 (277 reviews)

Cloud Run is a Google Cloud service that runs containerized code on Google-managed infrastructure with autoscaling and scale-to-zero behavior, supporting request/response services, run-to-completion jobs, and worker pools.

Est 1998|Valuation $4081.3B|Raised $26.1M|3 Ref Customers

LinkedIn 41.9M|Website|Web traffic 3.3M|FTEs 198,933|HQ Mountain View, California, US

MarketsCloud Infrastructure Providers (IaaS/PaaS)Application Hosting Platforms Container Management Cloud Infrastructure Providers (IaaS/PaaS)

Platform CoversContinuous Integration & Continuous Delivery (CI/CD)Workflow Orchestration

| Aspect | Cloud Run | Azure Container Apps | AWS App Runner | |--------|-----------|----------------------|----------------| | Starting Price | Published usage-based billing; vendor offers a published free-tier and options for committed discounts | Published usage-based billing with consumption- and request-based metering | Published usage-based billing based on compute/memory time and other usage dimensions | | Typical Fit | Teams seeking a managed container runtime with GCP integration, autoscaling, and serverless characteristics | Azure-centric teams running microservices within the Azure ecosystem | AWS-centric teams deploying web apps from source or images | | Notable Strength | Integration with GCP IAM/observability and multiple execution patterns (services/jobs/worker pools) | Azure-native integration and microservices tooling | Simple source-to-deploy workflows and AWS ecosystem integration | | Notable Weakness | Pricing and networking complexity for some architectures; cold-start considerations for latency-sensitive services | Region/feature parity and Azure-specific operational considerations | In some cases, limited scale-to-zero behavior; may be less cost-effective for sporadic workloads | - Narrative analysis - Cloud Run vs Azure Container Apps: differences are workload- and environment-dependent. Community reports suggesting performance differences are anecdotal and workload-specific; buyers should run benchmarks relevant to their workloads. - Cloud Run vs AWS App Runner: App Runner is positioned for simple deployments from source or containers; differences in scale-to-zero behavior and published pricing models can affect cost for infrequent traffic patterns. - Cloud Run vs DIY Knative/Kubernetes: self-managed Knative on Kubernetes provides more control and portability at the cost of higher operational complexity.

01Competitive Landscape

Aspect	Cloud Run	Azure Container Apps	AWS App Runner
Starting Price	Published usage-based billing; vendor offers a published free-tier and options for committed discounts	Published usage-based billing with consumption- and request-based metering	Published usage-based billing based on compute/memory time and other usage dimensions
Typical Fit	Teams seeking a managed container runtime with GCP integration, autoscaling, and serverless characteristics	Azure-centric teams running microservices within the Azure ecosystem	AWS-centric teams deploying web apps from source or images
Notable Strength	Integration with GCP IAM/observability and multiple execution patterns (services/jobs/worker pools)	Azure-native integration and microservices tooling	Simple source-to-deploy workflows and AWS ecosystem integration
Notable Weakness	Pricing and networking complexity for some architectures; cold-start considerations for latency-sensitive services	Region/feature parity and Azure-specific operational considerations	In some cases, limited scale-to-zero behavior; may be less cost-effective for sporadic workloads

Narrative analysis
- Cloud Run vs Azure Container Apps: differences are workload- and environment-dependent. Community reports suggesting performance differences are anecdotal and workload-specific; buyers should run benchmarks relevant to their workloads.
- Cloud Run vs AWS App Runner: App Runner is positioned for simple deployments from source or containers; differences in scale-to-zero behavior and published pricing models can affect cost for infrequent traffic patterns.
- Cloud Run vs DIY Knative/Kubernetes: self-managed Knative on Kubernetes provides more control and portability at the cost of higher operational complexity.