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 minutes
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
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 ↓
- Serverless (App Sleeping) | Railway Docs ↗
“Serverless allows you to increase the efficiency of resource utilization on Railway and may reduce the usage cost of a service, by ensuring it is running only when necessary. [...] When Serverless is enabled for a service, Railway automatically detects inactivity based on outbound traffic. [...] Inactivity is sampled on an interval rather than measured continuously, so in practice a service sleeps somewhere between 5 and 10 minutes after its last outbound traffic. [...] Slept services still consume a slot on Railway's infrastructure.”
Read 2026-09-05 · 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
What it costs to run there.
- Entry paid plan
- $5 / month (Hobby)
- Pricing model
- Plan fee that includes an equivalent usage credit
- 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 ↓
- Railway plans ↗
“Hobby Plan: For indie hackers and developers to build and deploy personal projects — $5/month”
Read 2026-09-05 · official docs
- 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
- Railway regions ↗
“US West Metal — California, USA; US East Metal — Virginia, USA; EU West Metal — Amsterdam, Netherlands; Southeast Asia Metal — Singapore”
Read 2026-09-05 · 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