Nuxt on Render
Render 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 Render publishes about each. Render documents 3 of the 4.
Max request duration
Not documented
Nitro server routes and server-side rendering both run per request, bounded by this ceiling.
Edge network
Supported
Nuxt's route rules cache and revalidate at the edge. Without an edge network those rules degrade to origin rendering.
Sources (1) →Sources ↓
- Static Sites – Render Docs ↗
“Render serves your site over a blazing-fast, reliable, and secure global CDN. We cache your content on network edges around the world, ensuring the fastest possible load times for your users.”
Read 2026-09-05 · official docs
Build minutes
Hobby: 500; Pro: 1000; Scale: 5000
Nuxt prerenders routes at build time when asked to, which moves cost from request time into the build allowance.
Sources (1) →Sources ↓
- Build Pipeline – Render Docs ↗
“Each workspace receives included Starter-tier pipeline minutes per month — Hobby 500, Pro 1000, Scale 5000”
Read 2026-09-05 · official docs
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 ↓
- Free Instances – Render Docs ↗
“Render spins down a Free web service that goes 15 minutes without receiving any inbound traffic.”
Read 2026-09-05 · official docs
What Render documents.
Render publishes its own guide for deploying Nuxt.
NuxtJS is a Vue.js framework that you can deploy on Render in just a few clicks.
Sources (1) →Sources ↓
- Deploy a Nuxt.js App – Render Docs ↗
“NuxtJS is a Vue.js framework that you can deploy on Render in just a few clicks.”
Read 2026-09-05 · official docs
What it costs to run there.
- Pricing model
- The Hobby plan does not have a monthly fee, so you only pay for usage.
- When you exceed a cap
- Pipeline minutes: overage is auto-purchased, but with no payment method or once the monthly spend limit is hit, Render stops all pipeline tasks including service builds for the rest of the month (platform-wide, all plans)
- Regions
- Oregon, USA; Ohio, USA; Virginia, USA; Frankfurt, Germany; Singapore
Sources (3) →Sources ↓
- Platform Features by Plan – Render Docs ↗
“The Hobby plan does not have a monthly fee, so you only pay for usage.”
Read 2026-09-05 · official docs
- Build Pipeline – Render Docs ↗
“If you run out of pipeline minutes during a given month, you automatically purchase a supplementary amount of minutes for your current tier, unless you've reached your monthly spend limit, or you haven't added a payment method. In the above cases, Render stops running pipeline tasks (including service builds!) for the remainder of the current month.”
Read 2026-09-05 · official docs
- Regions ↗
“Oregon, USA / Ohio, USA / Virginia, USA / Frankfurt, Germany / Singapore”
Read 2026-09-05 · official docs
Whether it suits you.
Workloads that need real background workers and persistent processes alongside web services, deployed from a repository or a Dockerfile. Managed Postgres and static sites run on the same platform.
Consider something else if…
Free web services spin down after 15 minutes without traffic, which makes the free tier unsuitable for anything that must answer immediately.
Visit Render documentation