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 actually requires from the platform underneath it, and what Railway publishes about each. Railway documents 3 of the 4.
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.
Sources (1) →Sources ↓
- Specs & Limits — Railway Docs ↗
“HTTP requests can run for up to 15 minutes if data keeps transferring (for example, keep-alive heartbeats), and are otherwise closed after 5 minutes with no data transferred. [...] Websocket connections are exempt from these duration and inactivity limits, and can stay open indefinitely, even while idle.”
Read 2026-09-05 · official docs
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 ↓
- Edge Networking — Railway Docs ↗
“Railway uses a globally distributed edge network to route traffic to your deployments. [...] Edge POPs are the entry points where user traffic first reaches Railway. Each request is terminated at the nearest POP and tagged with that POP's ID in the X-Railway-Edge header.”
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
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.
Sources (1) →Sources ↓
- App Sleeping — Railway Docs ↗
“The first request made to a slept service wakes it. [...] For Railway to put a service to sleep, a service must not send outbound traffic for at least 5 minutes. [...] Slept services still consume a slot on Railway's infrastructure, enabling Serverless de-prioritizes your workload”
Read 2026-09-13 · official docs
What Railway documents.
Railway publishes its own guide for deploying Nuxt.
Nuxt is a Vue.js framework that makes web development intuitive and powerful.
Sources (1) →Sources ↓
- Deploy a Nuxt App | Railway Guides ↗
“Nuxt is a Vue.js framework that makes web development intuitive and powerful.”
Read 2026-09-05 · official docs
Nuxt features on Railway
Capabilities Railway documents specifically for Nuxt, with the constraint it documents alongside each.
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.
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.
Sources (2) →Sources ↓
- Deploy a Nuxt App | Railway Guides ↗
“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.”
Read 2026-09-13 · official docs
- Choose Between SSR, SSG, and ISR for Your Frontend | Railway Guides ↗
“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.”
Read 2026-09-13 · official docs
What it costs to run there.
- 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
Sources (3) →Sources ↓
- Plans — Railway Docs ↗
“Plan Price Free $0 / month Hobby $5 / month Pro $20 / month Enterprise Custom”
Read 2026-09-13 · official pricing
- Pricing Plans | Railway Docs ↗
“If your total resource usage exceeds $5 in any given billing period, you will be charged the delta”
Read 2026-09-05 · official docs
- Regions — Railway Docs ↗
“Name Location Region Identifier US West Metal California, USA us-west2 US East Metal Virginia, USA us-east4-eqdc4a EU West Metal Amsterdam, Netherlands europe-west4-drams3a Southeast Asia Metal Singapore asia-southeast1-eqsg3a”
Read 2026-09-13 · official docs
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.
Visit Railway documentation