After creating an app with an AI-assisted tool likeGoogle AI StudioandVertex AI Studio, you can useCloud Runto deploy the app and make it available to users.

This guide describes the concepts of Cloud Run and somemodifications you can make after you use an AI-assisted tool orvibe codingtool to create and deploy an app. Understanding these concepts helps youtransition your application from a development environment to a scalableplatform.

From code to container

Cloud Run runs your application inside a container. A containeris a standard package that includes your application code and all itsdependencies. This packaging ensures that your application runs reliably andconsistently in any computing environment.

If you're not familiar with containers, Cloud Run lets youdeploy from source code, otherwise, you candeploy container images.

To deploy to Cloud Run, you first build your application into acontainer image. You can create a container image using aDockerfile or haveGoogle Cloud build one for you automatically from your source codeusing buildpacks. You then store this image in an artifact registry.

How Cloud Run works

Cloud Run uses a few core resources to manage and run yourcontainerized application. These resources work together to provide a seamlessdeployment and scaling experience.

Aservice is the primary resource in Cloud Run. Each servicehas a unique, permanent URL (run.app). When you deploy to a service,Cloud Run creates a new, immutable revision. Arevisionconsists of a specific container image and settings that you configure, such asmemory limits and environment variables.

By default, Cloud Run automatically runs your revisions on one ormore instances. Aninstance, sometimes called acontainer instance, is asingle, isolated environment that runs a copy of your container within aCloud Run service. To manage costs, Cloud Runscales the number of instances up or down to as low as to zero, based on thenumber of incoming instances. Cloud Run also lets youconfigure different settings to control the behavior ofyour service, andconnect to Google Cloud servicesto build a complete full-stack app that is highly scalable.

When your Cloud Run service interacts with Google CloudAPIs or other Cloud Run services, Cloud Run uses theservice identity to accessGoogle Cloud APIs. By default, Cloud Run automatically usesthedefault Compute Engine service accountto make make calls to Google Cloud APIs to perform the operations itneeds. We recommend that you create a custom service account, and grant thisidentity the minimal set of permissions needed for accessing a specificGoogle Cloud resource.

Update your service

After you've deployed your Cloud Run app using an AI-assistedtool or vibe coding tool, you can update the default settings to optimize forperformance, cost, and security.

To modify your service:

1. Go to the Cloud RunServices page:

   Go to Cloud Run

2. Select your service.

3. SelectEdit and deploy new revision.

4. Modify theconfiguration settings as needed.

   1. In theEdit Container section, you can modify the following:

      • Container configuration
      • CPU limits
      • Memory limits
      • Secrets
      • Environment variables

   2. In theSecurity tab, select the available options, such as:

      • HTTP/2
      • VPC connection

   3. In theSecurity tab, modify the default compute service account to adifferentservice accountswith minimal permissions.

   4. UnderRequest, modify the following if needed:

      • Request timeout
      • Concurrency

   5. UnderBilling, modify thebilling settingsif needed.

1. UnderExecution environment, modify theexecution environment if needed.

1. UnderRevision scaling, if you use the default Cloud Runautoscaling, optionally specify theminimum instances. If you usemanual scaling, specify the number of instances for the service.

2. ClickEdit & deploy new revision.

To learn more about viewing, copying, or deleting your service, seeManage services.

Best practices

For best practices to ensure your apps run efficiently onCloud Run, seeDevelop your service andGeneral development tips for services.

Cloud Run and the Google Cloud services that your app usesis a billable service. You can use thepricing calculator to estimateyour costs based on your expected usage.

What's next

• To get started, follow the quickstart todeploy a container image.
• To learn about the different types of resources and deployment options, seeResource model.
• For information on preparing your code for deployment, see theContainer runtime contract.
• To learn more about the benefits of using Cloud Run, SeeCloud Run AI use cases.