# Nuxt on Railway

Canonical: https://inetgeek.com/stacks/nuxt-on-railway/

Railway 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 requires from the platform underneath it, and what Railway publishes about each. Railway documents 3 of the 4.

| Requirement | Railway | Why it matters |
| --- | --- | --- |
| Max request duration | 15 minutes while data keeps transferring; closed after 5 minutes with no data transferred. Websocket connections are exempt and can stay open indefinitely. | 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. |
| 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 | Limited — Serverless sleeps an idle service, but a slept service still holds a slot and is de-prioritised. | Nitro can deploy as functions. Scaling to zero removes the idle bill and adds a cold start to the first request instead. |

- Max request duration source: https://docs.railway.com/networking/public-networking/specs-and-limits
- Edge network source: https://docs.railway.com/networking/edge-networking
- Scales to zero source: https://docs.railway.com/reference/app-sleeping

## What Railway documents

> Nuxt is a Vue.js framework that makes web development intuitive and powerful.

Source: https://docs.railway.com/guides/nuxt

### Nuxt features on Railway

- **zero_config_deploy**: Limited — Add "start":"node .output/server/index.mjs" to the package.json file. [...] Railway uses Railpack to build and deploy your code with zero configuration. Railpack will pick up the start script in the package.json file and use it to serve the app. ([source](https://docs.railway.com/guides/nuxt))
- **route_rules_isr**: Limited — Nuxt ( routeRules with swr or isr options) [...] On Railway: deploy as a Node service (same as SSR). The server must stay running to handle revalidation requests. [...] Cache is lost on every deploy. Railway replaces the container on each deployment. ([source](https://docs.railway.com/guides/ssr-ssg-isr))

## What it costs to run there

|  | Railway |
| --- | --- |
| Entry paid plan | $5 / month (Hobby) |
| Pricing model | A base subscription fee that goes towards usage, with the plan's own credit included; anything beyond the credit is billed as resource usage. |
| When you exceed a cap | Billed automatically: on the Hobby plan ($5/month, includes $5 of resource usage) usage above the included amount is charged as a delta on top of the subscription — no throttling or suspension is documented |
| Regions | 4 regions: California, Virginia, Amsterdam, Singapore |

- Entry paid plan source: https://docs.railway.com/reference/pricing/plans
- Pricing model source: https://docs.railway.com/reference/pricing/plans
- When you exceed a cap source: https://docs.railway.com/pricing/plans
- Regions source: https://docs.railway.com/reference/regions

## Whether it suits you

Teams that want a plan fee which doubles as usage credit, and deploy services straight from a Dockerfile without managing servers. The $5 Hobby fee comes back as $5 of resource usage.

Consider something else if: You need to run in a region outside California, Virginia, Amsterdam or Singapore.

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

## Related

- Best hosting for Nuxt: https://inetgeek.com/stacks/nuxt/
- Railway: https://inetgeek.com/hosting/railway/