Stay organized with collections
Save and categorize content based on your preferences.
This page lays out a list of criteria to help you determine if your app is
well-suited to be a Cloud Run service.
Criteria
In order to be a good fit as a Cloud Run service, your app needs
to meet all of the following criteria. See the Cloud Run
container contract for more
information.
Serves requests, streams, or events delivered using HTTP, HTTP/2, WebSockets,
or gRPC, or executes to completion.
Does not require a localpersistentfile system,
but either a local ephemeral file system or a network file system.
If your app meets those criteria, then it's good fit for
Cloud Run! To get started, try one of the
Cloud Run quickstarts.
If your app doesn't meet all of the criteria, you might want to check out
Google Kubernetes Engine (GKE) as a hosting option. For a
comparison of Cloud Run and Google Kubernetes Engine, see the
comparison guide. To
assess your application requirements for choosing between Cloud Run and Google Kubernetes Engine based on
technical and organizational considerations, see the Selection guide for managed container runtime environments.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[],[],null,["# Is my app a good fit for a Cloud Run service?\n\nThis page lays out a list of criteria to help you determine if your app is\nwell-suited to be a Cloud Run service.\n\nCriteria\n--------\n\nIn order to be a good fit as a Cloud Run service, your app needs\nto meet *all* of the following criteria. See the Cloud Run\n[container contract](/run/docs/reference/container-contract) for more\ninformation.\n\n- Serves requests, streams, or events delivered using HTTP, HTTP/2, WebSockets, or gRPC, or executes to completion.\n- Does not require a *local* *persistent* [file system](/run/docs/reference/container-contract#filesystem), but either a local *ephemeral* file system or a *network* file system.\n- Is built to handle [multiple instances of the app running simultaneously](/run/docs/about-instance-autoscaling).\n- Does not require more than [8 CPU and 32 GiB of memory per instance](/run/quotas#cloud_run_limits).\n\nIf your app meets those criteria, then it's good fit for\nCloud Run! To get started, try one of the\n[Cloud Run quickstarts](/run/docs/quickstarts#build-and-deploy-a-web-service).\n\nIf your app doesn't meet all of the criteria, you might want to check out\n[Google Kubernetes Engine (GKE)](/kubernetes-engine) as a hosting option. For a\ncomparison of Cloud Run and Google Kubernetes Engine, see the\n[comparison guide](/kubernetes-engine/docs/concepts/gke-and-cloud-run). To\nassess your application requirements for choosing between Cloud Run and Google Kubernetes Engine based on\ntechnical and organizational considerations, see the [Selection guide for managed container runtime environments](/architecture/select-managed-container-runtime-environment)."]]
