# Next.js on Google Cloud Run

Canonical: https://inetgeek.com/stacks/nextjs-on-google-cloud-run/

Google Cloud Run publishes its own guide for deploying Next.js.

React framework with file-based routing, server components and a build step that produces both static and server-rendered output.

## What Next.js needs

Every host claims to run Next.js, so the claim on its own decides nothing. These are the things Next.js requires from the platform underneath it, and what Google Cloud Run publishes about each. Google Cloud Run documents 2 of the 4.

| Requirement | Google Cloud Run | Why it matters |
| --- | --- | --- |
| Max request duration | 5 minutes by default, extendable to 60 minutes per request. | Server components and route handlers run per request. The wall-clock ceiling decides whether a slow upstream API or a model response can finish at all. |
| Streaming response limit | Not documented | The App Router streams the dynamic parts of a page as they resolve. A host that buffers the whole response first removes the benefit. |
| Edge network | Limited — deploy per region, add a load balancer | Middleware runs on every matched request before the cache is consulted. Where it executes decides how much latency it adds. |
| Build allowance | Not documented | A large Next.js app prerenders at build time, so the build allowance is a recurring cost rather than a one-off. |

- Max request duration source: https://docs.cloud.google.com/run/docs/configuring/request-timeout
- Edge network source: https://docs.cloud.google.com/run/docs/multiple-regions

## What Google Cloud Run documents

> Build and deploy a Next.js web app to Cloud Run Learn how to use a single command to build and deploy a "Hello World" web application from a code sample to Google Cloud using Cloud Run. By following the steps in this quickstart, Cloud Run automatically builds a Dockerfile for you when you deploy from source code.

Source: https://docs.cloud.google.com/run/docs/quickstarts/frameworks/deploy-nextjs-service

## What it costs to run there

|  | Google Cloud Run |
| --- | --- |
| Pricing model | Metered by resource, billed in 100 ms increments, with no monthly minimum. Two billing settings change what is counted: request-based charges CPU only while a request is being processed, instance-based charges for the whole instance lifecycle. Prices vary by region — the location list is split into Tier 1 and Tier 2 pricing — and the free tier is applied as a spending-based discount at Tier 1 rates. |
| Regions | 41 regions, counted from Cloud Run's own locations list — Google publishes the list rather than a total. They are split into Tier 1 and Tier 2 pricing, so the region chosen changes the bill as well as the latency. |

- Pricing model source: https://cloud.google.com/run/pricing
- Regions source: https://docs.cloud.google.com/run/docs/locations

## Whether it suits you

A container you already build, that should cost nothing when nobody is using it. Scales to zero by default and back up on request volume, with a 60-minute ceiling per request that most request-driven platforms do not offer.

Consider something else if: You need a process that stays running between requests, or a disk that survives a deploy.

Written by Palash Bagchi on 2026-09-09. This is a recommendation, not a sourced fact — it carries no citation because it is an opinion.

## Related

- Best hosting for Next.js: https://inetgeek.com/stacks/nextjs/
- Google Cloud Run: https://inetgeek.com/hosting/google-cloud-run/