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 local persistent file system , but either a local ephemeral file system or a network file system.
- Is built to handle multiple instances of the app running simultaneously .
- Does not require more than 8 CPU and 32 GiB of memory per instance .
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 .
For automatic GitHub integration and optimized deployments with CDN for server-rendered Next.js or Angular apps, consider using Firebase App Hosting .
