What is Google Cloud Run?
Google Cloud Run is a managed application platform for running code, including container-based services and jobs. Service billing configuration, resource allocation and connected build or storage products affect the complete workload cost.
Who is Google Cloud Run for?
Teams running an application or job on Google Cloud while choosing a managed execution and billing model.
Decide whether the workload serves requests or completes a job
The Cloud Run overview describes managed services for request handling and jobs that perform work and finish, alongside other resource types. The choice should follow what the code needs to do rather than a generic “serverless” label.
For a proposed API, define a response and the data dependencies. For a proposed processing job, define the input set and the completed output. Keep those briefs distinct when comparing Lambda, Azure Functions or Workers. The request path, background work and persistent storage need an explicit home.
Google Cloud Run features
The core capabilities to consider for your workflow.
- Managed application services
- Container-based execution and jobs
- Configurable service request timeouts
Google Cloud Run pricing
Usage-based; monthly free allowances
Budget the selected service or job configuration, region, CPU, memory and request usage. Treat the free tier as a billing-account-level allowance, and include any Cloud Build, Artifact Registry or Eventarc usage separately.
Calculate the cost of your quote →Free access & evaluation
Cloud Run has conditional monthly free-tier allowances. The request-based service offer lists two million free requests; other resources, billing modes and related services have their own scope.
Before you choose Google Cloud Run
Request-based and instance-based billing have different usage measures.
Free-tier usage is shared across projects by billing account.
Build, artifact storage and event-delivery products can add separate costs.
Include the build and the billing-account scope
Cloud Run pricing applies different usage measures by configuration. Its free tier is shared across projects by billing account, with region and resource conditions. Source deployment can also involve Cloud Build and Artifact Registry; those products are not included in the Cloud Run price.
For services, check the request timeout against the actual client and event source. A task may need a different execution design even if a longer service timeout is configurable. Build a budget from the chosen resource type, billing setting, expected demand and dependencies, then compare the same assumptions across the shortlist.
Explore related software
Google Cloud Run FAQs
Does Cloud Run include 2 million free requests every month?
The reviewed request-based service pricing lists two million free requests per month. The free tier has billing-account, region and resource conditions; it is not a promise that every Cloud Run workload or connected product is free.
Does every Cloud Run project get an independent free tier?
No. Free-tier usage is aggregated across projects by billing account and resets monthly. It is applied as a spending-based discount using Tier 1 pricing.
Can Cloud Run source deployment cost money while runtime use remains within the free tier?
Yes. Cloud Build and Artifact Registry have separate pricing. Artifact storage can incur charges even when the Cloud Run runtime use remains within its free allowance.
What is the default Cloud Run service request timeout?
The documented default is 5 minutes, or 300 seconds, configurable up to 60 minutes. Triggering services can impose their own timeout boundaries.
What is the difference between a Cloud Run service and a job?
A service handles incoming requests through an endpoint. A job runs tasks to completion. Choose the resource type around the application’s actual work and completion conditions.