This documentation is for the Latest version of Cloud Run for Anthos, which uses Anthos fleets and Anthos Service Mesh. Learn more.

The past version has been archived but the documentation remains available for existing users.

Choosing between Cloud Run and Cloud Run for Anthos

Stay organized with collections Save and categorize content based on your preferences.

This page provides details to help you choose between Cloud Run and Cloud Run for Anthos. Cloud Run is a fully managed and completely serverless product while Cloud Run for Anthos offers a serverless developer experience on a shared responsibility Anthos platform. If you're already using Anthos, Cloud Run for Anthos can easily deploy your workloads across hybrid and multi-cloud environments, all with the same consistent experience. Plus, you can easily switch from Cloud Run to Cloud Run for Anthos or vice versa; all without changing your application code.

One way to visualize the differences at a high-level architectural view:


Cloud Run

The Cloud Run platform allows you to deploy stateless containers without having to worry about the underlying infrastructure. Your workloads are automatically scaled out or in to zero depending on the traffic to your app. Cloud Run has pay-per-use pricing, rounded up to the nearest 100 millisecond.

Cloud Run for Anthos

Cloud Run for Anthos abstracts away the complexity of Kubernetes, making it easy to build and deploy apps across hybrid and multi-cloud environments. Cloud Run for Anthos is Google's managed and fully supported Knative offering, an open source project that enables serverless workloads on Kubernetes.

Comparison table

The follow table shows some key differences between the platforms:

Cloud Run Cloud Run for Anthos
Pricing Pay-per-use Included as part of Anthos.
Machine types Limited CPU and Memory. Standard or custom machine types on Anthos, including GPUs.
Autoscaling Up to 1,000 container instances by default, can be increased via a Quota increase. Limited by the capacity of your Anthos cluster.
Identity and policy Manage the identities that are allowed to invoke each service (or allow unauthenticated invocations). Publish services to the internet or make them available to cluster or VPC network only.
Networking Access to VPC / Compute Engine network via Serverless VPC Access. Services are not part of the Istio service mesh. Access to VPC / Compute Engine network. Services participate in the Anthos Service Mesh.
URLs Automatic service URLs and SSL certificates. Custom domains only with manual SSL certificates.
Container isolation Strict container isolation based on gVisor sandbox. Default Kubernetes container isolation.
Execution environments Fully managed on Google infrastructure. Anthos clusters.