Nuxt on Google Cloud Run
Google Cloud Run publishes its own guide for deploying Nuxt.
Vue framework with file-based routing and a choice of static, server-rendered or hybrid output.
What Nuxt needs.
Every host claims to run Nuxt, so the claim on its own decides nothing. These are the things Nuxt actually requires from the platform underneath it, and what Google Cloud Run publishes about each. Google Cloud Run documents 3 of the 4.
Max request duration
5 minutes by default, extendable to 60 minutes per request.
Nitro server routes and server-side rendering both run per request, bounded by this ceiling.
Sources (1) →Sources ↓
- Configure request timeout for services — Google Cloud Documentation ↗
“The timeout is set by default to 5 minutes (300 seconds) and can be extended up to 60 minutes (3600 seconds).”
Read 2026-09-09 · official docs
Edge network
Limited — deploy per region, add a load balancer
Nuxt's route rules cache and revalidate at the edge. Without an edge network those rules degrade to origin rendering.
Sources (1) →Sources ↓
- Serve traffic from multiple regions — Cloud Run — Google Cloud Documentation ↗
“Because Cloud Run services deploy into individual regions, you must deploy your service to multiple regions and then configure global load balancing for the service. You can automate cross-regional failover using Cloud Run service health.”
Read 2026-09-09 · official docs
Build allowance
Not documented
Nuxt prerenders routes at build time when asked to, which moves cost from request time into the build allowance.
Scales to zero
Supported
Nitro can deploy as functions. Scaling to zero removes the idle bill and adds a cold start to the first request instead.
Sources (1) →Sources ↓
- About instance autoscaling in Cloud Run services — Google Cloud Documentation ↗
“When a revision does not receive any traffic, by default, it is scaled to zero instances.”
Read 2026-09-09 · official docs
What Google Cloud Run documents.
Google Cloud Run publishes its own guide for deploying Nuxt.
Build and deploy a Nuxt.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.
Sources (1) →Sources ↓
- Quickstart: Build and deploy a Nuxt.js web app to Google Cloud with Cloud Run ↗
“Build and deploy a Nuxt.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.”
Read 2026-09-09 · official docs
What it costs to run there.
- 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.
Sources (2) →Sources ↓
- Cloud Run pricing — Google Cloud ↗
“Cloud Run charges you only for the resources you use, rounded up to the nearest 100 millisecond. Your total Cloud Run bill will be the sum of the resource usage in the pricing table after the free tier is applied. [...] Cloud Run pricing depends on the selected region. Pricing for Cloud Run services also depends on the billing configuration. [...] The free tier is applied as a spending based discount using Tier 1 pricing.”
Read 2026-09-09 · official pricing
- Cloud Run locations — Google Cloud Documentation ↗
“Each Cloud Run resource resides in a region. [...] Subject to Tier 1 pricing asia-east1 (Taiwan) asia-northeast1 (Tokyo) asia-northeast2 (Osaka) asia-south1 (Mumbai, India) asia-southeast1 [...] northamerica-northeast2 (Toronto) southamerica-east1 (Sao Paulo, Brazil) southamerica-west1 (Santiago, Chile) us-west2 (Los Angeles) us-west3 (Salt Lake City) us-west4 (Las Vegas)”
Read 2026-09-09 · official docs
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.
Visit Google Cloud Run documentation