Nuxt on Fly.io
Fly.io 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 Fly.io publishes about each. Fly.io documents 2 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
Limited
Nuxt's route rules cache and revalidate at the edge. Without an edge network those rules degrade to origin rendering.
Sources (1) →Sources ↓
- The Fly.io Architecture — Fly Docs ↗
“We broadcast and accept traffic from ranges of IP addresses (both IPv4 and IPv6) in all our datacenters. When we receive a connection on one of those IPs, we match it back to an active customer application, and then proxy the TCP connection to the closest available microVM.”
Read 2026-09-05 · 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 ↓
- Automatically stop and start Machines · Fly Docs ↗
“Use autostop/autostart to automatically start and stop or suspend existing Machines based on incoming requests. [...] you don't pay for their CPU and RAM when they're in a stopped or suspended state.”
Read 2026-09-05 · official docs
What Fly.io documents.
Fly.io publishes its own guide for deploying Nuxt.
You can deploy your Nuxt app on Fly with minimal effort, our CLI will do the heavy lifting.
Sources (1) →Sources ↓
- Run a Nuxt App · Fly Docs ↗
“You can deploy your Nuxt app on Fly with minimal effort, our CLI will do the heavy lifting.”
Read 2026-09-05 · official docs
Nuxt features on Fly.io
Capabilities Fly.io documents specifically for Nuxt, with the constraint it documents alongside each.
zero_config_deploy
Supported
You can deploy your Nuxt app on Fly with minimal effort, our CLI will do the heavy lifting. [...] Scanning source code Detected a Nuxt app
Sources (1) →Sources ↓
- Run a Nuxt App · Fly Docs ↗
“You can deploy your Nuxt app on Fly with minimal effort, our CLI will do the heavy lifting. [...] Scanning source code Detected a Nuxt app”
Read 2026-09-13 · official docs
What it costs to run there.
- Pricing model
- Usage-based, no compute plan tiers; billing is pro-rated for the time resources are provisioned.
- When you exceed a cap
- No plan cap to exceed — Fly bills per second for provisioned resources. The only documented enforcement is unspecified automated scaling limits, which surface as an error message (platform-wide, all plans)
- Regions
- 17 regions
Sources (2) →Sources ↓
- Pricing — Fly.io Docs ↗
“Plans get complicated, so we just charge based on usage. Pick and choose which pieces you need for your application; that's all you'll see on your invoice.”
Read 2026-09-14 · official docs
- Regions - Fly.io Documentation ↗
“You can host your apps in any of the following regions. Region ID Region Location Gateway MPG ams Amsterdam, Netherlands ✓ ✓ arn Stockholm, Sweden ✓ cdg Paris, France ✓ dfw Dallas, Texas (US) ✓ ✓ ewr Secaucus, NJ (US) ✓ fra Frankfurt, Germany ✓ ✓ gru Sao Paulo, Brazil ✓ iad Ashburn, Virginia (US) ✓ ✓ jnb Johannesburg, South Africa lax Los Angeles, California (US) ✓ ✓ lhr London, United Kingdom ✓ ✓ nrt Tokyo, Japan ✓ ✓ ord Chicago, Illinois (US) ✓ ✓ sin Singapore, Singapore ✓ ✓ sjc San Jose, California (US) ✓ ✓ syd Sydney, Australia ✓ ✓ yyz Toronto, Canada ✓ ✓”
Read 2026-09-27 · official docs
Whether it suits you.
Workloads that ship as Docker images and need placement in particular regions. Billing is purely usage-based with no plan tiers, which suits spiky or region-pinned traffic better than a flat monthly fee.
Consider something else if…
You want a predictable flat bill rather than charges that track the resources provisioned for each app.
Visit Fly.io documentation